Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 22 Aug 2022 22:00:37 +0600
From:   Khalid Masum <khalid.masum.92@gmail.com>
To:     Hawkins Jiawei <yin31149@gmail.com>, dan.carpenter@oracle.com
CC:     davem@davemloft.net, dhowells@redhat.com, edumazet@google.com,
        kuba@kernel.org, linux-afs@lists.infradead.org,
        linux-kernel-mentees@lists.linuxfoundation.org,
        linux-kernel@vger.kernel.org, marc.dionne@auristor.com,
        netdev@vger.kernel.org, pabeni@redhat.com, paskripkin@gmail.com,
        syzbot+7f0483225d0c94cb3441@syzkaller.appspotmail.com,
        syzkaller-bugs@googlegroups.com, yin31149@gmail.com
Subject: Re: [PATCH] rxrpc: fix bad unlock balance in rxrpc_do_sendmsg
User-Agent: K-9 Mail for Android
In-Reply-To: <20220822153944.6204-1-yin31149@gmail.com>
References: <20220822140532.GF2695@kadam> <20220822153944.6204-1-yin31149@gmail.com>
Message-ID: <0ED076C1-6250-43EA-A7BE-948DFAEE851A@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk


On August 22, 2022 9:39:43 PM GMT+06:00, Hawkins Jiawei <yin31149@gmail=2E=
com> wrote:
>On Mon, 22 Aug 2022 at 22:06, Dan Carpenter <dan=2Ecarpenter@oracle=2Ecom=
> wrote:

>I trid this before, it doesn't work as Dan points out=2E I think
>it seems that mutex_is_locked() only checks whether there is a task

I see=2E
>holding the mutex, but do not check whether it is current task holding
>mutex=2E I also tried lockdep_is_held(), lockdep_is_held() seems can dete=
ct

Ok=2E
>call->user_mutex is still held accurately, although this cannot be the pa=
tch=2E

Useful to know! Thanks for the information=2E

  -- Khalid Masum=20