[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201124093137.48d1e603@gandalf.local.home>
Date: Tue, 24 Nov 2020 09:31:37 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Jason Wang <jasowang@...hat.com>
Cc: Jakub Kicinski <kuba@...nel.org>,
Leon Romanovsky <leon@...nel.org>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
"Michael S. Tsirkin" <mst@...hat.com>,
Petr Mladek <pmladek@...e.com>,
John Ogness <john.ogness@...utronix.de>,
virtualization@...ts.linux-foundation.org,
Amit Shah <amit@...nel.org>, Itay Aveksis <itayav@...dia.com>,
Ran Rozenstein <ranro@...dia.com>,
netdev <netdev@...r.kernel.org>
Subject: Re: netconsole deadlock with virtnet
On Tue, 24 Nov 2020 11:22:03 +0800
Jason Wang <jasowang@...hat.com> wrote:
> Btw, have a quick search, there are several other drivers that uses tx
> lock in the tx NAPI.
tx NAPI is not the issue. The issue is that write_msg() (in netconsole.c)
calls this polling logic with the target_list_lock held.
Are those other drivers called by netconsole? If not, then this is unique
to virtio-net.
-- Steve
Powered by blists - more mailing lists