[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJfpeguZq-1C_hnCcyrW3MCcpP4Bwe+L4gpWaOeJCqa1q8j4Hg@mail.gmail.com>
Date: Fri, 19 Jun 2015 09:52:55 +0200
From: Miklos Szeredi <miklos@...redi.hu>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: David Howells <dhowells@...hat.com>, sds@...ho.nsa.gov,
Linux-Fsdevel <linux-fsdevel@...r.kernel.org>,
linux-security-module@...r.kernel.org,
"linux-unionfs@...r.kernel.org" <linux-unionfs@...r.kernel.org>,
Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/8] Security: Provide unioned file support
On Fri, Jun 19, 2015 at 9:20 AM, Al Viro <viro@...iv.linux.org.uk> wrote:
> On Thu, Jun 18, 2015 at 02:32:15PM +0100, David Howells wrote:
>>
>> The attached patches provide security support for unioned files where the
>> security involves an object-label-based LSM (such as SELinux) rather than a
>> path-based LSM.
>>
>> The patches can be broken down into a number of sets:
>>
>> (1) A small patch to drop a lock earlier in overlayfs. The main VFS patch
>> touches the same code, so I put this first.
>>
>> (2) The main VFS patch that makes an open file struct referring to a union
>> file have ->f_path point to the union/overlay file whilst ->f_inode and
>> ->f_mapping refer to the subordinate file that does the actual work.
>
> #1 and #2 applied, will be in tomorrow vfs.git#for-next
Brave.
What's going to happen to all those f_path.dentry uses where the
filesystem thinks it's getting its own dentry?
> git grep f_path.dentry | wc -l
171
Thanks,
Miklos
--
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/
Powered by blists - more mailing lists