From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <i.abramov@mt-integration.ru>
Cc: <johannes@sipsolutions.net>, <linux-kernel@vger.kernel.org>,
<linux-wireless@vger.kernel.org>, <lvc-project@linuxtesting.org>,
<netdev@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] Avoid calling WARN_ON() on allocation failure in cfg80211_switch_netns()
Date: Mon, 7 Apr 2025 10:29:57 -0700 [thread overview]
Message-ID: <20250407173036.30549-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20250407125345.1238818-1-i.abramov@mt-integration.ru>
From: Ivan Abramov <i.abramov@mt-integration.ru>
Date: Mon, 7 Apr 2025 15:53:41 +0300
> This series is inspired by similar series in ieee802154. As far as I know,
> there were no WARN_ON triggers in this code so far, but since it's almost
> identical to cfg802154_* counterparts, same changes are proposed.
>
> Link to ieee802154 series: https://lore.kernel.org/netdev/20250403101935.991385-1-i.abramov@mt-integration.ru/T/
>
> v2: Add 2 patches. Also make sure to commit against latest
> netdev/net.
>
> Ivan Abramov (3):
> cfg80211: Restore initial state on failed device_rename() in
> cfg80211_switch_netns()
> cfg80211: Avoid calling WARN_ON() on -ENOMEM in
> cfg80211_switch_netns()
> cfg80211: Remove WARN_ON() in cfg80211_pernet_exit()
Let's see how this thread goes first.
https://lore.kernel.org/netdev/CANn89i+UQQ6GqhWisHQEL0ECNFoQqVrO+2Ee3oDzysdR7dh=Ag@mail.gmail.com/
prev parent reply other threads:[~2025-04-07 17:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 12:53 [PATCH v2 0/3] Avoid calling WARN_ON() on allocation failure in cfg80211_switch_netns() Ivan Abramov
2025-04-07 12:53 ` [PATCH v2 1/3] cfg80211: Restore initial state on failed device_rename() " Ivan Abramov
2025-04-23 15:44 ` Johannes Berg
2025-04-23 18:16 ` Kuniyuki Iwashima
2025-04-07 12:53 ` [PATCH v2 2/3] cfg80211: Avoid calling WARN_ON() on -ENOMEM " Ivan Abramov
2025-04-07 12:53 ` [PATCH v2 3/3] cfg80211: Remove WARN_ON() in cfg80211_pernet_exit() Ivan Abramov
2025-04-07 17:29 ` Kuniyuki Iwashima [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=20250407173036.30549-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=i.abramov@mt-integration.ru \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=netdev@vger.kernel.org \
/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