From: Andrew Morton <akpm@linux-foundation.org>
To: Joel Savitz <jsavitz@redhat.com>
Cc: linux-kernel@vger.kernel.org, Shuah Khan <shuah@kernel.org>,
Nico Pache <npache@redhat.com>,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
Sidhartha Kumar <sidhartha.kumar@oracle.com>
Subject: Re: [PATCH] selftests: clarify common error when running gup_test
Date: Sat, 7 May 2022 14:26:30 -0700 [thread overview]
Message-ID: <20220507142630.56f7ee13658d6fd78cc2d88f@linux-foundation.org> (raw)
In-Reply-To: <20220502224942.995427-1-jsavitz@redhat.com>
On Mon, 2 May 2022 18:49:42 -0400 Joel Savitz <jsavitz@redhat.com> wrote:
>
> The gup_test binary will fail showing only the output of perror("open") in
> the case that /sys/kernel/debug/gup_test is not found. This will almost
> always be due to CONFIG_GUP_TEST not being set, which enables
> compilation of a kernel that provides this file.
>
> Add a short error message to clarify this failure and point the user to
> the solution.
>
> --- a/tools/testing/selftests/vm/gup_test.c
> +++ b/tools/testing/selftests/vm/gup_test.c
> @@ -18,6 +18,8 @@
> #define FOLL_WRITE 0x01 /* check pte is writable */
> #define FOLL_TOUCH 0x02 /* mark page accessed */
>
> +#define GUP_TEST_FILE "/sys/kernel/debug/gup_test"
> +
> static unsigned long cmd = GUP_FAST_BENCHMARK;
> static int gup_fd, repeats = 1;
> static unsigned long size = 128 * MB;
> @@ -204,9 +206,11 @@ int main(int argc, char **argv)
> if (write)
> gup.gup_flags |= FOLL_WRITE;
>
> - gup_fd = open("/sys/kernel/debug/gup_test", O_RDWR);
> + gup_fd = open(GUP_TEST_FILE, O_RDWR);
> if (gup_fd == -1) {
> perror("open");
> + fprintf(stderr, "Unable to open %s: check that CONFIG_GUP_TEST=y\n",
> + GUP_TEST_FILE);
> exit(1);
> }
>
Sidhartha did a similar thing:
https://lkml.kernel.org/r/20220405214809.3351223-1-sidhartha.kumar@oracle.com
(Which is now in mm-stable at
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm)
Although in retroreview, it should have printed that to stderr rather
than to stdout.
prev parent reply other threads:[~2022-05-07 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 22:49 Joel Savitz
2022-05-07 21:26 ` Andrew Morton [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=20220507142630.56f7ee13658d6fd78cc2d88f@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jsavitz@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npache@redhat.com \
--cc=shuah@kernel.org \
--cc=sidhartha.kumar@oracle.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