linux-kernel - Re: [PATCH v2 1/2] security: Add hook to invalidate inode security labels

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHc6FU7pcZ56HZ_ktDpQeCk9BFUrFen+Znp90HK3xgjtRVWUfQ@mail.gmail.com>
Date:	Mon, 5 Oct 2015 20:39:10 +0200
From:	Andreas Gruenbacher <agruenba@...hat.com>
To:	Casey Schaufler <casey@...aufler-ca.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	Alexander Viro <viro@...iv.linux.org.uk>,
	Christoph Hellwig <hch@...radead.org>,
	Paul Moore <paul@...l-moore.com>,
	Stephen Smalley <sds@...ho.nsa.gov>,
	Eric Paris <eparis@...isplace.org>, selinux@...ho.nsa.gov,
	LSM <linux-security-module@...r.kernel.org>
Subject: Re: [PATCH v2 1/2] security: Add hook to invalidate inode security labels

On Mon, Oct 5, 2015 at 8:24 PM, Casey Schaufler <casey@...aufler-ca.com> wrote:
> On 10/4/2015 12:19 PM, Andreas Gruenbacher wrote:
>> Add a hook to invalidate an inode's security label when the cached
>> information becomes invalid.
>
> Where is this used?

See the next patch in this patch queue, gfs2.

> If I need to do the same for Smack or any other module, how would I know that
> it works right?

I haven't looked at Smack but if it does the same thing as SELinux,
then label updates on one gfs2 nod ein a cluster won't become visible
on other nodes without this fix, and with this fix they will.

Andreas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/