From: Al Viro <viro@zeniv.linux.org.uk>
To: linux-security-module@vger.kernel.org
Cc: linux-integrity@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCHES][CFR][CFT] securityfs cleanups and fixes
Date: Wed, 25 Jun 2025 02:47:09 +0100 [thread overview]
Message-ID: <20250625014709.GQ1880847@ZenIV> (raw)
In-Reply-To: <20250612030951.GC1647736@ZenIV>
On Thu, Jun 12, 2025 at 04:09:51AM +0100, Al Viro wrote:
> Branch (6.16-rc1-based) lives in
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git #work.securityfs
> Individual patches in followups.
>
> Help with testing and review would be very welcome.
Seeing that no complaints have materialized, into -next it goes (with
Acked-by/Tested-by attached)...
next prev parent reply other threads:[~2025-06-25 1:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 3:09 [PATCHES][CFR][CFT] securityfs cleanups and fixes Al Viro
2025-06-12 3:11 ` [PATCH 01/10] securityfs: don't pin dentries twice, once is enough Al Viro
2025-06-12 3:11 ` [PATCH 02/10] securityfs: pin filesystem only for objects directly in root Al Viro
2025-06-12 3:11 ` [PATCH 03/10] fix locking in efi_secret_unlink() Al Viro
2025-06-12 3:11 ` [PATCH 04/10] make securityfs_remove() remove the entire subtree Al Viro
2025-06-12 3:11 ` [PATCH 05/10] efi_secret: clean securityfs use up Al Viro
2025-06-12 3:11 ` [PATCH 06/10] ima_fs: don't bother with removal of files in directory we'll be removing Al Viro
2025-06-17 18:42 ` Mimi Zohar
2025-06-12 3:11 ` [PATCH 07/10] ima_fs: get rid of lookup-by-dentry stuff Al Viro
2025-06-17 18:42 ` Mimi Zohar
2025-06-12 3:11 ` [PATCH 08/10] evm_secfs: clear securityfs interactions Al Viro
2025-06-17 19:49 ` Mimi Zohar
2025-06-12 3:11 ` [PATCH 09/10] ipe: don't bother with removal of files in directory we'll be removing Al Viro
2025-06-12 17:43 ` Fan Wu
2025-06-24 23:49 ` Fan Wu
2025-06-12 3:11 ` [PATCH 10/10] tpm: " Al Viro
2025-06-25 1:47 ` Al Viro [this message]
2025-06-25 2:07 ` [PATCHES][CFR][CFT] securityfs cleanups and fixes Paul Moore
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=20250625014709.GQ1880847@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-security-module@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;
as well as URLs for NNTP newsgroup(s).