On Thu, 31 Jul 2008, Nick Piggin wrote: > > It seems like the right way to fix this would be to allow the splicing > process to be notified of a short read, in which case it could try to > refill the pipe with the unread bytes... Hmm. That should certainly work with the splice model. The users of the data wouldn't eat (or ignore) the invalid data, they'd just say "invalid data", and stop. And it would be up to the other side to handle it (it can see the state of the pipe, we can make it both wake up POLL_ERR _and_ return an error if somebody tries to write to a "blocked" pipe). So yes, that's very possible, but it obviously requires splice() users to be able to handle more cases. I'm not sure it's realistic to expect users to be that advanced. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
