Re: [RFC PATCH v1 1/2] vsock: return errors other than -ENOMEM to socket

2023-03-29 Thread Vishnu Dasa via Virtualization
> On Mar 28, 2023, at 4:20 AM, Arseniy Krasnov wrote: > > !! External Email > > On 28.03.2023 14:19, Stefano Garzarella wrote: >> On Tue, Mar 28, 2023 at 01:42:19PM +0300, Arseniy Krasnov wrote: >>> >>> >>> On 28.03.2023 12:42, Stefano Garzarella wrote: I pressed send too early...

Re: [RFC PATCH v1 1/2] vsock: return errors other than -ENOMEM to socket

2023-03-28 Thread Stefano Garzarella
On Tue, Mar 28, 2023 at 01:42:19PM +0300, Arseniy Krasnov wrote: On 28.03.2023 12:42, Stefano Garzarella wrote: I pressed send too early... CCing Bryan, Vishnu, and pv-driv...@vmware.com On Tue, Mar 28, 2023 at 11:39 AM Stefano Garzarella wrote: On Sun, Mar 26, 2023 at 01:13:11AM +0300,

Re: [RFC PATCH v1 1/2] vsock: return errors other than -ENOMEM to socket

2023-03-28 Thread Stefano Garzarella
I pressed send too early... CCing Bryan, Vishnu, and pv-driv...@vmware.com On Tue, Mar 28, 2023 at 11:39 AM Stefano Garzarella wrote: > > On Sun, Mar 26, 2023 at 01:13:11AM +0300, Arseniy Krasnov wrote: > >This removes behaviour, where error code returned from any transport > >was always

Re: [RFC PATCH v1 1/2] vsock: return errors other than -ENOMEM to socket

2023-03-28 Thread Stefano Garzarella
On Sun, Mar 26, 2023 at 01:13:11AM +0300, Arseniy Krasnov wrote: This removes behaviour, where error code returned from any transport was always switched to ENOMEM. This works in the same way as: commit c43170b7e157 ("vsock: return errors other than -ENOMEM to socket"), but for receive calls.