[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1903709.1661849345@warthog.procyon.org.uk>
Date: Tue, 30 Aug 2022 09:49:05 +0100
From: David Howells <dhowells@...hat.com>
To: Casey Schaufler <casey@...aufler-ca.com>
Cc: dhowells@...hat.com, Christian Brauner <brauner@...nel.org>,
viro@...iv.linux.org.uk, Jeff Layton <jlayton@...nel.org>,
Trond Myklebust <trond.myklebust@...merspace.com>,
Anna Schumaker <anna@...nel.org>,
Scott Mayhew <smayhew@...hat.com>,
Paul Moore <paul@...l-moore.com>, linux-nfs@...r.kernel.org,
selinux@...r.kernel.org, linux-security-module@...r.kernel.org,
linux-fsdevel@...r.kernel.org, dwysocha@...hat.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4] vfs, security: Fix automount superblock LSM init problem, preventing NFS sb sharing
Casey Schaufler <casey@...aufler-ca.com> wrote:
> The authors of this version of the mount code failed to look
> especially closely at how Smack maintains label names. Once a
> label name is used in the kernel it is kept on a list forever.
> All the copies of smk_known here and in the rest of the mount
> infrastructure are unnecessary and wasteful. The entire set of
> Smack hooks that deal with mounting need to be reworked to remove
> that waste. It's on my list of Smack cleanups, but I'd be happy
> if someone else wanted a go at it.
I don't have time to overhaul Smack right now. Should I drop the Smack part
of the patch?
David
Powered by blists - more mailing lists