Re: [PATCH v4 2/2] efi: an sysfs interface for user to update efi firmware

From: Andy Lutomirski <luto@amacapital.net>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Kweh, Hock Leong" <hock.leong.kweh@intel.com>,
	Matt Fleming <matt@codeblueprint.co.uk>,
	Ming Lei <ming.lei@canonical.com>,
	"Ong, Boon Leong" <boon.leong.ong@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
	Sam Protsenko <semen.protsenko@linaro.org>,
	Peter Jones <pjones@redhat.com>, Roy Franz <roy.franz@linaro.org>,
	Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH v4 2/2] efi: an sysfs interface for user to update efi firmware
Date: Tue, 21 Apr 2015 18:58:58 -0700	[thread overview]
Message-ID: <CALCETrX9GZmWnfkm-CwKW-2mPvRbNcRaY6tUY=8e0THsPBKMcA@mail.gmail.com> (raw)
In-Reply-To: <1429665679.2207.44.camel@HansenPartnership.com>

On Tue, Apr 21, 2015 at 6:21 PM, James Bottomley
<James.Bottomley@hansenpartnership.com> wrote:
> Andy, just on the misc device idea, what about triggering the capsule
> update from close()?  In theory close returns an error code (not sure if
> most tools actually check this, though).  That means we can do the write
> in chunks but pass it in atomically on the close and cat will work
> (provided it checks the return code of close).

I thought about this but IIRC cat doesn't check the return value from close.

--Andy

>
> James
>
>

-- 
Andy Lutomirski
AMA Capital Management, LLC