All of lore.kernel.org
 help / color / mirror / Atom feed
From: gang.yan@linux.dev
To: "Cen Zhang" <zzzccc427@gmail.com>
Cc: matttbe@kernel.org, martineau@kernel.org, geliang@kernel.org,
	mptcp@lists.linux.dev
Subject: Re: [PATCH net] mptcp: protect listener backlog reads in diagnostics
Date: Tue, 27 Oct 2026 10:41:21 +0000	[thread overview]
Message-ID: <f88992ae9b2dc51fd3a0ba2f9c23a29a91660877@linux.dev> (raw)
In-Reply-To: <CAFRLqsU2QHD2Ta2aL_qSVr9nVFrn6mXV_nZ987+oqHUbCa7ZSw@mail.gmail.com>

October 26, 2026 at 10:44 PM, "Cen Zhang" <zzzccc427@gmail.com mailto:zzzccc427@gmail.com?to=%22Cen%20Zhang%22%20%3Czzzccc427%40gmail.com%3E > wrote:


> 
> Hi Eric,
> 
> Eric Dumazet <edumazet@kernel.org> 于2026年10月26日周一 20:38写道:
> 
> > 
> > Adding these stack traces without symbols is not really nice.
> > 
> >  Time to use scripts/decode_stacktrace.sh
> > 
> Sorry about that, v2 carries the report decoded with
> scripts/decode_stacktrace.sh and trimmed to the relevant frames.
> 
> > 
> > msk->first is a TCP socket: TCP listeners have SOCK_RCU_FREE, and
> >  tcp_prot / tcpv6_prot use SLAB_TYPESAFE_BY_RCU. Reading two integers
> >  under rcu_read_lock() is safe, and stale values are fine for diag.
> > 
> Thanks for the suggestions.

Hi Cen,

Basically this looks fine to me, I don't see any issue with the overall
approach.

Also, could you send v3 separately to the MPTCP mailing list? It seems the
CI checks were not triggered this time. I guess it might be because the
patch was not based on the export branch of the mptcp repo on GitHub, so
you can generate the patch based on that branch
(multipath-tcp/mptcp_net-next, branch export).

Two notes for next time (Important):
1. For MPTCP-only patches, it is enough to send them to the MPTCP list
   only, no need to CC netdev.
2. If a new version is needed, please wait 24 hours before sending it.



Thanks
Gang


> 
> Best regards,
> Cen Zhang
>

  reply	other threads:[~2026-10-27 10:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26 12:04 [PATCH net] mptcp: protect listener backlog reads in diagnostics Cen Zhang
2026-10-26 12:10 ` netdev-bot+sinfo
2026-10-26 12:38 ` Eric Dumazet
2026-10-26 14:44   ` Cen Zhang
2026-10-27 10:41     ` gang.yan [this message]
2026-10-27 10:49       ` gang.yan
2026-10-27 11:37       ` Matthieu Baerts
2026-10-28 13:54         ` Cen Zhang

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=f88992ae9b2dc51fd3a0ba2f9c23a29a91660877@linux.dev \
    --to=gang.yan@linux.dev \
    --cc=geliang@kernel.org \
    --cc=martineau@kernel.org \
    --cc=matttbe@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=zzzccc427@gmail.com \
    /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.