[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7992566c682b46dc9ec2502e44a2fb04@intel.com>
Date: Thu, 25 Nov 2021 09:27:40 +0000
From: "Wang, Wei W" <wei.w.wang@...el.com>
To: "mst@...hat.com" <mst@...hat.com>,
"stefanha@...hat.com" <stefanha@...hat.com>,
"sgarzare@...hat.com" <sgarzare@...hat.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"asias@...hat.com" <asias@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"virtualization@...ts.linux-foundation.org"
<virtualization@...ts.linux-foundation.org>
Subject: RE: [PATCH] virtio/vsock: fix the transport to work with
VMADDR_CID_ANY
On Thursday, November 25, 2021 3:16 PM, Wang, Wei W wrote:
> - /* Update CID in case it has changed after a transport reset event */
> - vsk->local_addr.svm_cid = dst.svm_cid;
> -
> if (space_available)
> sk->sk_write_space(sk);
>
Not sure if anybody knows how this affects the transport reset.
Thanks,
Wei
Powered by blists - more mailing lists