[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f103b4a29b7c1942f091bd7b90d7a927d72c20a2.camel@coelho.fi>
Date: Sat, 13 Mar 2021 18:32:26 +0200
From: Luca Coelho <luca@...lho.fi>
To: Jiri Kosina <jikos@...nel.org>, Kalle Valo <kvalo@...eaurora.org>
Cc: Johannes Berg <johannes.berg@...el.com>,
Emmanuel Grumbach <emmanuel.grumbach@...el.com>,
linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] iwlwifi: Fix softirq/hardirq disabling in
iwl_pcie_enqueue_hcmd()
On Sat, 2021-03-13 at 16:43 +0100, Jiri Kosina wrote:
> On Sat, 13 Mar 2021, Kalle Valo wrote:
>
> > > > > From: Jiri Kosina <jkosina@...e.cz>
> > > > >
> > > > > It's possible for iwl_pcie_enqueue_hcmd() to be called with hard IRQs
> > > > > disabled (e.g. from LED core). We can't enable BHs in such a situation.
> > > > >
> > > > > Turn the unconditional BH-enable/BH-disable code into
> > > > > hardirq-disable/conditional-enable.
> > > > >
> > > > > This fixes the warning below.
> > > >
> > > > Hi,
> > > >
> > > > friendly ping on this one ...
> > >
> > > Luca,
> > >
> > > Johannes is telling me that he merged this patch internally, but I have no
> > > idea what is happening to it ... ?
> > >
> > > The reported splat is a clear bug, so it should be fixed one way or the
> > > other.
> >
> > Should I take this to wireless-drivers?
>
> I can't speak for the maintainers, but as far as I am concerned, it
> definitely is a 5.12 material, as it fixes real scheduling bug.
Yes, please take this to w-d. We have a similar patch internally, but
there's a backlog and it will take me some time to get to it. I'll
resolve eventual conflicts when time comes.
Thanks!
--
Cheers,
Luca.
Powered by blists - more mailing lists