From: I Hsin Cheng <richard120310@gmail.com>
To: Peter Seiderer <ps.report@gmx.net>
Cc: shuah@kernel.org, brauner@kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH] selftests: pidfd: Fix compiling errors and warning
Date: Thu, 6 Feb 2025 00:46:51 +0800 [thread overview]
Message-ID: <Z6OV-1CTAcK3RS4e@vaxr-BM6660-BM6360> (raw)
In-Reply-To: <20250205130756.7b7b4f7e@gmx.net>
On Wed, Feb 05, 2025 at 01:07:56PM +0100, Peter Seiderer wrote:
> Hello *,
>
> On Wed, 5 Feb 2025 13:39:26 +0800, I Hsin Cheng <richard120310@gmail.com> wrote:
>
> > When compiling selftests files under tools/testing/selftests/pidfd/ ,
> > some compiling errors and warnings will pop out as the following.
> >
> > CC pidfd_fdinfo_test
> > pidfd_fdinfo_test.c: In function ‘child_fdinfo_nspid_test’:
> > pidfd_fdinfo_test.c:231:13: warning: implicit declaration of function \
> > ‘mount’ [-Wimplicit-function-declaration]
> > 231 | r = mount(NULL, "/", NULL, MS_REC | MS_PRIVATE, 0);
> > | ^~~~~
> > pidfd_fdinfo_test.c:231:36: error: ‘MS_REC’ undeclared \
> > (first use in this function)
> > 231 | r = mount(NULL, "/", NULL, MS_REC | MS_PRIVATE, 0);
> > | ^~~~~~
> > pidfd_fdinfo_test.c:231:36: note: each undeclared identifier is \
> > reported only once for each function it appears in
> > pidfd_fdinfo_test.c:231:45: error: ‘MS_PRIVATE’ undeclared \
> > (first use in this function); did you mean ‘MAP_PRIVATE’?
> > 231 | r = mount(NULL, "/", NULL, MS_REC | MS_PRIVATE, 0);
> > | ^~~~~~~~~~
> > | MAP_PRIVATE
> > pidfd_fdinfo_test.c:237:15: warning: implicit declaration of function \
> > ‘umount2’; did you mean ‘SYS_umount2’? \
> > [-Wimplicit-function-declaration]
> > 237 | (void)umount2("/proc", MNT_DETACH);
> > | ^~~~~~~
> > | SYS_umount2
> > pidfd_fdinfo_test.c:237:32: error: ‘MNT_DETACH’ undeclared \
> > (first use in this function)
> > 237 | (void)umount2("/proc", MNT_DETACH);
> > | ^~~~~~~~~~
> > make: *** [../lib.mk:222: \
> > ~/linux/tools/testing/selftests/pidfd/pidfd_fdinfo_test] Error 1
> >
> > Solve these errors and warnings by including header file <sys/mount.h>.
> >
> > Signed-off-by: I Hsin Cheng <richard120310@gmail.com>
> > ---
> > tools/testing/selftests/pidfd/pidfd_fdinfo_test.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/tools/testing/selftests/pidfd/pidfd_fdinfo_test.c b/tools/testing/selftests/pidfd/pidfd_fdinfo_test.c
> > index f062a986e..f718aac75 100644
> > --- a/tools/testing/selftests/pidfd/pidfd_fdinfo_test.c
> > +++ b/tools/testing/selftests/pidfd/pidfd_fdinfo_test.c
> > @@ -13,6 +13,7 @@
> > #include <syscall.h>
> > #include <sys/wait.h>
> > #include <sys/mman.h>
> > +#include <sys/mount.h>
> >
> > #include "pidfd.h"
> > #include "../kselftest.h"
>
> Predated patch already available, see
>
> https://lore.kernel.org/linux-kselftest/20250115105211.390370-1-ps.report@gmx.net/
>
Hello Peter,
Thanks for the kindly reminder!
Good to know it's already solved, thanks!
Regards,
I Hsin Cheng.
> Regards,
> Peter
>
prev parent reply other threads:[~2025-02-05 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 5:39 I Hsin Cheng
2025-02-05 12:07 ` Peter Seiderer
2025-02-05 16:46 ` I Hsin Cheng [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=Z6OV-1CTAcK3RS4e@vaxr-BM6660-BM6360 \
--to=richard120310@gmail.com \
--cc=brauner@kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=ps.report@gmx.net \
--cc=shuah@kernel.org \
/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®