public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>,
	 Andreas Schwab <schwab@suse.de>
Subject: Re: [PATCH v7 5/5] linux: Add mount_setattr
Date: Mon, 11 Jul 2022 14:53:54 +0200	[thread overview]
Message-ID: <87sfn73j4t.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <46921EC3-6197-4188-B5C4-F241DE6C1D8F@linaro.org> (Adhemerval Zanella's message of "Mon, 11 Jul 2022 09:49:46 -0300")

* Adhemerval Zanella:

>> On 11 Jul 2022, at 05:55, Florian Weimer <fweimer@redhat.com> wrote:
>> 
>> * Adhemerval Zanella via Libc-alpha:
>> 
>>> I am not sure how to handle it, glibc sys/mount.h should be a standalone
>>> header.
>> 
>> Is it really necessary to keep <sys/mount.h> standalone?  It's not even
>> a standard interface, and we don't have conform tests for this header as
>> far as I can see.
>> 
>> So I think the usual __has_include approach should work here, too.
>
> The main problem is sys/mount.h defines interfaces for syscall added
> in multiple releases.  It means that depending of the kernel version
> used by the compiler we will need to add some defines (for instance
> fsconfig_command).  There is also a small difference where glibc
> header define the MS_* constant as a unnamed enum (not sure if this
> affects C++ mangling).

You are right, I had missed that.

> I know that using kernel headers simplify some support, specially sync
> with newer releases; but this also adds more complexity where we need
> to handle integration outside glibc project.

For openat2, we got a separate header.  Maybe we can request that for
the fsmount interfaces, too?  Than we can do the usual thing just for
<linux/fsmount.h>.  <linux/mount.h> can still include <linux/fsmount.h>,
so the change would be transparent.

Thanks,
Florian


  reply	other threads:[~2022-07-11 12:53 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
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 [this message]
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=87sfn73j4t.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.org \
    --cc=schwab@suse.de \
    /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).