Received: by 2002:a05:6a10:9afc:0:0:0:0 with SMTP id t28csp720686pxm; Fri, 25 Feb 2022 18:16:50 -0800 (PST) X-Google-Smtp-Source: ABdhPJySSiBi9aEjH7Yil1uarKF5rc7+eGUun8AkFDxemp8x6rIP1/3X2Xw2dyZY1iIVtYy0vw42 X-Received: by 2002:a63:fa0d:0:b0:372:d581:e84 with SMTP id y13-20020a63fa0d000000b00372d5810e84mr8382469pgh.414.1645841810387; Fri, 25 Feb 2022 18:16:50 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645841810; cv=none; d=google.com; s=arc-20160816; b=EhXuOSva19QKX6uv4kL1vqQvfAVvaZwR9FNs4d653F3nVEf9F+lhW6CA7+DozemkaM cddINqHxaDrMeZN1qNy1N5hOSrnEPjrKSc8w04HP/cVTXDMMZrFSvd8mc7FV4LxHd+kh iL8ebMohGr1Uv9505Y1+6CBbUCc430PpVHMBGhY7zI7pGvtnWci7VBBV2B/YgirKfbFe 5dt0l9Oheo3FvZyeHaGEirx7csvrArtpB4D1OSpzbbJ2XwKvJ2Z0EpdAf5LGhxWB9BHE l1ChEv9bIe3wJnvHBhq8Uf8856cVR7UapPqaTsFKtqnx26SFHltABEM0YjvWZw/FlFbT H53Q== 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:mail-followup-to:reply-to:message-id :subject:cc:to:from:date:dkim-signature:dkim-signature; bh=xtE+k70TidQoWi4j72BLWUm5533B5JQEZRp6zQv++Vg=; b=JuVIKFGsqlFTYmO45jfOy0AEkPTpwSU7QZPhVPGMJvSCpecCerho1CoAcehJnB9xVd AmmVjVNF5EVb6w8QNjGab03Xa2goXIzV7/zpSpTi7bhcCi/OmPalA4xgSIUHVKHu5a0Z tbZmv8SjI8EsJ+EOElAejUn+OQLj5TivSaX0hy5MfJ1cuX7uh3eIXxEcNibIF6/ckP8c U+tySX+kdtdCEOo4IoaZKxgj03rc58kBXoejt82PMKzhmow89uLcSWj31it20cPpe2dv mZij2A8zRy4FmAIRprJTiiolnDe/VWrAolGyvyRCh9PDKBNxP3KqVbFVsXARaxuS1PP/ Y/Zw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.cz header.s=susede2_rsa header.b=cqGbabts; dkim=neutral (no key) header.i=@suse.cz header.s=susede2_ed25519; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [23.128.96.19]) by mx.google.com with ESMTPS id e18-20020a17090301d200b0014fc71eb981si3394834plh.501.2022.02.25.18.16.50 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 25 Feb 2022 18:16:50 -0800 (PST) Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19; Authentication-Results: mx.google.com; dkim=pass header.i=@suse.cz header.s=susede2_rsa header.b=cqGbabts; dkim=neutral (no key) header.i=@suse.cz header.s=susede2_ed25519; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 2C3332BE219; Fri, 25 Feb 2022 17:50:00 -0800 (PST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240487AbiBYMEP (ORCPT + 99 others); Fri, 25 Feb 2022 07:04:15 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48722 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S240459AbiBYMEG (ORCPT ); Fri, 25 Feb 2022 07:04:06 -0500 Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 53C1C1B84E9; Fri, 25 Feb 2022 04:03:35 -0800 (PST) Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out2.suse.de (Postfix) with ESMTP id 02E941F380; Fri, 25 Feb 2022 12:03:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1645790614; h=from:from:reply-to:reply-to: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=xtE+k70TidQoWi4j72BLWUm5533B5JQEZRp6zQv++Vg=; b=cqGbabtspkxrbOc1xI1LRqg89EFUz/W0dSxa1Arw46Ca0MCA2fTnD+xwzfxtgNYJwkt3sN 8mKl13lL4fwVSmE39D4b/vLhXsaWaxVUm697H3HKe8yTUA2wprUwy1Z972p1n/yqjxfQ8x LhZkHL7TKJrf4xIDI2mFy9KXfnrEMo4= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1645790614; h=from:from:reply-to:reply-to: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=xtE+k70TidQoWi4j72BLWUm5533B5JQEZRp6zQv++Vg=; b=05jhUNWeAHGEyV3bFElcwMeV3zL2RiSqWWzpzY9DNFCSiEzkBf9mGtAciG0ymfNofs6paf 7UALELV7SVI00aDg== Received: from ds.suse.cz (ds.suse.cz [10.100.12.205]) by relay2.suse.de (Postfix) with ESMTP id EBBC4A3B8D; Fri, 25 Feb 2022 12:03:33 +0000 (UTC) Received: by ds.suse.cz (Postfix, from userid 10065) id 9B74FDA818; Fri, 25 Feb 2022 12:59:44 +0100 (CET) Date: Fri, 25 Feb 2022 12:59:44 +0100 From: David Sterba To: broonie@kernel.org Cc: David Sterba , Linux Kernel Mailing List , Linux Next Mailing List , Qu Wenruo , =?utf-8?B?RMSBdmlzIE1vc8SBbnM=?= Subject: Re: linux-next: manual merge of the btrfs tree with the btrfs-fixes tree Message-ID: <20220225115944.GF12643@suse.cz> Reply-To: dsterba@suse.cz Mail-Followup-To: dsterba@suse.cz, broonie@kernel.org, David Sterba , Linux Kernel Mailing List , Linux Next Mailing List , Qu Wenruo , =?utf-8?B?RMSBdmlzIE1vc8SBbnM=?= References: <20220224134427.3208381-1-broonie@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220224134427.3208381-1-broonie@kernel.org> User-Agent: Mutt/1.5.23.1-rc1 (2014-03-12) X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RDNS_NONE,SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=no 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 Thu, Feb 24, 2022 at 01:44:27PM +0000, broonie@kernel.org wrote: > Hi all, > > Today's linux-next merge of the btrfs tree got conflicts in: > > fs/btrfs/ctree.h > fs/btrfs/file.c > fs/btrfs/inode.c > fs/btrfs/ioctl.c > fs/btrfs/lzo.c > > between commit: > > 2ac3e062af024 ("btrfs: reduce extent threshold for autodefrag") > 741b23a970a79 ("btrfs: prevent copying too big compressed lzo segment") > 26fbac2517fca ("btrfs: autodefrag: only scan one inode once") > 966d879bafaaf ("btrfs: defrag: allow defrag_one_cluster() to skip large extent which is not a target") > d5633b0dee02d ("btrfs: defrag: bring back the old file extent search behavior") > > from the btrfs-fixes tree and commit: > > 13b2f7ab699a5 ("btrfs: close the gap between inode_should_defrag() and autodefrag extent size threshold") > 48b433a2ef82a ("btrfs: add lzo workspace buffer length constants") > db360c49d476f ("btrfs: autodefrag: only scan one inode once") > e6c69fcbee7ef ("btrfs: defrag: use control structure in btrfs_defrag_file()") > 6b17743d934ec ("btrfs: defrag: bring back the old file extent search behavior") > > from the btrfs tree. The fixes and for-next snapshot branches got out of sync a bit, I've checked that they merge without conflicts as of yesterday.