public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: netdev@vger.kernel.org
Cc: Stanislav Fomichev <sdf.kernel@gmail.com>,
	davem@davemloft.net, edumazet@google.com, pabeni@redhat.com
Subject: Re: [PATCH net-next v7 00/15] net: sleepable ndo_set_rx_mode
Date: Mon, 13 Apr 2026 11:45:22 -0700	[thread overview]
Message-ID: <20260413114522.3e8e1b6d@kernel.org> (raw)
In-Reply-To: <20260413171131.550126-1-sdf@fomichev.me>

On Mon, 13 Apr 2026 10:11:16 -0700 Stanislav Fomichev wrote:
> This series adds a new ndo_set_rx_mode_async callback that enables
> drivers to handle address list updates in a sleepable context. The
> current ndo_set_rx_mode is called under the netif_addr_lock spinlock
> with BHs disabled, which prevents drivers from sleeping. This is
> problematic for ops-locked drivers that need to sleep.

A note to other reviewers - I asked Stanislav (off-list) to keep working
on this even tho he's targeting net-next, because the patch set
addresses a syzbot report. Chances of hitting the issue are low but
this is a fix, really.

  parent reply	other threads:[~2026-04-13 18:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-13 17:11 [PATCH net-next v7 00/15] net: sleepable ndo_set_rx_mode Stanislav Fomichev
2026-04-13 17:11 ` [PATCH net-next v7 01/15] net: add address list snapshot and reconciliation infrastructure Stanislav Fomichev
2026-04-13 17:11 ` [PATCH net-next v7 02/15] net: introduce ndo_set_rx_mode_async and netdev_rx_mode_work Stanislav Fomichev
2026-04-13 17:11 ` [PATCH net-next v7 03/15] net: cache snapshot entries for ndo_set_rx_mode_async Stanislav Fomichev
2026-04-13 17:11 ` [PATCH net-next v7 04/15] net: move promiscuity handling into netdev_rx_mode_work Stanislav Fomichev
2026-04-13 17:11 ` [PATCH net-next v7 05/15] fbnic: convert to ndo_set_rx_mode_async Stanislav Fomichev
2026-04-13 17:11 ` [PATCH net-next v7 06/15] mlx5: " Stanislav Fomichev
2026-04-13 17:11 ` [PATCH net-next v7 07/15] bnxt: " Stanislav Fomichev
2026-04-13 17:11 ` [PATCH net-next v7 08/15] bnxt: use snapshot in bnxt_cfg_rx_mode Stanislav Fomichev
2026-04-13 17:11 ` [PATCH net-next v7 09/15] iavf: convert to ndo_set_rx_mode_async Stanislav Fomichev
2026-04-13 17:11 ` [PATCH net-next v7 10/15] netdevsim: " Stanislav Fomichev
2026-04-13 17:11 ` [PATCH net-next v7 11/15] dummy: " Stanislav Fomichev
2026-04-13 17:11 ` [PATCH net-next v7 12/15] netkit: " Stanislav Fomichev
2026-04-13 17:11 ` [PATCH net-next v7 13/15] net: warn ops-locked drivers still using ndo_set_rx_mode Stanislav Fomichev
2026-04-13 17:11 ` [PATCH net-next v7 14/15] selftests: net: add team_bridge_macvlan rx_mode test Stanislav Fomichev
2026-04-13 18:09   ` Breno Leitao
2026-04-13 17:11 ` [PATCH net-next v7 15/15] selftests: net: use ip commands instead of teamd in team " Stanislav Fomichev
2026-04-13 18:45 ` Jakub Kicinski [this message]
2026-04-14  2:08 ` [PATCH net-next v7 00/15] net: sleepable ndo_set_rx_mode Jakub Kicinski
2026-04-14 19:24   ` Stanislav Fomichev

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=20260413114522.3e8e1b6d@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf.kernel@gmail.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