From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2108DC28D13 for ; Mon, 22 Aug 2022 08:49:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234122AbiHVItB (ORCPT ); Mon, 22 Aug 2022 04:49:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58378 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233841AbiHVIso (ORCPT ); Mon, 22 Aug 2022 04:48:44 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 067439FCE for ; Mon, 22 Aug 2022 01:48:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1661158101; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=hf0005VbFoqadMHqE2/k8IMSgs4M7ELH98Ps6ciAPSE=; b=G0Bsx/PeugOuSsWTIYWimTgroy7E9RtIsr8ARDadyY0hEEJcVk3XlBvZYmAL07PT6hLH+q Cl8eKlnIeMvUyWgu4+NNzlyIFMN64SpnZ5IoYG12UC6XopYGXTUBIiuZSjXgVnTDYpuABE cjpdPscmb8Wr6A1m4eAV2TBGn3o/6XY= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-548-Yeqpuf_3Ngep_gSMOePBeA-1; Mon, 22 Aug 2022 04:48:17 -0400 X-MC-Unique: Yeqpuf_3Ngep_gSMOePBeA-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 46FF28037AF; Mon, 22 Aug 2022 08:48:17 +0000 (UTC) Received: from warthog.procyon.org.uk (unknown [10.33.36.72]) by smtp.corp.redhat.com (Postfix) with ESMTP id 530E74010D2A; Mon, 22 Aug 2022 08:48:15 +0000 (UTC) Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: <20220821125751.4185-1-yin31149@gmail.com> References: <20220821125751.4185-1-yin31149@gmail.com> <000000000000ce327f05d537ebf7@google.com> To: Hawkins Jiawei Cc: dhowells@redhat.com, syzbot+7f0483225d0c94cb3441@syzkaller.appspotmail.com, Marc Dionne , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com, linux-kernel-mentees@lists.linuxfoundation.org, paskripkin@gmail.com, skhan@linuxfoundation.org, 18801353760@163.com Subject: Re: [PATCH] rxrpc: fix bad unlock balance in rxrpc_do_sendmsg MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <924817.1661158094.1@warthog.procyon.org.uk> Date: Mon, 22 Aug 2022 09:48:14 +0100 Message-ID: <924818.1661158094@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 2.84 on 10.11.54.2 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hawkins Jiawei wrote: > - if (mutex_lock_interruptible(&call->user_mutex) < 0) > + if (mutex_lock_interruptible(&call->user_mutex) < 0) { > + mutex_lock(&call->user_mutex); Yeah, as Khalid points out that kind of makes the interruptible lock pointless. Either rxrpc_send_data() needs to return a separate indication that we returned without the lock held or it needs to always drop the lock on error (at least for ERESTARTSYS/EINTR) which can be checked for higher up. David