[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAABMjtE-XKa-_kW-aREvHDiyGwcs-GZWjtSjZEeF577FKcUTAA@mail.gmail.com>
Date: Mon, 22 Aug 2022 19:55:27 +0600
From: Khalid Masum <khalid.masum.92@...il.com>
To: Hawkins Jiawei <yin31149@...il.com>
Cc: David Howells <dhowells@...hat.com>,
Marc Dionne <marc.dionne@...istor.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
"open list:NETWORKING [GENERAL]" <netdev@...r.kernel.org>,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
syzbot+7f0483225d0c94cb3441@...kaller.appspotmail.com,
Pavel Skripkin <paskripkin@...il.com>,
linux-kernel-mentees
<linux-kernel-mentees@...ts.linuxfoundation.org>,
linux-afs@...ts.infradead.org,
Dan Carpenter <dan.carpenter@...cle.com>
Subject: Re: [PATCH] rxrpc: fix bad unlock balance in rxrpc_do_sendmsg
>
> /*
> + * @holding_mutex: An indication whether caller can still holds
> + * the call->user_mutex when returned to caller.
Maybe we can use mutex_is_locked instead of using the holding_mutex
parameter to get whether call->user_mutex is still held.
https://www.kernel.org/doc/htmldocs/kernel-locking/API-mutex-is-locked.html
> + * This argument can be NULL, which will effect nothing.
> + *
> * Wait for space to appear in the Tx queue or a signal to occur.
> */
>
thanks,
-- Khalid Masum
Powered by blists - more mailing lists