mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Amin Vakil <info@aminvakil.com>
To: Shuah Khan <skhan@linuxfoundation.org>, Shuah Khan <shuah@kernel.org>
Cc: Aleksa Sarai <cyphar@cyphar.com>,
	Christian Brauner <brauner@kernel.org>,
	linux-kselftest@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests: proc: include fcntl.h in proc-pidns
Date: Thu, 18 Jun 2026 19:42:40 +0330	[thread overview]
Message-ID: <e5d05ae5-3b3c-48ad-8f91-c8461a77ff75@aminvakil.com> (raw)
In-Reply-To: <16ef9ff1-4c98-4c89-aefa-734a9e775df2@linuxfoundation.org>


[-- Attachment #1.1.1: Type: text/plain, Size: 3062 bytes --]

On 6/18/26 6:54 PM, Shuah Khan wrote:
> On 6/18/26 09:14, Amin Vakil wrote:
>> proc-pidns.c uses open() and O_* flags, but does not include
>> <fcntl.h>. This breaks the proc selftests build with errors such as:
>>
>>    error: implicit declaration of function 'open'
>>    error: 'O_WRONLY' undeclared
>>    error: 'O_CREAT' undeclared
>>    error: 'O_RDONLY' undeclared
>>
>> Include <fcntl.h> to provide the declaration and flag definitions.
> 
> Did you install headers before compiling the test?

Sorry, no I hadn't.

But seems like problem is still relevant after make headers, I've tested 
now with these commands:

make -C tools/testing/selftests TARGETS=proc clean
make headers
make -C tools/testing/selftests TARGETS=proc
   CC       proc-pidns
proc-pidns.c: In function ‘touch’:
proc-pidns.c:34:18: error: implicit declaration of function ‘open’; did 
you mean ‘popen’? [-Wimplicit-function-declaration]
    34 |         int fd = open(path, O_WRONLY|O_CREAT|O_CLOEXEC, 0644);
       |                  ^~~~
       |                  popen
proc-pidns.c:34:29: error: ‘O_WRONLY’ undeclared (first use in this 
function)
    34 |         int fd = open(path, O_WRONLY|O_CREAT|O_CLOEXEC, 0644);
       |                             ^~~~~~~~
proc-pidns.c:34:29: note: each undeclared identifier is reported only 
once for each function it appears in
proc-pidns.c:34:38: error: ‘O_CREAT’ undeclared (first use in this function)
    34 |         int fd = open(path, O_WRONLY|O_CREAT|O_CLOEXEC, 0644);
       |                                      ^~~~~~~
proc-pidns.c: In function ‘ns_setup’:
proc-pidns.c:49:54: error: ‘O_RDONLY’ undeclared (first use in this 
function); did you mean ‘MS_RDONLY’?
    49 |         self->host_mntns = open("/proc/self/ns/mnt", 
O_RDONLY|O_CLOEXEC);
       |                                                      ^~~~~~~~
       |                                                      MS_RDONLY

After applying the patch I've sent, error is gone.

My environment if relevant:
$ gcc --version
gcc (GCC) 16.1.1 20260430
$ make --version
GNU Make 4.4.1
Built for x86_64-pc-linux-gnu
$ ldd --version
ldd (GNU libc) 2.43
$ getconf GNU_LIBC_VERSION
glibc 2.43
> 
>>
>> Fixes: 5554d820f71c ("selftests/proc: add tests for new pidns APIs")
>> Tested with:
>>    make -C tools/testing/selftests TARGETS=proc
>>
>> Signed-off-by: Amin Vakil <info@aminvakil.com>
>> ---
>>   tools/testing/selftests/proc/proc-pidns.c | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/tools/testing/selftests/proc/proc-pidns.c b/tools/ 
>> testing/selftests/proc/proc-pidns.c
>> index 25b9a2933c45..6f7c10fe97b3 100644
>> --- a/tools/testing/selftests/proc/proc-pidns.c
>> +++ b/tools/testing/selftests/proc/proc-pidns.c
>> @@ -6,6 +6,7 @@
>>   #include <assert.h>
>>   #include <errno.h>
>> +#include <fcntl.h>
>>   #include <sched.h>
>>   #include <stdbool.h>
>>   #include <stdlib.h>
> 
> thanks,
> -- Shuah


[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2493 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 665 bytes --]

  reply	other threads:[~2026-06-18 16:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-18 15:14 Amin Vakil
2026-06-18 15:24 ` Shuah Khan
2026-06-18 16:12   ` Amin Vakil [this message]
2026-06-23 10:13 ` Christian Brauner
2026-06-29 14:47   ` Amin Vakil

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=e5d05ae5-3b3c-48ad-8f91-c8461a77ff75@aminvakil.com \
    --to=info@aminvakil.com \
    --cc=brauner@kernel.org \
    --cc=cyphar@cyphar.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=skhan@linuxfoundation.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®