Re: [RFC] writev() semantics with invalid iovec in the middle

From: Linus Torvalds
Date: Thu Sep 15 2016 - 18:33:12 EST

On Thu, Sep 15, 2016 at 3:29 PM, Al Viro <viro@xxxxxxxxxxxxxxxxxx> wrote:
> Unfortunately, some of LTP writev tests end up checking that writev() does
> behave that way - they feed it a three-element iovec with shorter-than-page
> segments, the second of which is all invalid. And they check that the
> entire first segment had been written.
> I would really like to drop that property,

I'm pretty sure you can and should do that.

The LTP test people have actually been pretty good about just fixing
their tests when they cause problems and there is no reason for the
particular behavior.