From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: Daniel Suchy <danny@danysek.cz>,
"davem@davemloft.net" <davem@davemloft.net>,
"rafael.richter@gin.de" <rafael.richter@gin.de>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: patch problem - mv88e6xxx: flush switchdev FDB workqueue
Date: Mon, 14 Mar 2022 07:38:50 +0100 [thread overview]
Message-ID: <Yi7i+pebGu0NoIsF@kroah.com> (raw)
In-Reply-To: <20220313141030.ztwhuhfwxjfzi5nb@skbuf>
On Sun, Mar 13, 2022 at 02:10:31PM +0000, Vladimir Oltean wrote:
> Hi Daniel,
>
> On Sun, Mar 13, 2022 at 03:03:07PM +0100, Daniel Suchy wrote:
> > Hello,
> >
> > I noticed boot problems on my Turris Omnia (with Marvell 88E6176 switch
> > chip) after "net: dsa: mv88e6xxx: flush switchdev FDB workqueue before
> > removing VLAN" commit https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2566a89b9e163b2fcd104d6005e0149f197b8a48
> >
> > Within logs I catched hung kernel tasks (see below), at least first is
> > related to DSA subsystem.
> >
> > When I revert this patch, everything works as expected and without any
> > issues.
> >
> > In my setup, I have few vlans on affected switch (i'm using ifupdown2 v3.0
> > with iproute2 5.16 for configuration).
> >
> > It seems your this patch introduces some new problem (at least for 5.15
> > kernels). I suggest revert this patch.
> >
> > - Daniel
>
> Oh wow, I'm terribly sorry. Yes, this patch shouldn't have been
> backported to kernel 5.15 and below, but I guess I missed the
> backport notification email and forgot to tell Greg about this.
> Patch "net: dsa: mv88e6xxx: flush switchdev FDB workqueue before
> removing VLAN" needs to be immediately reverted from these trees.
>
> Greg, to avoid this from happening in the future, would something like
> this work? Is this parsed in some way?
>
> Depends-on: 0faf890fc519 ("net: dsa: drop rtnl_lock from dsa_slave_switchdev_event_work") # which first appeared in v5.16
The "Fixes:" tag will solve this, please just use that in the future.
I'll go revert this, thanks.
greg k-h
next prev parent reply other threads:[~2022-03-14 6:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ccf51795-5821-203d-348e-295aabbdc735@danysek.cz>
2022-03-13 14:10 ` patch problem - mv88e6xxx: flush switchdev FDB workqueue Vladimir Oltean
2022-03-13 14:18 ` Vladimir Oltean
2022-03-14 6:38 ` gregkh [this message]
2022-03-14 7:21 ` gregkh
2022-03-14 11:17 ` Vladimir Oltean
2022-03-14 11:25 ` gregkh
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=Yi7i+pebGu0NoIsF@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=danny@danysek.cz \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rafael.richter@gin.de \
--cc=stable@vger.kernel.org \
--cc=vladimir.oltean@nxp.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