| 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
| ||
|
Date: Tue, 14 Apr 2009 22:03:31 +0200 From: Miklos Szeredi <miklos@...redi.hu> To: jamie@...reable.org CC: miklos@...redi.hu, jens.axboe@...cle.com, mfasheh@...e.com, akpm@...ux-foundation.org, viro@...IV.linux.org.uk, torvalds@...ux-foundation.org, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [patch 5/6] splice: remove generic_file_splice_write_nolock() On Tue, 14 Apr 2009, Jamie Lokier wrote: > Miklos Szeredi wrote: > > Remove the now unused generic_file_splice_write_nolock() function. > > It's conceptually broken anyway, because splice may need to wait for > > pipe events so holding locks across the whole operation is wrong. > > Did the conceptual brokenness affect userspace behaviour of > splice/sendfile at all? Splice: yes, sendfile: no. Sendfile uses an internal pipe and it always makes sure there's no blocking on that pipe. With splice it's up to the process feeding the pipe to make sure there are buffers for the splice to consume. If it the pipe is not fed properly then the splice call might hang, waiting for data, keeping any locks surrounding generic_file_splice_write_nolock() locked. Which in turn will block other operations from proceeding. Not what we want. Thanks, Miklos -- 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