From: Christoph Hellwig <hch@lst.de>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Andrey Albershteyn <aalbersh@kernel.org>,
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: Thu, 5 Nov 2026 08:52:44 +0100 [thread overview]
Message-ID: <20261105075244.GB17923@lst.de> (raw)
In-Reply-To: <20261104215749.GA3648616@google.com>
On Wed, Nov 04, 2026 at 09:57:49PM +0000, Eric Biggers wrote:
> Changes to 'struct inode' should be Cc'ed to linux-fsdevel as well.
Yes. Except for that and the two btrfs/f2fs issue reported by Sashiko
this looks sane. Please try to do a full fsverity xfstests run for
all the touched file systems.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Eric Biggers <ebiggers@kernel.org>
Cc: fsverity@lists.linux.dev,
Andrey Albershteyn <aalbersh@kernel.org>,
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: Thu, 5 Nov 2026 08:52:44 +0100 [thread overview]
Message-ID: <20261105075244.GB17923@lst.de> (raw)
In-Reply-To: <20261104215749.GA3648616@google.com>
On Wed, Nov 04, 2026 at 09:57:49PM +0000, Eric Biggers wrote:
> Changes to 'struct inode' should be Cc'ed to linux-fsdevel as well.
Yes. Except for that and the two btrfs/f2fs issue reported by Sashiko
this looks sane. Please try to do a full fsverity xfstests run for
all the touched file systems.
_______________________________________________
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-05 7:52 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 ` [PATCH 0/5] fsverity: lift ioctl() input masking and runtime inode flag to VFS Eric Biggers
2026-11-04 21:57 ` [f2fs-dev] " Eric Biggers via Linux-f2fs-devel
2026-11-05 7:52 ` Christoph Hellwig [this message]
2026-11-05 7:52 ` 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=20261105075244.GB17923@lst.de \
--to=hch@lst.de \
--cc=aalbersh@kernel.org \
--cc=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--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.