linux-kernel - Re: efivarfs and writev() support

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: <20150311134226.GB24174@codeblueprint.co.uk>
Date:	Wed, 11 Mar 2015 13:42:26 +0000
From:	Matt Fleming <matt@...eblueprint.co.uk>
To:	Marcel Holtmann <marcel@...tmann.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-efi@...r.kernel.org,
	Matthew Garrett <matthew.garrett@...ula.com>,
	Jeremy Kerr <jk@...abs.org>,
	Matt Fleming <matt.fleming@...el.com>,
	Al Viro <viro@...IV.linux.org.uk>
Subject: Re: efivarfs and writev() support

On Sun, 08 Mar, at 03:24:09PM, Marcel Holtmann wrote:
> Hi,
> 
> it seems that efivarfs only supports readv(), but when it comes to
> writev(), I am getting an error. Is there any reason to not support
> vectored write on this filesystem? Especially with the uint32 header
> for each file, I think it would make perfect sense to support it.

What error are you seeing? I thought that the vfs fell back to a looped
write if the file system doesn't support .write_iter()?

But yes, we definitely should support writev().

-- 
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/