From: sashiko-bot@kernel.org
To: "Cai Xinchen" <caixinchen1@huawei.com>
Cc: selinux@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH v2 stable/linux-6.6.y 1/3] fs: prepare for adding LSM blob to backing_file
Date: Sat, 27 Jun 2026 06:34:25 +0000 [thread overview]
Message-ID: <20260627063425.D38E41F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260627065720.1945589-2-caixinchen1@huawei.com>
> From: Amir Goldstein <amir73il@gmail.com>
>
> [ Upstream commit 880bd496ec72a6dcb00cb70c430ef752ba242ae7 ]
>
> In preparation to adding LSM blob to backing_file struct, factor out
> helpers init_backing_file() and backing_file_free().
>
> Cc: stable@vger.kernel.org
> Cc: linux-fsdevel@vger.kernel.org
> Cc: linux-unionfs@vger.kernel.org
> Cc: linux-erofs@lists.ozlabs.org
> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
> Reviewed-by: Serge Hallyn <serge@hallyn.com>
> [PM: use the term "LSM blob", fix comment style to match file]
> Signed-off-by: Paul Moore <paul@paul-moore.com>
> [1. The commit def3ae83da02
> ("fs: store real path instead of fake path in backing file f_path")
> is not merged, The 6.6 LTS version accordingly operates on
> &ff->real_path instead of &ff->user_path.
>
> 2. Mainline's file_free() does both the backing_file cleanup and the
> kmem_cache_free() synchronously. Linux 6.6.y defers the actual kfree()
> to file_free_rcu() via call_rcu(), so only path_put() is done
> synchronously in file_free().]
> Signed-off-by: Cai Xinchen <caixinchen1@huawei.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260627065720.1945589-1-caixinchen1@huawei.com?part=1
next prev parent reply other threads:[~2026-06-27 6:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-27 6:57 [PATCH v2 stable/linux-6.6.y 0/3] Backport Fix incorrect overlayfs mmap() and mprotect() LSM access controls Cai Xinchen
2026-06-27 6:57 ` [PATCH v2 stable/linux-6.6.y 1/3] fs: prepare for adding LSM blob to backing_file Cai Xinchen
2026-06-27 6:34 ` sashiko-bot [this message]
2026-06-27 6:57 ` [PATCH v2 stable/linux-6.6.y 2/3] lsm: add backing_file LSM hooks Cai Xinchen
2026-06-27 6:41 ` sashiko-bot
2026-06-27 6:57 ` [PATCH v2 stable/linux-6.6.y 3/3] selinux: fix overlayfs mmap() and mprotect() access checks Cai Xinchen
2026-06-27 6:36 ` sashiko-bot
2026-06-28 3:33 ` [PATCH v2 stable/linux-6.6.y 0/3] Backport Fix incorrect overlayfs mmap() and mprotect() LSM access controls Sasha Levin
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=20260627063425.D38E41F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=caixinchen1@huawei.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=selinux@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