public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: Fangrui Song <maskray@google.com>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	libc-alpha@sourceware.org
Subject: Re: [PATCH v7 1/5] linux: Add fsconfig
Date: Mon, 11 Jul 2022 10:47:31 -0400	[thread overview]
Message-ID: <f551fafe-8bad-d1e8-6f99-877b614b46e6@redhat.com> (raw)
In-Reply-To: <20220711081624.ws7lhii2baq7efoe@google.com>

On 7/11/22 04:16, Fangrui Song wrote:
> On 2022-07-04, Carlos O'Donell via Libc-alpha wrote:
>> On 6/24/22 15:59, Adhemerval Zanella wrote:
>>> It was added on Linux 5.2 (ecdab150fddb42fe6a739335257949220033b782)
>>> as a way to a configure filesystem creation context and trigger
>>> actions upon it, to be used in conjunction with fsopen, fspick and
>>> fsmount.
>>>
>>> The fsconfig_command commands are currently only defined as an enum,
>>> so they can't be checked on tst-mount-consts.py with current test
>>> support.
>>
>> LGTM. API uses const void * correctly and syscall wrapper signature matches.
>>
>> Reviewed-by: Carlos O'Donell <carlos@redhat.com>
> 
> https://sourceware.org/glibc/wiki/Synchronizing_Headers can be updated that
> 
>     #include <sys/mount.h>
>     #include <linux/mount.h>
> 
> no longer works. This led to a compiler-rt build failure which I am
> going to fix in https://reviews.llvm.org/D129471 (llvm-project 15.0 will be branched soon
> https://discourse.llvm.org/t/llvm-15-0-0-release-schedule/63495)
> 
> Note:
> 
>     #include <linux/mount.h>
>     #include <sys/mount.h>
> 
> doesn't work for a long time
> 
>     /usr/include/x86_64-linux-gnu/sys/mount.h:35:3: error: expected identifier before numeric constant
>        35 |   MS_RDONLY = 1,                /* Mount read-only.  */
>           |   ^~~~~~~~~
> 

I added the known conflict to the wiki. Thanks.

-- 
Cheers,
Carlos.


  reply	other threads:[~2022-07-11 14:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24 19:59 [PATCH v7 0/5] linux: Add new syscalls Adhemerval Zanella
2022-06-24 19:59 ` [PATCH v7 1/5] linux: Add fsconfig Adhemerval Zanella
2022-07-04 21:36   ` Carlos O'Donell
2022-07-11  8:16     ` Fangrui Song
2022-07-11 14:47       ` Carlos O'Donell [this message]
2022-06-24 19:59 ` [PATCH v7 2/5] linux: Add fspick Adhemerval Zanella
2022-07-04 21:39   ` Carlos O'Donell
2022-06-24 19:59 ` [PATCH v7 3/5] linux: Add open_tree Adhemerval Zanella
2022-07-04 21:42   ` Carlos O'Donell
2022-06-24 19:59 ` [PATCH v7 4/5] linux: Add tst-mount to check for Linux new mount API Adhemerval Zanella
2022-07-04 21:45   ` Carlos O'Donell
2022-06-24 19:59 ` [PATCH v7 5/5] linux: Add mount_setattr Adhemerval Zanella
2022-07-04 21:51   ` Carlos O'Donell
2022-07-06  9:25     ` Andreas Schwab
2022-07-06 12:21       ` Adhemerval Zanella
2022-07-10  2:28         ` Rudi Heitbaum
2022-07-11 12:51           ` Adhemerval Zanella
2022-07-11 13:13             ` Rudi Heitbaum
2022-07-12 13:11               ` Rudi Heitbaum
2022-07-12 15:33                 ` Adhemerval Zanella Netto
2022-07-11  8:30         ` Andreas Schwab
2022-07-11  8:55         ` Florian Weimer
2022-07-11 12:49           ` Adhemerval Zanella
2022-07-11 12:53             ` Florian Weimer
2022-07-25 15:08               ` Andreas Schwab
2022-07-26  0:28                 ` Rudi Heitbaum

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=f551fafe-8bad-d1e8-6f99-877b614b46e6@redhat.com \
    --to=carlos@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.org \
    --cc=maskray@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).