[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180124.163830.2180124252515802160.davem@davemloft.net>
Date: Wed, 24 Jan 2018 16:38:30 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: jasowang@...hat.com
Cc: mst@...hat.com, linux-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org, netdev@...r.kernel.org
Subject: Re: [PATCH net 1/2] vhost: use mutex_lock_nested() in
vhost_dev_lock_vqs()
From: Jason Wang <jasowang@...hat.com>
Date: Tue, 23 Jan 2018 17:27:25 +0800
> We used to call mutex_lock() in vhost_dev_lock_vqs() which tries to
> hold mutexes of all virtqueues. This may confuse lockdep to report a
> possible deadlock because of trying to hold locks belong to same
> class. Switch to use mutex_lock_nested() to avoid false positive.
>
> Fixes: 6b1e6cc7855b0 ("vhost: new device IOTLB API")
> Reported-by: syzbot+dbb7c1161485e61b0241@...kaller.appspotmail.com
> Signed-off-by: Jason Wang <jasowang@...hat.com>
Michael, I see you ACK'd this, meaning that you're OK with these two
fixes going via my net tree?
Thanks.
Powered by blists - more mailing lists