io_submit with silly values/pointers

[Denys Vlasenko]

On 11/06/2013 08:55 PM, Dr. David Alan Gilbert wrote:
> Hi,
>   'trinity' generated an io_submit call with a ludicrous large
> 'nr' of requests, the result being strace sat there just printing out
> {...}, for nearly ever since the data didn't exist.
> 
>   Is the right thing to 'break' rather than 'continue' if either
> of the umove calls fail?     The alternative way is to break 
> if the iocbs read fails but allow individualy broken iocb reads.
> I'm not sure which is more sane - you could have a real call
> that fails for another reason before hitting the bad iocb.

Please try attached patch.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 3.patch
Type: text/x-patch
Size: 1757 bytes
Desc: not available
URL: <http://lists.strace.io/pipermail/strace-devel/attachments/20131108/c083dad4/attachment.bin>