[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20191001.212355.540884408544073853.davem@davemloft.net>
Date: Tue, 01 Oct 2019 21:23:55 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: decui@...rosoft.com
Cc: kys@...rosoft.com, haiyangz@...rosoft.com, sthemmin@...rosoft.com,
sashal@...nel.org, stefanha@...hat.com, gregkh@...uxfoundation.org,
arnd@...db.de, deepa.kernel@...il.com, ytht.net@...il.com,
tglx@...utronix.de, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-hyperv@...r.kernel.org,
kvm@...r.kernel.org, virtualization@...ts.linux-foundation.org,
mikelley@...rosoft.com, sgarzare@...hat.com, jhansen@...are.com
Subject: Re: [PATCH net v3] vsock: Fix a lockdep warning in
__vsock_release()
From: Dexuan Cui <decui@...rosoft.com>
Date: Mon, 30 Sep 2019 18:43:50 +0000
> Lockdep is unhappy if two locks from the same class are held.
>
> Fix the below warning for hyperv and virtio sockets (vmci socket code
> doesn't have the issue) by using lock_sock_nested() when __vsock_release()
> is called recursively:
...
> Tested-by: Stefano Garzarella <sgarzare@...hat.com>
> Signed-off-by: Dexuan Cui <decui@...rosoft.com>
Applied, thanks.
Powered by blists - more mailing lists