[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5346EDE8.2060004@amacapital.net>
Date: Thu, 10 Apr 2014 12:15:52 -0700
From: Andy Lutomirski <luto@...capital.net>
To: Colin Walters <walters@...bum.org>, tytso@....edu
CC: David Herrmann <dh.herrmann@...il.com>,
linux-kernel@...r.kernel.org, Hugh Dickins <hughd@...gle.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
Matthew Wilcox <matthew@....cx>,
Karol Lewandowski <k.lewandowsk@...sung.com>,
Kay Sievers <kay@...y.org>, Daniel Mack <zonque@...il.com>,
Lennart Poettering <lennart@...ttering.net>,
Kristian@...nk.org, john.stultz@...aro.org,
Greg Kroah-Hartman <greg@...ah.com>, Tejun Heo <tj@...nel.org>,
Johannes Weiner <hannes@...xchg.org>,
dri-devel@...ts.freedesktop.org, linux-fsdevel@...r.kernel.org,
linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Ryan Lortie <desrt@...rt.ca>, mtk.manpages@...il.com
Subject: Re: [PATCH 0/6] File Sealing & memfd_create()
On 04/10/2014 07:45 AM, Colin Walters wrote:
> On Thu, Mar 20, 2014 at 11:32 AM, tytso@....edu wrote:
>>
>> Looking at your patches, and what files you are modifying, you are
>> enforcing this in the low-level file system.
>
> I would love for this to be implemented in the filesystem level as
> well. Something like the ext4 immutable bit, but with the ability to
> still make hardlinks would be *very* useful for OSTree. And anyone else
> that uses hardlinks as a data source. The vserver people do something
> similiar:
> http://linux-vserver.org/util-vserver:Vhashify
>
> At the moment I have a read-only bind mount over /usr, but what I really
> want is to make the individual objects in the object store in
> /ostree/repo/objects be immutable, so even if a user or app navigates
> out to /sysroot they still can't mutate them (or the link targets in the
> visible /usr).
COW links can do this already, I think. Of course, you'll have to use a
filesystem that supports them.
--Andy
--
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