linux-kernel - Re: [patch 0/3] make splice more generic

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: <E1M3XKv-0001Su-Ds@pomaz-ex.szeredi.hu>
Date:	Mon, 11 May 2009 17:22:37 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	jens.axboe@...cle.com
CC:	miklos@...redi.hu, max@...mpel.org, torvalds@...ux-foundation.org,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [patch 0/3] make splice more generic

On Mon, 11 May 2009, Jens Axboe wrote:
> I have applied all three, thanks! However, I think we should be able to
> pass in whether or not this is a strict splice or not. Falling back to
> readv/writev is a good thing as it may help get the interface adopted
> more widely, but I can also easily imagine cases where you'd want to
> make sure that splice actually works without copies. It may even just be
> for users to retry with alternative code paths, instead of proceeding
> with the splice. SPLICE_F_MOVE is a soft flag in that it will move if it
> can, but not fail if it can't. Perhaps we should add a flag that does
> pass back an error if we can't just move pages around, SPLICE_F_STRICT
> or something like that.

Okay, seems pretty trivial.  I'll do a patch.

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/