From: David Hildenbrand <david@redhat.com>
To: "Arnd Bergmann" <arnd@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Jérôme Glisse" <jglisse@redhat.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Alistair Popple <apopple@nvidia.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
Thorsten Blum <thorsten.blum@linux.dev>,
Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lib/test_hmm: reduce stack usage
Date: Tue, 10 Jun 2025 12:31:31 +0200 [thread overview]
Message-ID: <f9155f8d-022c-4341-85da-5b08d6a3aee9@redhat.com> (raw)
In-Reply-To: <20250610092159.2639515-1-arnd@kernel.org>
On 10.06.25 11:21, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> The various test ioctl handlers use arrays of 64 integers that add up to 1KiB
> of stack data, which in turn leads to exceeding the warning limit in some
> configurations:
>
> lib/test_hmm.c:935:12: error: stack frame size (1408) exceeds limit (1280) in 'dmirror_migrate_to_device' [-Werror,-Wframe-larger-than]
>
> Use half the size for these arrays, in order to stay under the warning limits.
> The code can already deal with arbitrary lengths, but this may be a little less
> efficient.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> lib/test_hmm.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/lib/test_hmm.c b/lib/test_hmm.c
> index 5b144bc5c4ec..761725bc713c 100644
> --- a/lib/test_hmm.c
> +++ b/lib/test_hmm.c
> @@ -330,7 +330,7 @@ static int dmirror_fault(struct dmirror *dmirror, unsigned long start,
> {
> struct mm_struct *mm = dmirror->notifier.mm;
> unsigned long addr;
> - unsigned long pfns[64];
> + unsigned long pfns[32];
> struct hmm_range range = {
> .notifier = &dmirror->notifier,
> .hmm_pfns = pfns,
> @@ -879,8 +879,8 @@ static int dmirror_migrate_to_system(struct dmirror *dmirror,
> unsigned long size = cmd->npages << PAGE_SHIFT;
> struct mm_struct *mm = dmirror->notifier.mm;
> struct vm_area_struct *vma;
> - unsigned long src_pfns[64] = { 0 };
> - unsigned long dst_pfns[64] = { 0 };
> + unsigned long src_pfns[32] = { 0 };
> + unsigned long dst_pfns[32] = { 0 };
> struct migrate_vma args = { 0 };
> unsigned long next;
> int ret;
> @@ -939,8 +939,8 @@ static int dmirror_migrate_to_device(struct dmirror *dmirror,
> unsigned long size = cmd->npages << PAGE_SHIFT;
> struct mm_struct *mm = dmirror->notifier.mm;
> struct vm_area_struct *vma;
> - unsigned long src_pfns[64] = { 0 };
> - unsigned long dst_pfns[64] = { 0 };
> + unsigned long src_pfns[32] = { 0 };
> + unsigned long dst_pfns[32] = { 0 };
> struct dmirror_bounce bounce;
> struct migrate_vma args = { 0 };
> unsigned long next;
> @@ -1144,8 +1144,8 @@ static int dmirror_snapshot(struct dmirror *dmirror,
> unsigned long size = cmd->npages << PAGE_SHIFT;
> unsigned long addr;
> unsigned long next;
> - unsigned long pfns[64];
> - unsigned char perm[64];
> + unsigned long pfns[32];
> + unsigned char perm[32];
> char __user *uptr;
> struct hmm_range range = {
> .hmm_pfns = pfns,
Should we just add a define for the common value (now 32)?
TEST_HMM_NR_PFN or sth like that.
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2025-06-10 10:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 9:21 Arnd Bergmann
2025-06-10 10:31 ` David Hildenbrand [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f9155f8d-022c-4341-85da-5b08d6a3aee9@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=jgg@ziepe.ca \
--cc=jglisse@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=thorsten.blum@linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox