Re: [PATCH v2] vringh: fix __vringh_iov() when riov and wiov are different

2020-10-09 Thread Stefano Garzarella
On Fri, Oct 09, 2020 at 12:05:15PM +0800, Jason Wang wrote: > > On 2020/10/9 上午4:42, Stefano Garzarella wrote: > > If riov and wiov are both defined and they point to different > > objects, only riov is initialized. If the wiov is not initialized > > by the caller, the function fails returning

Re: [PATCH v2] vringh: fix __vringh_iov() when riov and wiov are different

2020-10-08 Thread Jason Wang
On 2020/10/9 上午4:42, Stefano Garzarella wrote: If riov and wiov are both defined and they point to different objects, only riov is initialized. If the wiov is not initialized by the caller, the function fails returning -EINVAL and printing "Readable desc 0x... after writable" error message.

[PATCH v2] vringh: fix __vringh_iov() when riov and wiov are different

2020-10-08 Thread Stefano Garzarella
If riov and wiov are both defined and they point to different objects, only riov is initialized. If the wiov is not initialized by the caller, the function fails returning -EINVAL and printing "Readable desc 0x... after writable" error message. This issue happens when descriptors have both