From: Eric Biggers <ebiggers@kernel.org>
To: Andrey Albershteyn <aalbersh@kernel.org>
Cc: hch@lst.de, fsverity@lists.linux.dev, linux-xfs@vger.kernel.org,
linux-btrfs@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH 0/5] fsverity: lift ioctl() input masking and runtime inode flag to VFS
Date: Wed, 4 Nov 2026 21:57:49 +0000 [thread overview]
Message-ID: <20261104215749.GA3648616@google.com> (raw)
In-Reply-To: <20261104194618.103332-1-aalbersh@kernel.org>
On Wed, Nov 04, 2026 at 08:46:09PM +0100, Andrey Albershteyn wrote:
> Hi folks,
>
> This patchset lifts two things from filesystems to VFS level:
> - No-oping FS_VERITY_FL in SET ioctl()
> - runtime fsverity construction flag
>
> The first one fixes BTRFS get-modify-set loop with
> FS_IOC_GETFLAGS/SETFLAGS ioctl()s, as it does return fsverity flag but
> not mask it out.
Changes to 'struct inode' should be Cc'ed to linux-fsdevel as well.
- Eric
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Andrey Albershteyn <aalbersh@kernel.org>
Cc: fsverity@lists.linux.dev, linux-f2fs-devel@lists.sourceforge.net,
linux-xfs@vger.kernel.org, linux-ext4@vger.kernel.org,
hch@lst.de, linux-btrfs@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH 0/5] fsverity: lift ioctl() input masking and runtime inode flag to VFS
Date: Wed, 4 Nov 2026 21:57:49 +0000 [thread overview]
Message-ID: <20261104215749.GA3648616@google.com> (raw)
In-Reply-To: <20261104194618.103332-1-aalbersh@kernel.org>
On Wed, Nov 04, 2026 at 08:46:09PM +0100, Andrey Albershteyn wrote:
> Hi folks,
>
> This patchset lifts two things from filesystems to VFS level:
> - No-oping FS_VERITY_FL in SET ioctl()
> - runtime fsverity construction flag
>
> The first one fixes BTRFS get-modify-set loop with
> FS_IOC_GETFLAGS/SETFLAGS ioctl()s, as it does return fsverity flag but
> not mask it out.
Changes to 'struct inode' should be Cc'ed to linux-fsdevel as well.
- Eric
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2026-11-04 21:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 19:46 [PATCH 0/5] fsverity: lift ioctl() input masking and runtime inode flag to VFS Andrey Albershteyn
2026-11-04 19:46 ` [f2fs-dev] " Andrey Albershteyn via Linux-f2fs-devel
2026-11-04 19:46 ` [PATCH 1/5] fsverity: strip FS_VERITY_FL from FS_IOC_SETFLAGS Andrey Albershteyn
2026-11-04 19:46 ` [f2fs-dev] " Andrey Albershteyn via Linux-f2fs-devel
2026-11-04 19:55 ` sashiko-bot
2026-11-04 19:46 ` [PATCH 2/5] fsverity: add I_VERITY_BUILDING inode state flag Andrey Albershteyn
2026-11-04 19:46 ` [f2fs-dev] " Andrey Albershteyn via Linux-f2fs-devel
2026-11-04 19:57 ` sashiko-bot
2026-11-04 19:46 ` [PATCH 3/5] btrfs: use I_VERITY_BUILDING instead of private flags Andrey Albershteyn
2026-11-04 19:46 ` [f2fs-dev] " Andrey Albershteyn via Linux-f2fs-devel
2026-11-04 20:00 ` sashiko-bot
2026-11-04 19:46 ` [PATCH 4/5] ext4: " Andrey Albershteyn
2026-11-04 19:46 ` [f2fs-dev] " Andrey Albershteyn via Linux-f2fs-devel
2026-11-04 20:01 ` sashiko-bot
2026-11-04 19:46 ` [PATCH 5/5] f2fs: " Andrey Albershteyn
2026-11-04 19:46 ` [f2fs-dev] " Andrey Albershteyn via Linux-f2fs-devel
2026-11-04 20:04 ` sashiko-bot
2026-11-05 9:54 ` Andrey Albershteyn
2026-11-04 21:57 ` Eric Biggers [this message]
2026-11-04 21:57 ` [f2fs-dev] [PATCH 0/5] fsverity: lift ioctl() input masking and runtime inode flag to VFS Eric Biggers via Linux-f2fs-devel
2026-11-05 7:52 ` Christoph Hellwig
2026-11-05 7:52 ` [f2fs-dev] " Christoph Hellwig
2026-11-05 10:56 ` Andrey Albershteyn
2026-11-05 10:56 ` [f2fs-dev] " Andrey Albershteyn via Linux-f2fs-devel
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=20261104215749.GA3648616@google.com \
--to=ebiggers@kernel.org \
--cc=aalbersh@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=hch@lst.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-xfs@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.