All of lore.kernel.org
 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,
	horms@kernel.org, andrew+netdev@lunn.ch, netdev@vger.kernel.org,
	eric.dumazet@gmail.com, qingfang.deng@linux.dev,
	linux-ppp@vger.kernel.org
Subject: Re: [PATCH net] ppp: annotate data races in ppp_generic
Date: Thu, 23 Jul 2026 14:10:21 +0000	[thread overview]
Message-ID: <178481582189.2248593.7721284529663157759.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260722101605.2868548-1-edumazet@google.com>

Hello:

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

On Wed, 22 Jul 2026 10:16:05 +0000 you wrote:
> Several fields in struct ppp can be read or updated concurrently
> from multiple CPUs without synchronization, causing data races:
> 
> 1. ppp->mru is read concurrently in ppp_receive_nonmp_frame() while
>    being updated via PPPIOCSMRU ioctl. Protect ppp->mru updates in
>    PPPIOCSMRU with ppp_recv_lock(ppp).
> 
> [...]

Here is the summary with links:
  - [net] ppp: annotate data races in ppp_generic
    https://git.kernel.org/netdev/net/c/543adf072165

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-07-23 14:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22 10:16 [PATCH net] ppp: annotate data races in ppp_generic Eric Dumazet
2026-07-23  6:24 ` Qingfang Deng
2026-07-23  6:48   ` Eric Dumazet
2026-07-23  7:21     ` Qingfang Deng
2026-07-23 14:10 ` 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=178481582189.2248593.7721284529663157759.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-ppp@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=qingfang.deng@linux.dev \
    /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.