All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nguyen Dinh Phi [SG]" <phind.uet@gmail.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>, Andy King <acking@vmware.com>,
	Dmitry Torokhov <dtor@vmware.com>,
	George Zhang <georgezhang@vmware.com>,
	syzbot+1b2c9c4a0f8708082678@syzkaller.appspotmail.com,
	virtualization@lists.linux.dev, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] vsock: use sock_error() to consume sk_err after a
Date: Thu, 30 Jul 2026 16:25:26 +0800	[thread overview]
Message-ID: <51881c2d-0c76-4333-9bf5-63d4945c520d@gmail.com> (raw)
In-Reply-To: <amn7W3hAIEC7kcQO@sgarzare-redhat>

On 29/7/26 21:19, Stefano Garzarella wrote:
> 
> Should we do the same in other paths (e.g. send/recv) as well in a 
> follwup patch or in a series?
> 
> The patch itself LGTM.
> 
> Thanks,
> Stefano
> 
That is a good point. I'll look into it and send a follow-up patch if it 
makes sense.

Thanks,
Phi

      reply	other threads:[~2026-07-30  8:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27  7:13 [PATCH v2] vsock: use sock_error() to consume sk_err after a phind.uet
2026-07-28  3:14 ` mawupeng
2026-07-29 13:21   ` Stefano Garzarella
2026-07-29 13:19 ` Stefano Garzarella
2026-07-30  8:25   ` Nguyen Dinh Phi [SG] [this message]

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=51881c2d-0c76-4333-9bf5-63d4945c520d@gmail.com \
    --to=phind.uet@gmail.com \
    --cc=acking@vmware.com \
    --cc=davem@davemloft.net \
    --cc=dtor@vmware.com \
    --cc=edumazet@google.com \
    --cc=georgezhang@vmware.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sgarzare@redhat.com \
    --cc=syzbot+1b2c9c4a0f8708082678@syzkaller.appspotmail.com \
    --cc=virtualization@lists.linux.dev \
    /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.