mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ginger Li <ginger.jzllee@gmail.com>
Cc: jmaloy@redhat.com, tung.quang.nguyen@est.tech,
	netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] tipc: Fix a data race on mon->peer_cnt in mon_timeout()
Date: Thu, 24 Sep 2026 17:30:16 +0000	[thread overview]
Message-ID: <179027101689.1669750.10034423915812616755.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260922080909.21123-1-ginger.jzllee@gmail.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 22 Sep 2026 16:09:09 +0800 you wrote:
> mon_timeout() evaluates dom_size(mon->peer_cnt) before it takes mon->lock,
> while mon->peer_cnt is updated under that lock by tipc_mon_add_peer() and
> tipc_mon_remove_peer().  The value can therefore be stale, and the decision
> whether the local domain has to be recomputed can be based on an outdated
> member count.
> 
> Read mon->peer_cnt inside the write_lock_bh(&mon->lock) protected region.
> 
> [...]

Here is the summary with links:
  - [net] tipc: Fix a data race on mon->peer_cnt in mon_timeout()
    https://git.kernel.org/netdev/net/c/8e1937fed673

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



      parent reply	other threads:[~2026-09-24 17:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22  8:09 Ginger Li
2026-09-23  3:46 ` Tung Quang Nguyen
2026-09-24 17: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=179027101689.1669750.10034423915812616755.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ginger.jzllee@gmail.com \
    --cc=jmaloy@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=tipc-discussion@lists.sourceforge.net \
    --cc=tung.quang.nguyen@est.tech \
    /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
all inboxes | Powered by JetHome®