From: Sarthak Sharma <sarthak.sharma@arm.com>
To: zhaozhengzhuo <zhaozhengzhuo@uniontech.com>,
David Hildenbrand <david@kernel.org>,
Shuah Khan <shuah@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
John Hubbard <jhubbard@nvidia.com>, Peter Xu <peterx@redhat.com>,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/mm: fix gup_longterm EINVAL error message
Date: Fri, 24 Jul 2026 12:56:38 +0530 [thread overview]
Message-ID: <6b2f4fde-0da2-4c0c-aa97-f23982fb7e18@arm.com> (raw)
In-Reply-To: <8A3ADC563A32EF67+20260724065929.1474539-1-zhaozhengzhuo@uniontech.com>
Hi!
On 7/24/26 12:29 PM, zhaozhengzhuo wrote:
> The gup_longterm test prints a literal "n" when
> PIN_LONGTERM_TEST_START fails with EINVAL because the string is missing the
> newline escape sequence.
>
> Print a newline instead.
>
> Signed-off-by: zhaozhengzhuo <zhaozhengzhuo@uniontech.com>
Can you add a Fixes: tag here? For this patch, it would be
Fixes: 800ddf3cd74b ("selftests/mm: report errno when things fail in
gup_longterm")
Rest looks good to me.
Reviewed-by: Sarthak Sharma <sarthak.sharma@arm.com>
> ---
> tools/testing/selftests/mm/gup_longterm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/mm/gup_longterm.c b/tools/testing/selftests/mm/gup_longterm.c
> index eb8963e9d..c03b4f891 100644
> --- a/tools/testing/selftests/mm/gup_longterm.c
> +++ b/tools/testing/selftests/mm/gup_longterm.c
> @@ -196,7 +196,7 @@ static void do_test(int fd, size_t size, enum test_type type, bool shared)
> args.flags |= rw ? PIN_LONGTERM_TEST_FLAG_USE_WRITE : 0;
> ret = ioctl(gup_fd, PIN_LONGTERM_TEST_START, &args);
> if (ret && errno == EINVAL) {
> - ksft_print_msg("PIN_LONGTERM_TEST_START failed (EINVAL)n");
> + ksft_print_msg("PIN_LONGTERM_TEST_START failed (EINVAL)\n");
> result = KSFT_SKIP;
> break;
> } else if (ret && errno == EFAULT) {
>
> base-commit: c04df384b55dd9dcf72c36b661becb5aaba371a9
next prev parent reply other threads:[~2026-07-24 7:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 6:59 zhaozhengzhuo
2026-07-24 7:26 ` Sarthak Sharma [this message]
2026-07-24 7:46 ` [PATCH v2] " zhaozhengzhuo
2026-07-24 8:22 ` Dev Jain
2026-07-24 19:02 ` David Hildenbrand (Arm)
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=6b2f4fde-0da2-4c0c-aa97-f23982fb7e18@arm.com \
--to=sarthak.sharma@arm.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.com \
--cc=shuah@kernel.org \
--cc=zhaozhengzhuo@uniontech.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
all inboxes | Powered by JetHome®