[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <85e76f66-f807-ad12-df9d-0805b68133fa@gmail.com>
Date: Sun, 26 Apr 2020 14:53:42 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: "Jason A. Donenfeld" <Jason@...c4.com>,
Eric Dumazet <eric.dumazet@...il.com>
Cc: syzbot <syzbot+0251e883fe39e7a0cb0a@...kaller.appspotmail.com>,
David Miller <davem@...emloft.net>,
Florian Fainelli <f.fainelli@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
jhs@...atatu.com,
Jiří Pírko <jiri@...nulli.us>,
Krzysztof Kozlowski <krzk@...nel.org>, kuba@...nel.org,
kvalo@...eaurora.org, leon@...nel.org,
LKML <linux-kernel@...r.kernel.org>,
linux-kselftest@...r.kernel.org, Netdev <netdev@...r.kernel.org>,
Shuah Khan <shuah@...nel.org>, syzkaller-bugs@...glegroups.com,
Thomas Gleixner <tglx@...utronix.de>, vivien.didelot@...il.com,
Cong Wang <xiyou.wangcong@...il.com>
Subject: Re: INFO: rcu detected stall in wg_packet_tx_worker
On 4/26/20 1:46 PM, Jason A. Donenfeld wrote:
>
> Ah, whew, okay. I had just begun instrumenting sfq (the highly
> technical term for "adding printks everywhere") to figure out what's
> going on. Looks like you've got a handle on it, so I'll let you have
> at it.
Yes, syzbot manages to put a zero in q->scaled_quantum
I will send a fix.
>
> On the brighter side, it seems like Dmitry's and my effort to get full
> coverage of WireGuard has paid off in the sense that tons of packets
> wind up being shoveled through it in one way or another, which is
> good.
>
Sure !
Powered by blists - more mailing lists