From: Greg KH <gregkh@linuxfoundation.org>
To: wndgwang4 <guangming.wang@windriver.com>
Cc: stable@vger.kernel.org, Zi Yan <ziy@nvidia.com>,
Zach O'Keefe <zokeefe@google.com>,
David Hildenbrand <david@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 6.1.y] selftests/vm: fix split huge page tests
Date: Thu, 29 May 2025 13:39:14 +0200 [thread overview]
Message-ID: <2025052957-recolor-upward-a8a3@gregkh> (raw)
In-Reply-To: <20250528085440.818430-1-guangming.wang@windriver.com>
On Wed, May 28, 2025 at 04:54:40PM +0800, wndgwang4 wrote:
> From: Zi Yan <ziy@nvidia.com>
>
> [ upstream commit dd63bd7df41a8f9393a2e3ff9157a441c08eb996 ]
>
> Fix two inputs to check_anon_huge() and one if condition, so the tests
> work as expected.
>
> Steps to reproduce the issue.
> make headers
> make -C tools/testing/selftests/vm
>
> Before patching:test fails with a non-zero exit code
> ~/linux$ sudo tools/testing/selftests/vm/split_huge_page_test | echo 0
> 2
> ~/linux$ sudo tools/testing/selftests/vm/split_huge_page_test
> No THP is allocated
>
> After patching:
> ~/linux$ sudo tools/testing/selftests/vm/split_huge_page_test | echo 0
> 0
> ~/linux$ sudo tools/testing/selftests/vm/split_huge_page_test
> Split huge pages successful
> ...
>
> Link: https://lkml.kernel.org/r/20230306160907.16804-1-zi.yan@sent.com
> Fixes: c07c343cda8e ("selftests/vm: dedup THP helpers")
> Cc: stable@vger.kernel.org
> Signed-off-by: Zi Yan <ziy@nvidia.com>
> Reviewed-by: Zach O'Keefe <zokeefe@google.com>
> Tested-by: Zach O'Keefe <zokeefe@google.com>
> Acked-by: David Hildenbrand <david@redhat.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> Signed-off-by: wndgwang4 <guangming.wang@windriver.com>
We need a real name for a signed-off-by line, you all know this :(
prev parent reply other threads:[~2025-05-29 11:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 8:54 [PATCH 6.1.y] selftests/vm: fix split huge page tests wndgwang4
2025-05-29 11:39 ` Greg KH [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=2025052957-recolor-upward-a8a3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=guangming.wang@windriver.com \
--cc=stable@vger.kernel.org \
--cc=ziy@nvidia.com \
--cc=zokeefe@google.com \
/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