All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Andrey Albershteyn <aalbersh@kernel.org>
Cc: fsverity@lists.linux.dev, 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: Mon, 26 Jan 2026 11:28:42 -0800	[thread overview]
Message-ID: <20260126192842.GA2305@quark> (raw)
In-Reply-To: <20260126115658.27656-1-aalbersh@kernel.org>

On Mon, Jan 26, 2026 at 12:56:56PM +0100, Andrey Albershteyn wrote:
> Hi all,
> 
> 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
> 
> Andrey Albershteyn (2):
>   fs: add FS_XFLAG_VERITY for fs-verity files
>   fsverity: add tracepoints

Applied to https://git.kernel.org/pub/scm/fs/fsverity/linux.git/log/?h=for-next

Thanks!

- Eric

  parent reply	other threads:[~2026-01-26 19:28 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 ` Eric Biggers [this message]
2026-01-29 15:01 ` [PATCH v3 0/2] Add traces and file attributes for fs-verity Christian Brauner
2026-01-29 17:40   ` Eric Biggers
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=20260126192842.GA2305@quark \
    --to=ebiggers@kernel.org \
    --cc=aalbersh@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.