[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20191121.113732.388996672669686057.davem@davemloft.net>
Date: Thu, 21 Nov 2019 11:37:32 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: sgarzare@...hat.com
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
syzbot+e2e5c07bf353b2f79daa@...kaller.appspotmail.com,
stefanha@...hat.com, decui@...rosoft.com, jhansen@...are.com
Subject: Re: [PATCH net-next] vsock: avoid to assign transport if its
initialization fails
From: Stefano Garzarella <sgarzare@...hat.com>
Date: Thu, 21 Nov 2019 10:06:09 +0100
> If transport->init() fails, we can't assign the transport to the
> socket, because it's not initialized correctly, and any future
> calls to the transport callbacks would have an unexpected behavior.
>
> Fixes: c0cfa2d8a788 ("vsock: add multi-transports support")
> Reported-and-tested-by: syzbot+e2e5c07bf353b2f79daa@...kaller.appspotmail.com
> Signed-off-by: Stefano Garzarella <sgarzare@...hat.com>
Applied.
Powered by blists - more mailing lists