[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150417143640.GB3671@codeblueprint.co.uk>
Date: Fri, 17 Apr 2015 15:36:40 +0100
From: Matt Fleming <matt@...eblueprint.co.uk>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: "Kweh, Hock Leong" <hock.leong.kweh@...el.com>,
Ming Lei <ming.lei@...onical.com>,
"Ong, Boon Leong" <boon.leong.ong@...el.com>,
LKML <linux-kernel@...r.kernel.org>,
"linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
Sam Protsenko <semen.protsenko@...aro.org>,
Peter Jones <pjones@...hat.com>,
Andy Lutomirski <luto@...capital.net>,
Roy Franz <roy.franz@...aro.org>,
Borislav Petkov <bp@...en8.de>
Subject: Re: [PATCH v4 2/2] efi: an sysfs interface for user to update efi
firmware
On Fri, 17 Apr, at 03:49:24PM, Greg KH wrote:
>
> Not really, the kernel namespace is what matters at that point in time.
>
> And maybe it does matter, I haven't thought through all of the issues.
> But passing a path from userspace, to the kernel, to have the kernel
> turn around again and use that path is full of nasty consequences at
> times due to namespaces, let's avoid all of that please.
Oh crap. The namespace issue is a good point and not something I'd
thought of at all.
At this point, I think we've really run out of objections to Andy's
suggestion of implementing this as a misc device, right?
The concern I had about userspace tooling can partly be addressed by
including the source in tools/ in the kernel tree. So provided we do
that, I'm happy enough to see this implemented as a misc device because
the other options we've explored just haven't panned out.
Objections?
--
Matt Fleming, Intel Open Source Technology Center
--
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