netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	netdev@vger.kernel.org, eric.dumazet@gmail.com,
	syzkaller@googlegroups.com, bigeasy@linutronix.de
Subject: Re: [PATCH net] net: hsr: remove seqnr_lock
Date: Mon, 09 Sep 2024 09:30:31 +0000	[thread overview]
Message-ID: <172587423152.3396102.11022055395407789320.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240904133725.1073963-1-edumazet@google.com>

Hello:

This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:

On Wed,  4 Sep 2024 13:37:25 +0000 you wrote:
> syzbot found a new splat [1].
> 
> Instead of adding yet another spin_lock_bh(&hsr->seqnr_lock) /
> spin_unlock_bh(&hsr->seqnr_lock) pair, remove seqnr_lock
> and use atomic_t for hsr->sequence_nr and hsr->sup_sequence_nr.
> 
> This also avoid a race in hsr_fill_info().
> 
> [...]

Here is the summary with links:
  - [net] net: hsr: remove seqnr_lock
    https://git.kernel.org/netdev/net/c/b3c9e65eb227

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-09-09  9:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-04 13:37 [PATCH net] net: hsr: remove seqnr_lock Eric Dumazet
2024-09-05 10:54 ` Simon Horman
2024-09-05 12:17 ` Sebastian Andrzej Siewior
2024-09-05 12:26   ` Eric Dumazet
2024-09-05 13:18     ` Sebastian Andrzej Siewior
2024-09-05 13:26       ` Eric Dumazet
2024-09-05 13:40         ` Sebastian Andrzej Siewior
2024-09-05 20:47         ` Sebastian Andrzej Siewior
2024-09-09  9:30 ` patchwork-bot+netdevbpf [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=172587423152.3396102.11022055395407789320.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzkaller@googlegroups.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).