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, kuniyu@google.com, netdev@vger.kernel.org,
	eric.dumazet@gmail.com,
	syzbot+965506b59a2de0b6905c@syzkaller.appspotmail.com, ja@ssi.bg
Subject: Re: [PATCH net] net: serialize netif_running() check in enqueue_to_backlog()
Date: Tue, 16 Jun 2026 22:50:08 +0000	[thread overview]
Message-ID: <178165020813.1270198.2547560185678219192.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260616141317.407791-1-edumazet@google.com>

Hello:

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

On Tue, 16 Jun 2026 14:13:17 +0000 you wrote:
> Syzbot reported a KASAN slab-use-after-free in fib_rules_lookup().
> 
> The root cause is a race condition where packets can escape the backlog
> flushing during device unregistration (e.g., during netns exit).
> 
> Commit e9e4dd3267d0 ("net: do not process device backlog during unregistration")
> introduced a lockless netif_running() check in enqueue_to_backlog() to
> prevent queuing packets to an unregistering device.
> 
> [...]

Here is the summary with links:
  - [net] net: serialize netif_running() check in enqueue_to_backlog()
    https://git.kernel.org/netdev/net-next/c/46762cefe7f4

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-06-16 22:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-16 14:13 [PATCH net] net: serialize netif_running() check in enqueue_to_backlog() Eric Dumazet
2026-06-16 21:39 ` Kuniyuki Iwashima
2026-06-16 22:50 ` 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=178165020813.1270198.2547560185678219192.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=horms@kernel.org \
    --cc=ja@ssi.bg \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzbot+965506b59a2de0b6905c@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 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.