Kevin Wolf wrote on Wed, Jun 29, 2022 at 10:46:08AM +0200: > I see this a few lines above: > > /* Update read position */ > luringcb->total_read = nread; > > Doesn't it have the same problem? Though maybe getting two short reads > is more of a theoretical case.
Good catch, I'll send a v2 with that one adjusted as well tomorrow -- I had logs and can confirm I didn't get two short reads in a row... I wonder if there'd be a way to test? E.g. act like we've requested n bytes but actually only fill in a bit less in the iov? -- Dominique
