From: Eric Biggers <ebiggers@kernel.org>
To: stable@vger.kernel.org
Cc: fsverity@lists.linux.dev, Eric Biggers <ebiggers@kernel.org>
Subject: [PATCH 5.10 0/2] Backport additional ->get_verity_descriptor() checks
Date: Sat, 7 Nov 2026 11:44:43 -0800 [thread overview]
Message-ID: <20261107194445.55959-1-ebiggers@kernel.org> (raw)
Backport "fsverity: Be more careful with return value of
->get_verity_descriptor()" to 5.10. Easist way to do it was to backport
"fs-verity: factor out fsverity_get_descriptor()" first. Both are clean
cherry-picks.
Eric Biggers (2):
fs-verity: factor out fsverity_get_descriptor()
fsverity: Be more careful with return value of ->get_verity_descriptor()
fs/verity/fsverity_private.h | 7 +-
fs/verity/open.c | 148 ++++++++++++++++++++++-------------
2 files changed, 100 insertions(+), 55 deletions(-)
base-commit: 3a323bc22b881a5bdc1646080f93f5ecb22850bf
--
2.56.0
next reply other threads:[~2026-11-07 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 19:44 Eric Biggers [this message]
2026-11-07 19:44 ` [PATCH 5.10 1/2] fs-verity: factor out fsverity_get_descriptor() Eric Biggers
2026-11-07 19:44 ` [PATCH 5.10 2/2] fsverity: Be more careful with return value of ->get_verity_descriptor() 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=20261107194445.55959-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox