linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Paul Moore <paul@paul-moore.com>
Cc: linux-fsdevel@vger.kernel.org, torvalds@linux-foundation.org,
	brauner@kernel.org, jack@suse.cz, kees@kernel.org,
	casey@schaufler-ca.com, linux-security-module@vger.kernel.org,
	john.johansen@canonical.com
Subject: Re: [PATCH 31/39] convert selinuxfs
Date: Sun, 21 Sep 2025 22:41:10 +0100	[thread overview]
Message-ID: <20250921214110.GN39973@ZenIV> (raw)
In-Reply-To: <CAHC9VhTRsQtncKx4bkbkSqVXpZyQLHbvKkcaVO-ss21Fq36r+Q@mail.gmail.com>

On Sun, Sep 21, 2025 at 04:44:28PM -0400, Paul Moore wrote:
> > +       dput(dentry);
> > +       return dentry;  // borrowed
> >  }
> 
> Prefer C style comments on their own line:
> 
>   dput(dentry);
>   /* borrowed dentry */
>   return dentry;

Umm...  IMO that's more of an annotation along the lines of "fallthru"...

> > @@ -2079,15 +2088,14 @@ static int sel_fill_super(struct super_block *sb, struct fs_context *fc)
> >                 goto err;
> >         }
> >
> > -       fsi->policycap_dir = sel_make_dir(sb->s_root, POLICYCAP_DIR_NAME,
> > +       dentry = sel_make_dir(sb->s_root, POLICYCAP_DIR_NAME,
> >                                           &fsi->last_ino);
> 
> I'd probably keep fsi->policycap_dir in this patch simply to limit the
> scope of this patch to just the DCACHE_PERSISTENT related changes, but
> I'm not going to make a big fuss about that.

Not hard to split that way.  Will do...


BTW, an unrelated question: does userland care about selinuxfs /null being
called that (and being on selinuxfs, for that matter)?  Same for the
apparmor's securityfs /apparmor/.null...

If nobody cares, I would rather add an internal-only filesystem with
root being a character device (1,3) and whatever markings selinux et.al.
need for it.  With open_devnull(creds) provided for selinux,
apparmor and whoever else wants to play with neutering descriptors
on exec...

       reply	other threads:[~2025-09-21 21:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250920074156.GK39973@ZenIV>
     [not found] ` <20250920074759.3564072-1-viro@zeniv.linux.org.uk>
     [not found]   ` <20250920074759.3564072-31-viro@zeniv.linux.org.uk>
     [not found]     ` <CAHC9VhTRsQtncKx4bkbkSqVXpZyQLHbvKkcaVO-ss21Fq36r+Q@mail.gmail.com>
2025-09-21 21:41       ` Al Viro [this message]
2025-09-22  2:45         ` [PATCH 31/39] convert selinuxfs Paul Moore
2025-09-22 12:34           ` Stephen Smalley
2025-09-22 13:46             ` Al Viro
2025-09-22 21:12         ` John Johansen

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=20250921214110.GN39973@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=brauner@kernel.org \
    --cc=casey@schaufler-ca.com \
    --cc=jack@suse.cz \
    --cc=john.johansen@canonical.com \
    --cc=kees@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=torvalds@linux-foundation.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).