From: Eric Biggers <ebiggers@kernel.org>
To: Christian Brauner <brauner@kernel.org>
Cc: fsverity@lists.linux.dev,
Andrey Albershteyn <aalbersh@kernel.org>,
linux-fsdevel@vger.kernel.org,
"Darrick J. Wong" <djwong@kernel.org>
Subject: Re: [PATCH v3 0/2] Add traces and file attributes for fs-verity
Date: Thu, 29 Jan 2026 09:40:15 -0800 [thread overview]
Message-ID: <20260129174015.GA2240@sol> (raw)
In-Reply-To: <20260129-beieinander-klein-bcbb23eb6c7b@brauner>
On Thu, Jan 29, 2026 at 04:01:29PM +0100, Christian Brauner wrote:
> On Mon, 26 Jan 2026 12:56:56 +0100, Andrey Albershteyn wrote:
> > This two small patches grew from fs-verity XFS patchset. I think they're
> > self-contained improvements which could go without XFS implementation.
> >
> > Cc: linux-fsdevel@vger.kernel.org
> > Cc: "Darrick J. Wong" <djwong@kernel.org>
> >
> > v3:
> > - Make tracepoints arguments more consistent
> > - Make tracepoint messages more consistent
> > v2:
> > - Update kernel version in the docs to v7.0
> > - Move trace point before merkle tree block hash check
> > - Update commit message in patch 2
> > - Add VERITY to FS_COMMON_FL and FS_XFLAG_COMMON constants
> > - Fix block index argument in the tree block hash trace point
> >
> > [...]
>
> Applied to the vfs-7.0.misc branch of the vfs/vfs.git tree.
> Patches in the vfs-7.0.misc branch should appear in linux-next soon.
>
> Please report any outstanding bugs that were missed during review in a
> new review to the original patch series allowing us to drop it.
>
> It's encouraged to provide Acked-bys and Reviewed-bys even though the
> patch has now been applied. If possible patch trailers will be updated.
>
> Note that commit hashes shown below are subject to change due to rebase,
> trailer updates or similar. If in doubt, please check the listed branch.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
> branch: vfs-7.0.misc
>
> [1/2] fs: add FS_XFLAG_VERITY for fs-verity files
> https://git.kernel.org/vfs/vfs/c/0e6b7eae1fde
> [2/2] fsverity: add tracepoints
> https://git.kernel.org/vfs/vfs/c/fa19d42cc791
I guess this means you want me to drop them. So, dropped now.
- Eric
next prev parent reply other threads:[~2026-01-29 17:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 11:56 [PATCH v3 0/2] Add traces and file attributes for fs-verity Andrey Albershteyn
2026-01-26 11:56 ` [PATCH v3 1/2] fs: add FS_XFLAG_VERITY for fs-verity files Andrey Albershteyn
2026-01-26 11:56 ` [PATCH v3 2/2] fsverity: add tracepoints Andrey Albershteyn
2026-01-26 19:33 ` Eric Biggers
2026-01-26 19:28 ` [PATCH v3 0/2] Add traces and file attributes for fs-verity Eric Biggers
2026-01-29 15:01 ` Christian Brauner
2026-01-29 17:40 ` Eric Biggers [this message]
2026-02-03 14:16 ` Christian Brauner
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=20260129174015.GA2240@sol \
--to=ebiggers@kernel.org \
--cc=aalbersh@kernel.org \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=linux-fsdevel@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.