Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp1334206rwb; Tue, 4 Oct 2022 20:19:08 -0700 (PDT) X-Google-Smtp-Source: AMsMyM4IpXegqffCpe4H9mbAzisDJ90benGHCKVhJNzwrrj4mqV02FNH1y9Adr+YIN173hPt0Z2a X-Received: by 2002:aa7:c04f:0:b0:457:1b08:d056 with SMTP id k15-20020aa7c04f000000b004571b08d056mr27536743edo.146.1664939948317; Tue, 04 Oct 2022 20:19:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1664939948; cv=none; d=google.com; s=arc-20160816; b=v22aHkcHzGoh9uDM9rJu9Z6foDKH1+BqimtjFUNPBulVepkkmaPwGuT1drengOjKM9 APnKFfO99GJ4VO6Sb6uMP9HglSLnoI4qrkf7BBU5M4QwUhMKIEPqvx7uJP23bVH3NkWn SPYsKVh4bzLgU8gLlmlUZwCLXYlTrVzvVD+wQR5RlARM4ZWhHA3YcVtUCMgVZOyqflmm o5K0NHjZWg6XmWbYKiRrXsrbAf/mYcd/53i55q0tzH70ADOsF2USaZ4yv67JskVtxAeP amd0ys+z5OxqV7zQYikrTsrb0W9K5GuEN7dK/ADheDuduJ4MbWCsAANUidNwQFpFt07k 8XDQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=O3h07fEmby9KDUUKSBDJWzJBkBqccKKOaK9Kt/KSxd8=; b=B82vl6/I8nwWyIK35Aytm9HC3Ur1jfx5BSlbRYQNUacYxyEkt1eJVZ5Gs0aCJW+bho oBTlMhcJoWXsNx7UA38PKCfzRgHcaFeAGN73cnNePG7jKvYfDGJ3bYrr++gr5MhG1eWu aXM74lDNbLEK3uLvgwOa57sTuH/cvC/cLIIlGePBO5WINYQFlZjUsKzWfZhXByUGhy7E LNOShyhW90WJ64WvkRuaSDY/8azQs0W5PJYV331qfDXAX4//7gR+KjwydvOq8v+XKiJK byunGds4mp0+c0Iq4gPKoJr6LnBjcR5HDDH+gdln1DfobXmFD8t124v9T2zODoo7RSvN OyFQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id hc42-20020a17090716aa00b0077ab738911fsi13115922ejc.140.2022.10.04.20.18.42; Tue, 04 Oct 2022 20:19:08 -0700 (PDT) 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; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229573AbiJEDOJ (ORCPT + 99 others); Tue, 4 Oct 2022 23:14:09 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42976 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229518AbiJEDOG (ORCPT ); Tue, 4 Oct 2022 23:14:06 -0400 Received: from 1wt.eu (wtarreau.pck.nerim.net [62.212.114.60]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id C4165696D7; Tue, 4 Oct 2022 20:14:02 -0700 (PDT) Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id 2953DaIv003171; Wed, 5 Oct 2022 05:13:36 +0200 Date: Wed, 5 Oct 2022 05:13:36 +0200 From: Willy Tarreau To: "Darrick J. Wong" Cc: Stephen Zhang , Dave Chinner , Stephen Rothwell , linux-xfs@vger.kernel.org, Shida Zhang , Linux Kernel Mailing List , Linux Next Mailing List Subject: Re: linux-next: Signed-off-by missing for commit in the xfs tree Message-ID: <20221005031336.GA3161@1wt.eu> References: <20221004072302.345bfd4a@canb.auug.org.au> <20221003222103.GM3600936@dread.disaster.area> <20221004225012.501e11ed@canb.auug.org.au> <20221004210400.GO3600936@dread.disaster.area> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS, SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 04, 2022 at 08:01:26PM -0700, Darrick J. Wong wrote: > I think Dave means something like this patch of mine: > https://lore.kernel.org/linux-xfs/166473478893.1083155.2555785331844801316.stgit@magnolia/T/#u > > From: "Darrick J. Wong" > To: djwong@kernel.org > Cc: linux-xfs@vger.kernel.org > Date: Sun, 02 Oct 2022 11:19:48 -0700 > Subject: [PATCH 3/4] xfs: set the buffer type after holding the AG[IF] across trans_roll > > From: Darrick J. Wong > > Currently, the only way to lock an allocation group is to hold the AGI > and AGF buffers. If repair needs to roll the transaction while > repairing some AG metadata, it maintains that lock by holding the two > buffers across the transaction roll and joins them afterwards. > > However, repair is not the same as the other parts of XFS that employ > this bhold/bjoin sequence, because it's possible that the AGI or AGF > buffers are not actually dirty before the roll. In this case, the > buffer log item can detach from the buffer, which means that we have to > re-set the buffer type in the bli after joining the buffer to the new > transaction so that log recovery will know what to do if the fs fails. > > Signed-off-by: Darrick J. Wong > --- > > Notice how after the Subject: there is a blank line (which terminates > the headers) followed by a new From: line in the body? And the > name/email in that second From: line matches the SOB later on? Or maybe we could have a new option to git-am to always use the first SOB as the From when there's no other explicit From in the message, so that we never care about the From used to send the e-mail ? That would also implicitly perform a requirement that an SOB necessarily exists. Willy