From: Eric Biggers <ebiggers@kernel.org>
To: fsverity@lists.linux.dev
Cc: linux-fsdevel@vger.kernel.org,
linux-security-module@vger.kernel.org,
Andrey Albershteyn <aalbersh@kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] fsverity: Explicitly require FMODE_READ to retrieve hashes
Date: Wed, 28 Oct 2026 11:06:12 -0700 [thread overview]
Message-ID: <20261028180612.GA1876@quark> (raw)
In-Reply-To: <20261022211522.1489943-1-ebiggers@kernel.org>
On Thu, Oct 22, 2026 at 09:15:22PM +0000, Eric Biggers wrote:
> Therefore, just disallow these ioctls on ioctl-only file descriptors,
> similar to what was already done with FS_IOC_ENABLE_VERITY.
Applied to https://git.kernel.org/pub/scm/fs/fsverity/linux.git/log/?h=for-current
Acks from the LSM maintainers would be appreciated as well, given that
this patch fixes the interaction with certain LSMs.
- Eric
prev parent reply other threads:[~2026-10-28 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 21:15 [PATCH] fsverity: Explicitly require FMODE_READ to retrieve hashes Eric Biggers
2026-10-22 21:18 ` sashiko-bot
2026-10-26 13:36 ` Andrey Albershteyn
2026-10-28 18:06 ` Eric Biggers [this message]
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=20261028180612.GA1876@quark \
--to=ebiggers@kernel.org \
--cc=aalbersh@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--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