linux-kernel - Splice: splice_direct_to_actor() and randomly data drop

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>] [day] [month] [year] [list]

Message-ID: <AANLkTi=NU5mDQoRMM7n-F78c_pk+nmOd3=4J8L9puZAd@mail.gmail.com>
Date:	Mon, 29 Nov 2010 15:32:38 +0500
From:	Марк Коренберг 
	<socketpair@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Splice: splice_direct_to_actor() and randomly data drop

Seeing implementation of  splice_direct_to_actor(), I decide, that
"random data drop" can appear if we alrady have done splice_to, but
have problems with splice_from.

1. Why not to use tee() instead of splice_to ? and after all
operations copmleted successfully, just consume data from IN to
/dev/null :) anyhow.

It will allow to splice between ANY file descriptors, not between
"regular file/block device" and ANY.

2. After that, in do_splice we might call do_splice_direct() if both
file descriptors are not pipe.

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