Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp790733pxu; Thu, 3 Dec 2020 12:43:03 -0800 (PST) X-Google-Smtp-Source: ABdhPJynTZDYzwdSRol2sev/JGhTGCSF2+Xmu+pGVxYy9NAyqZ2BDRXH1sus0q82CTk45FbWLWJ0 X-Received: by 2002:a17:906:9605:: with SMTP id s5mr3876685ejx.179.1607028182808; Thu, 03 Dec 2020 12:43:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1607028182; cv=none; d=google.com; s=arc-20160816; b=msEmWAADwHgAu9atvbOOm9G0mvCRej/UzwOBSIiCe+DcEmXObkHkxMoGuFcP0EaIM2 naD/s2z3fi0F3EpaVtkZIYpEs0d3NyGlGOtuoaiTYoE+6Dyvmpp4hVYVBPgx3ZAyXu5g 0uinnHaQ99JetEMA358nMyMuxvHI87y81TcO8v8+iVEz85SEZSMYU49nNZPvoawpCg8B T32d7X+K3ZingsNGTBHWdcAWje5kgMZ/zDNvemnUDX5gT8XpTPnoCdoG1pfF2hoHgmOI jVlCxeE4IWa2US65Oh5jQYiVtSkLX2GQ9pzdZKxhApq8zx/eXTjx4mlqHCXdDziZJqEI OAzw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=nqVvCkAZT7tjj37L0oDE44+4d6pGfum6jRVnuyvitb8=; b=NTA3Hjex1wNd31fbk/od4C97yCLl5EkYLcMW9xMJxtnugFBNGnTQnaS/81uSdOsh5Y gx0eok4KbiUfPFSsPLsA9oJz7SqxDpbQ+rhGzBs0g7kTaiO4JIZs0pGOK4Zq7exJ5w8P 1DHWgvrEtOWIaeu+a17IczHDklUpHeTkqMcEFEUvOVZOAX95z6jlTMrpt6RBhiiRZGw5 FBHMdeUt8gc7OkH+LVYBeYVGGL5j/xZfamcAAOJrYtZJ3OvZc6AZe+ZgKhc+BxBEEX8D oihEypn8JVoRwnak6dAb/LVOaFBwss4nj5On9K7IZWP+v5EU703kyMdKI4CJL1k2iC1C yrMQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id g18si1572438edh.40.2020.12.03.12.42.13; Thu, 03 Dec 2020 12:43:02 -0800 (PST) Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727844AbgLCUkL (ORCPT + 99 others); Thu, 3 Dec 2020 15:40:11 -0500 Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:42132 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726597AbgLCUkL (ORCPT ); Thu, 3 Dec 2020 15:40:11 -0500 Received: from callcc.thunk.org (pool-72-74-133-215.bstnma.fios.verizon.net [72.74.133.215]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 0B3KdGeL011944 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 3 Dec 2020 15:39:16 -0500 Received: by callcc.thunk.org (Postfix, from userid 15806) id 0E357420136; Thu, 3 Dec 2020 15:39:16 -0500 (EST) Date: Thu, 3 Dec 2020 15:39:15 -0500 From: "Theodore Y. Ts'o" To: Alexander Lochmann Cc: Horst Schirmeier , Jan Kara , linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3] Updated locking documentation for transaction_t Message-ID: <20201203203915.GN441757@mit.edu> References: <20190408083500.66759-1-alexander.lochmann@tu-dortmund.de> <10cfbef1-994c-c604-f8a6-b1042fcc622f@tu-dortmund.de> <20201203140405.GC441757@mit.edu> <29d6de5d-4abc-e836-7b14-bb67d782a752@tu-dortmund.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <29d6de5d-4abc-e836-7b14-bb67d782a752@tu-dortmund.de> Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org On Thu, Dec 03, 2020 at 03:38:40PM +0100, Alexander Lochmann wrote: > > > On 03.12.20 15:04, Theodore Y. Ts'o wrote: > > On Thu, Oct 15, 2020 at 03:26:28PM +0200, Alexander Lochmann wrote: > > > Hi folks, > > > > > > I've updated the lock documentation according to our finding for > > > transaction_t. > > > Does this patch look good to you? > > > > I updated the annotations to match with the local usage, e.g: > > > > * When commit was requested [journal_t.j_state_lock] > > > > became: > > > > * When commit was requested [j_state_lock]What do you mean by local usage? > The annotations of other members of transaction_t? Yes, I'd like the annotations of the other objects to be consistent, and just use j_state_lock, j_list_lock, etc., for the other annotations. > Shouldn't the annotation look like this? > [t_journal->j_state_lock] > It would be more precise. It's more precise, but it's also unnecessary in this case, since all of the elements of the journal have a j_ prefix, elements of a transaction_t have a t_ prefix, etc. There is also no other structure element which has a j_state_lock name *other* than in journal_t. Cheers, - Ted