All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrey Albershteyn <aalbersh@redhat.com>
To: fsverity@lists.linux.dev, ebiggers@kernel.org,
	aalbersh@kernel.org,  djwong@kernel.org
Subject: [PATCH 0/3] Add traces and file attributes for fs-verity
Date: Mon, 12 Jan 2026 13:13:35 +0100	[thread overview]
Message-ID: <cover.1768219885.patch-series@thinky> (raw)

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.

Andrey Albershteyn <aalbersh@kernel.org>:
  fs: add FS_XFLAG_VERITY for fs-verity files
  fsverity: add tracepoints

Diffstat:
  Documentation/filesystems/fsverity.rst |  16 ++++++++++++++++
  MAINTAINERS                            |   1 +
  fs/file_attr.c                         |   4 ++++
  fs/verity/enable.c                     |   4 ++++
  fs/verity/fsverity_private.h           |   2 ++
  fs/verity/init.c                       |   1 +
  fs/verity/verify.c                     |   9 +++++++++
  include/linux/fileattr.h               |   2 +-
  include/trace/events/fsverity.h        | 143 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
  include/uapi/linux/fs.h                |   1 +
  10 files changed, 182 insertions(+), 1 deletion(-)

-- 
- Andrey


             reply	other threads:[~2026-01-12 12:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-12 12:13 Andrey Albershteyn [this message]
2026-01-12 12:14 ` [PATCH 1/2] fs: add FS_XFLAG_VERITY for fs-verity files Andrey Albershteyn
2026-01-12 22:02   ` Darrick J. Wong
2026-01-13 10:07     ` Andrey Albershteyn
2026-01-17 23:15   ` Eric Biggers
2026-01-12 12:15 ` [PATCH 2/2] fsverity: add tracepoints Andrey Albershteyn
2026-01-17 23:33   ` Eric Biggers
2026-01-17 23:34 ` [PATCH 0/3] Add traces and file attributes for fs-verity Eric Biggers

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=cover.1768219885.patch-series@thinky \
    --to=aalbersh@redhat.com \
    --cc=aalbersh@kernel.org \
    --cc=djwong@kernel.org \
    --cc=ebiggers@kernel.org \
    --cc=fsverity@lists.linux.dev \
    /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.