From: "Günther Noack" <gnoack3000@gmail.com>
To: "Mickaël Salaün" <mic@digikod.net>
Cc: "Günther Noack" <gnoack@google.com>,
"Christian Brauner" <brauner@kernel.org>,
linux-security-module@vger.kernel.org,
"Paul Moore" <paul@paul-moore.com>,
"Amir Goldstein" <amir73il@gmail.com>,
"Miklos Szeredi" <miklos@szeredi.hu>,
"Serge Hallyn" <serge@hallyn.com>,
"Stephen Smalley" <stephen.smalley.work@gmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v5 2/5] landlock: Require LANDLOCK_ACCESS_FS_MAKE_REG for whiteout creation
Date: Wed, 12 Aug 2026 21:48:51 +0200 [thread overview]
Message-ID: <20260812.ebb43b3e31d6@gnoack.org> (raw)
In-Reply-To: <20260731.Shalee5tiiki@digikod.net>
On Fri, Jul 31, 2026 at 11:35:14PM +0200, Mickaël Salaün wrote:
> On Fri, Jul 31, 2026 at 05:43:50PM +0200, Günther Noack wrote:
> > +static __attribute_const__ access_mask_t
>
> The __attribute_const__ is incorrect here, you can just drop it.
Thanks, will address.
> > +get_dentry_access(const struct dentry *const dentry)
> > +{
>
> const struct inode *const inode = d_backing_inode(dentry);
Done.
-Günther
next prev parent reply other threads:[~2026-08-12 19:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 15:43 [PATCH v5 0/5] landlock: Restrict whiteout object creation Günther Noack
2026-07-31 15:43 ` [PATCH v5 1/5] selftests/landlock: Use an actual chardev for MAKE_CHAR audit test Günther Noack
2026-07-31 15:43 ` [PATCH v5 2/5] landlock: Require LANDLOCK_ACCESS_FS_MAKE_REG for whiteout creation Günther Noack
2026-07-31 21:35 ` Mickaël Salaün
2026-08-12 19:48 ` Günther Noack [this message]
2026-07-31 15:43 ` [PATCH v5 3/5] selftests/landlock: Add tests for whiteout object creation Günther Noack
2026-07-31 15:43 ` [PATCH v5 4/5] selftests/landlock: Test whiteout object behaviour in OverlayFS renames Günther Noack
2026-07-31 15:43 ` [PATCH v5 5/5] landlock: Link the erratum documentation for whiteout objects Günther Noack
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=20260812.ebb43b3e31d6@gnoack.org \
--to=gnoack3000@gmail.com \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=gnoack@google.com \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=miklos@szeredi.hu \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=stable@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
/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