[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yg9xN5e3zyjKTfJw@linutronix.de>
Date: Fri, 18 Feb 2022 11:13:11 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Marek Szyprowski <m.szyprowski@...sung.com>
Cc: bpf@...r.kernel.org, netdev@...r.kernel.org,
"David S. Miller" <davem@...emloft.net>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Jesper Dangaard Brouer <hawk@...nel.org>,
John Fastabend <john.fastabend@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Toke Høiland-Jørgensen <toke@...e.dk>,
Toke Høiland-Jørgensen <toke@...hat.com>,
Felipe Balbi <balbi@...nel.org>, linux-usb@...r.kernel.org
Subject: Re: [PATCH net-next] net: Correct wrong BH disable in hard-interrupt.
On 2022-02-18 11:02:35 [+0100], Marek Szyprowski wrote:
> Hi,
Hi,
> > Marek, could you please give it a try?
>
> Yes. The above change fixes the issue.
Awesome. I will make a patch and send today.
> I've also tried to revert the mentioned commit e5f68b4a3e7b, but this
> gives me the following lockdep warning:
Oh oh. Thank you for that splat.
Sebastian
Powered by blists - more mailing lists