linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xin Xie <xiexinet@gmail.com>
To: Hangbin Liu <liuhangbin@gmail.com>, Felix Maurer <fmaurer@redhat.com>
Cc: Simon Horman <horms@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Lukasz Majewski <lukma@denx.de>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Hangbin Liu <liuhangbin@kylinos.cn>,
	syzbot+fbf74291c3b7e753b481@syzkaller.appspotmail.com
Subject: Re: [PATCH net] hsr: Avoid holding seqnr_lock while transmitting packets
Date: Fri, 7 Aug 2026 16:18:01 +0200	[thread overview]
Message-ID: <e0019840-0b51-4997-a5cd-8bdb0e95ebf3@gmail.com> (raw)
In-Reply-To: <anXnxn-PBv8qH6VB@fedora>

On 07/08/2026 16:12, Hangbin Liu wrote:
> On Fri, Aug 07, 2026 at 03:16:36PM +0200, Felix Maurer wrote:
> 
> Oh, interesting. I just came back to work this week and found this issue
> when reviewing the syzbot bug list. Since Xie Xin has worked on this,
> let's drop my patch and fix it in his patch set.
> 
> Cheers
> Hangbin

Hi Hangbin,

Thanks for coordinating. I have just posted v5:

https://lore.kernel.org/netdev/20260807140751.1351-1-xiexinet@gmail.com/

Patch 2 contains the overlapping seqnr_lock fix, including the affected TX statistics and the PRP supervision path.

Thanks,
-- 
Xin

      reply	other threads:[~2026-08-07 14:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05  3:09 [PATCH net] hsr: Avoid holding seqnr_lock while transmitting packets Hangbin Liu
2026-08-07  9:43 ` Simon Horman
2026-08-07 12:42   ` Hangbin Liu
2026-08-07 13:16     ` Felix Maurer
2026-08-07 14:12       ` Hangbin Liu
2026-08-07 14:18         ` Xin Xie [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=e0019840-0b51-4997-a5cd-8bdb0e95ebf3@gmail.com \
    --to=xiexinet@gmail.com \
    --cc=bigeasy@linutronix.de \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fmaurer@redhat.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liuhangbin@gmail.com \
    --cc=liuhangbin@kylinos.cn \
    --cc=lukma@denx.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzbot+fbf74291c3b7e753b481@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).