From: Paolo Abeni <pabeni@redhat.com>
To: quanyeyang@proton.me, Eric Dumazet <edumazet@google.com>,
Neal Cardwell <ncardwell@google.com>,
Kuniyuki Iwashima <kuniyu@google.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Simon Horman <horms@kernel.org>,
"Matthieu Baerts (NGI0)" <matttbe@kernel.org>,
Geliang Tang <geliang@kernel.org>,
Mat Martineau <martineau@kernel.org>,
Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v5 0/2] tcp: annotate lockless access to sk->sk_err
Date: Thu, 1 Oct 2026 11:10:40 +0200 [thread overview]
Message-ID: <3d9d442f-f168-43da-87b0-010ad5a78365@redhat.com> (raw)
In-Reply-To: <20260925-mptcp-sk-err-net-v5-0-0cac04d6ea48@proton.me>
On 9/25/26 14:47, Quanye Yang via B4 Relay wrote:
> do_recvmmsg() and getsockopt(SO_ERROR) call sock_error() without the
> socket lock and clear sk_err with xchg().
>
> Patch 1 covers TCP. Peek-only sites use READ_ONCE(). On the no-data
> recv and splice paths, call sock_error() once and only stop when it
> returns a non-zero error. tcp_bpf_sendmsg() folds two unmarked loads
> into one READ_ONCE() and uses that value as the returned errno.
>
> Patch 2 does the same for MPTCP and annotates the remaining subflow
> error-report peeks.
Note that there are more possible follow-ups in tls and on the write side:
https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260925-mptcp-sk-err-net-v5-0-0cac04d6ea48@proton.me
/P
next prev parent reply other threads:[~2026-10-01 9:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 12:47 [PATCH net-next v5 0/2] tcp: annotate lockless access to sk->sk_err Quanye Yang via B4 Relay
2026-09-25 12:47 ` [PATCH net-next v5 1/2] " Quanye Yang via B4 Relay
2026-10-01 0:21 ` Jakub Kicinski
2026-10-01 7:24 ` Eric Dumazet
2026-09-25 12:47 ` [PATCH net-next v5 2/2] mptcp: " Quanye Yang via B4 Relay
2026-10-01 7:32 ` Matthieu Baerts
2026-10-01 9:10 ` [PATCH net-next v5 0/2] tcp: " patchwork-bot+netdevbpf
2026-10-01 9:10 ` Paolo Abeni [this message]
2026-10-01 12:44 ` quanyeyang
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=3d9d442f-f168-43da-87b0-010ad5a78365@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=jiayuan.chen@linux.dev \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=quanyeyang@proton.me \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox