[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4E92753A-04BD-4018-A3A4-5E3E4242D8B9@zytor.com>
Date: Sun, 12 May 2019 03:18:16 -0700
From: hpa@...or.com
To: Dominik Brodowski <linux@...inikbrodowski.net>,
Roberto Sassu <roberto.sassu@...wei.com>
CC: viro@...iv.linux.org.uk, linux-security-module@...r.kernel.org,
linux-integrity@...r.kernel.org, initramfs@...r.kernel.org,
linux-api@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, zohar@...ux.vnet.ibm.com,
silviu.vlasceanu@...wei.com, dmitry.kasatkin@...wei.com,
takondra@...co.com, kamensky@...co.com, arnd@...db.de,
rob@...dley.net, james.w.mcmechan@...il.com
Subject: Re: [PATCH v2 0/3] initramfs: add support for xattrs in the initial ram disk
On May 12, 2019 2:17:48 AM PDT, Dominik Brodowski <linux@...inikbrodowski.net> wrote:
>On Thu, May 09, 2019 at 01:24:17PM +0200, Roberto Sassu wrote:
>> This proposal consists in marshaling pathnames and xattrs in a file
>called
>> .xattr-list. They are unmarshaled by the CPIO parser after all files
>have
>> been extracted.
>
>Couldn't this parsing of the .xattr-list file and the setting of the
>xattrs
>be done equivalently by the initramfs' /init? Why is kernel involvement
>actually required here?
>
>Thanks,
> Dominik
There are a lot of things that could/should be done that way...
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Powered by blists - more mailing lists