linux-kernel - Re: [PATCH v6 0/2] Enable capsule loader interface for efi firmware updating

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20151003090829.GD11942@pd.tnic>
Date:	Sat, 3 Oct 2015 11:08:29 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Andy Lutomirski <luto@...capital.net>
Cc:	"linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
	Matt Fleming <matt@...sole-pimps.org>,
	Roy Franz <roy.franz@...aro.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"Kweh, Hock Leong" <hock.leong.kweh@...el.com>,
	Ong Boon Leong <boon.leong.ong@...el.com>,
	James Bottomley <James.Bottomley@...senpartnership.com>,
	Sam Protsenko <semen.protsenko@...aro.org>,
	Linux FS Devel <linux-fsdevel@...r.kernel.org>,
	Fleming Matt <matt.fleming@...el.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Peter Jones <pjones@...hat.com>
Subject: Re: [PATCH v6 0/2] Enable capsule loader interface for efi firmware
 updating

On Fri, Oct 02, 2015 at 09:18:05PM -0700, Andy Lutomirski wrote:
> > What does the error case look like? A standard glibc message about
> > write(2) failing?
> >
> 
> close(2), right?

I'm looking at those retvals of efi_capsule_write(). They are returned
to userspace during write(2), no?

/me has no idea how the whole plumbing actually works that's why me is
asking stupid questions.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
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/