From: Simon Horman <horms@kernel.org>
To: Tony Battersby <tonyb@cybernetics.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Jay Vosburgh <j.vosburgh@gmail.com>,
Andy Gospodarek <andy@greyhouse.net>,
Zhengchao Shao <shaozhengchao@huawei.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH net] bonding: fix oops during rmmod
Date: Wed, 15 May 2024 12:44:26 +0100 [thread overview]
Message-ID: <20240515114426.GJ154012@kernel.org> (raw)
In-Reply-To: <641f914f-3216-4eeb-87dd-91b78aa97773@cybernetics.com>
On Tue, May 14, 2024 at 03:57:29PM -0400, Tony Battersby wrote:
> "rmmod bonding" causes an oops ever since commit cc317ea3d927 ("bonding:
> remove redundant NULL check in debugfs function"). Here are the relevant
> functions being called:
>
> bonding_exit()
> bond_destroy_debugfs()
> debugfs_remove_recursive(bonding_debug_root);
> bonding_debug_root = NULL; <--------- SET TO NULL HERE
> bond_netlink_fini()
> rtnl_link_unregister()
> __rtnl_link_unregister()
> unregister_netdevice_many_notify()
> bond_uninit()
> bond_debug_unregister()
> (commit removed check for bonding_debug_root == NULL)
> debugfs_remove()
> simple_recursive_removal()
> down_write() -> OOPS
>
> However, reverting the bad commit does not solve the problem completely
> because the original code contains a race that could cause the same
> oops, although it was much less likely to be triggered unintentionally:
>
> CPU1
> rmmod bonding
> bonding_exit()
> bond_destroy_debugfs()
> debugfs_remove_recursive(bonding_debug_root);
>
> CPU2
> echo -bond0 > /sys/class/net/bonding_masters
> bond_uninit()
> bond_debug_unregister()
> if (!bonding_debug_root)
>
> CPU1
> bonding_debug_root = NULL;
>
> So do NOT revert the bad commit (since the removed checks were racy
> anyway), and instead change the order of actions taken during module
> removal. The same oops can also happen if there is an error during
> module init, so apply the same fix there.
>
> Fixes: cc317ea3d927 ("bonding: remove redundant NULL check in debugfs function")
> Cc: stable@vger.kernel.org
> Signed-off-by: Tony Battersby <tonyb@cybernetics.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2024-05-15 11:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 19:57 [PATCH net] bonding: fix oops during rmmod Tony Battersby
2024-05-15 11:44 ` Simon Horman [this message]
2024-05-15 12:44 ` Jay Vosburgh
2024-05-17 2:40 ` patchwork-bot+netdevbpf
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=20240515114426.GJ154012@kernel.org \
--to=horms@kernel.org \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=j.vosburgh@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shaozhengchao@huawei.com \
--cc=tonyb@cybernetics.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.