From: "Wang, Wei W" <wei.w.wang@intel.com>
To: "mst@redhat.com" <mst@redhat.com>,
"stefanha@redhat.com" <stefanha@redhat.com>,
"sgarzare@redhat.com" <sgarzare@redhat.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"asias@redhat.com" <asias@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>
Subject: RE: [PATCH] virtio/vsock: fix the transport to work with VMADDR_CID_ANY
Date: Thu, 25 Nov 2021 09:27:40 +0000 [thread overview]
Message-ID: <7992566c682b46dc9ec2502e44a2fb04@intel.com> (raw)
In-Reply-To: <20211125071554.16969-1-wei.w.wang@intel.com>
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
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
WARNING: multiple messages have this Message-ID (diff)
From: "Wang, Wei W" <wei.w.wang@intel.com>
To: "mst@redhat.com" <mst@redhat.com>,
"stefanha@redhat.com" <stefanha@redhat.com>,
"sgarzare@redhat.com" <sgarzare@redhat.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"asias@redhat.com" <asias@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>
Subject: RE: [PATCH] virtio/vsock: fix the transport to work with VMADDR_CID_ANY
Date: Thu, 25 Nov 2021 09:27:40 +0000 [thread overview]
Message-ID: <7992566c682b46dc9ec2502e44a2fb04@intel.com> (raw)
In-Reply-To: <20211125071554.16969-1-wei.w.wang@intel.com>
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
next prev parent reply other threads:[~2021-11-25 9:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 7:15 [PATCH] virtio/vsock: fix the transport to work with VMADDR_CID_ANY Wei Wang
2021-11-25 7:15 ` Wei Wang
2021-11-25 9:27 ` Wang, Wei W [this message]
2021-11-25 9:27 ` Wang, Wei W
2021-11-25 10:40 ` Stefano Garzarella
2021-11-25 10:40 ` Stefano Garzarella
2021-11-26 2:15 ` Wang, Wei W
2021-11-26 2:15 ` Wang, Wei W
2021-11-25 22:54 ` kernel test robot
2021-11-25 22:54 ` kernel test robot
2021-11-25 22:54 ` kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7992566c682b46dc9ec2502e44a2fb04@intel.com \
--to=wei.w.wang@intel.com \
--cc=asias@redhat.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.