public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Rodrigo Campos <rodrigo@sdfg.com.ar>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] mount_setattr.2: Update supported file-systems
Date: Mon, 29 Apr 2024 12:31:43 +0200	[thread overview]
Message-ID: <Zi93EAyeU4byltGB@debian> (raw)
In-Reply-To: <b52c03a3-bc07-4358-aec4-9728f213d31e@sdfg.com.ar>

[-- Attachment #1: Type: text/plain, Size: 2609 bytes --]

Hi Rodrigo,

On Mon, Apr 29, 2024 at 11:19:36AM +0100, Rodrigo Campos wrote:
> On 4/17/24 1:02 PM, Alejandro Colomar wrote:
> > Hi Rodrigo,
> > 
> > On Tue, Apr 09, 2024 at 03:10:46PM +0100, Rodrigo Campos wrote:
> > > Let's update the list with the last file-systems that added support.

I've amended this: s/last/latest/

> > > You can easily verify this by "git grep FS_ALLOW_IDMAP" on the given Linux
> > > version to see that the fs is listed and then checkout the previous Linux
> > > version to see that it is not listed, therefore it was added in that version.
> > 
> > You could add the following to the commit message:
> > 
> > $ diff -w -U0 \
> > 	<(git grep FS_ALLOW_IDMAP v6.8 | sed 's/^v6.8://') \
> > 	<(git grep FS_ALLOW_IDMAP v6.9-rc4 | sed 's/^v6.9-rc4://') \
> > | tail -n+4;
> > +fs/hugetlbfs/inode.c:	.fs_flags               = FS_ALLOW_IDMAP,
> > 
> > $ diff -w -U0 \
> > 	<(git grep FS_ALLOW_IDMAP v6.6 | sed 's/^v6.6://') \
> > 	<(git grep FS_ALLOW_IDMAP v6.7 | sed 's/^v6.7://') \
> > | tail -n+4;
> > +fs/ceph/super.c:	.fs_flags	= FS_RENAME_DOES_D_MOVE | FS_ALLOW_IDMAP,
> > $ diff -w -U0 \
> > 	<(git grep FS_ALLOW_IDMAP v6.2 | sed 's/^v6.2://') \
> > 	<(git grep FS_ALLOW_IDMAP v6.3 | sed 's/^v6.3://') \
> > | tail -n+4;
> > +mm/shmem.c:	.fs_flags	= FS_USERNS_MOUNT | FS_ALLOW_IDMAP,
> > $ diff -w -U0 \
> > 	<(git grep FS_ALLOW_IDMAP v6.1 | sed 's/^v6.1://') \
> > 	<(git grep FS_ALLOW_IDMAP v6.2 | sed 's/^v6.2://') \
> > | tail -n+4;
> > +fs/squashfs/super.c:	.fs_flags = FS_REQUIRES_DEV | FS_ALLOW_IDMAP,
> 
> 
> Heh, nice trick. Do I need to resend for this or can you add it while you
> apply it?

I can.  :-)

> > > Signed-off-by: Rodrigo Campos <rodrigo@sdfg.com.ar>
> > > ---
> > > 
> > > I've took the liberty of adding hugetlbfs that was merged in Linux 6.9-rc1 but there is still no
> > > final release of 6.9. Please feel free to drop that if you prefer to wait for the final release to
> > > include it.
> > 
> > Are you confident that it will be in 6.9?  If so, I don't mind having it
> > already in the manual.
> 
> Yes. It's already rc6 and there was no issue reported for this, the patch is
> quite trivial too and was in linux-next before without issues either.

Okay.  I've applied the patch.  Thanks!
<https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=8ea186128f96d6f8912e05c95544734004618827>

Have a lovely day!
Alex

-- 
<https://www.alejandro-colomar.es/>
A client is hiring kernel driver, mm, and/or crypto developers;
contact me if interested.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-04-29 10:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-09 14:10 [PATCH] mount_setattr.2: Update supported file-systems Rodrigo Campos
2024-04-17 12:02 ` Alejandro Colomar
2024-04-29 10:19   ` Rodrigo Campos
2024-04-29 10:31     ` Alejandro Colomar [this message]
2024-05-21  9:08       ` Rodrigo Campos
2024-05-21 10:31         ` Alejandro Colomar
2024-05-21 10:53           ` Rodrigo Campos
2024-05-21 11:27             ` Alejandro Colomar
2024-05-21 11:49               ` Rodrigo Campos
2024-05-21 12:16                 ` Alejandro Colomar
2024-05-23  9:24                   ` Rodrigo Campos
2024-05-23 14:06                     ` Alejandro Colomar

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=Zi93EAyeU4byltGB@debian \
    --to=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=rodrigo@sdfg.com.ar \
    /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