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 0A828E8FDAF for ; Tue, 3 Oct 2023 19:45:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240965AbjJCTpg convert rfc822-to-8bit (ORCPT ); Tue, 3 Oct 2023 15:45:36 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35754 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230502AbjJCTpe (ORCPT ); Tue, 3 Oct 2023 15:45:34 -0400 Received: from lithops.sigma-star.at (lithops.sigma-star.at [195.201.40.130]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5C37E9E; Tue, 3 Oct 2023 12:45:30 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by lithops.sigma-star.at (Postfix) with ESMTP id 4C38C6340DF3; Tue, 3 Oct 2023 21:45:28 +0200 (CEST) Received: from lithops.sigma-star.at ([127.0.0.1]) by localhost (lithops.sigma-star.at [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 3ulYD1wGVKZI; Tue, 3 Oct 2023 21:45:28 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by lithops.sigma-star.at (Postfix) with ESMTP id EA3E26340E0F; Tue, 3 Oct 2023 21:45:27 +0200 (CEST) Received: from lithops.sigma-star.at ([127.0.0.1]) by localhost (lithops.sigma-star.at [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id mJfZ--EnOnn8; Tue, 3 Oct 2023 21:45:27 +0200 (CEST) Received: from lithops.sigma-star.at (lithops.sigma-star.at [195.201.40.130]) by lithops.sigma-star.at (Postfix) with ESMTP id C40526340DF3; Tue, 3 Oct 2023 21:45:27 +0200 (CEST) Date: Tue, 3 Oct 2023 21:45:27 +0200 (CEST) From: Richard Weinberger To: Daniel Golle Cc: Randy Dunlap , Miquel Raynal , Vignesh Raghavendra , Rob Herring , Krzysztof Kozlowski , Conor Dooley , linux-mtd , devicetree , linux-kernel Message-ID: <226381209.31782.1696362327615.JavaMail.zimbra@nod.at> In-Reply-To: References: Subject: Re: [PATCH v4 5/8] mtd: ubi: attach MTD partition from device-tree MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT X-Originating-IP: [195.201.40.130] X-Mailer: Zimbra 8.8.12_GA_3807 (ZimbraWebClient - FF97 (Linux)/8.8.12_GA_3809) Thread-Topic: attach MTD partition from device-tree Thread-Index: kqr0xqm+jR+lBv0FwDpbk9UYfLM3MQ== Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org ----- Ursprüngliche Mail ----- > diff --git a/drivers/mtd/ubi/block.c b/drivers/mtd/ubi/block.c > index e0618bbde3613..99b5f502c9dbc 100644 > --- a/drivers/mtd/ubi/block.c > +++ b/drivers/mtd/ubi/block.c > @@ -470,7 +470,7 @@ int ubiblock_remove(struct ubi_volume_info *vi, bool force) > } > > /* Found a device, let's lock it so we can check if it's busy */ > - mutex_lock(&dev->dev_mutex); > + mutex_lock_nested(&dev->dev_mutex, SINGLE_DEPTH_NESTING); The usage of mutex_lock_nested() in this patch looks fishy. Can you please elaborate a bit more why all these mutexes can be taken twice? (Any why not more often). Thanks, //richard