[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1397159378.4434.1@mail.messagingengine.com>
Date: Thu, 10 Apr 2014 19:45:38 +0000
From: Colin Walters <walters@...bum.org>
To: Andy Lutomirski <luto@...capital.net>
Cc: tytso@....edu, 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 Thu, Apr 10, 2014 at 3:15 PM, Andy Lutomirski <luto@...capital.net>
wrote:
>
>
> COW links can do this already, I think. Of course, you'll have to
> use a
> filesystem that supports them.
COW is nice if the filesystem supports them, but my userspace code
needs to be filesystem agnostic. Because of that, the design for
userspace simply doesn't allow arbitrary writes.
Instead, I have to painfully audit every rpm %post/dpkg postinst type
script to ensure they break hardlinks, and furthermore only allow
executing scripts that are known to do so.
But I think even in a btrfs world it'd still be useful to mark files as
content-immutable.
--
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