Received: by 2002:a05:6a10:17d3:0:0:0:0 with SMTP id hz19csp1172444pxb; Sun, 11 Apr 2021 09:50:17 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxNld5yJm4q+5ORKCK9tj0DXfbYWJdmF8sc1vmcG/SfRAKQbTLCsf+k6kLYsAmthE9BYcVy X-Received: by 2002:a17:907:1692:: with SMTP id hc18mr23762939ejc.265.1618159817120; Sun, 11 Apr 2021 09:50:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1618159817; cv=none; d=google.com; s=arc-20160816; b=KN4dgUUZrmWqWVXwRKJWgReqshFHnyyFAz+hcv0Ydr8Aq8xGpXgzNzioEknk1iYvky uDUrrbcFpKTKgc6QVFs8tG1CQ0wTcl22eRzGIxTpqfh16bd9rcK1yMGmrpVn0AO2PIr/ m1ov6L44qacT7cE+SK4BHt+7DFniIWDVLS8CodaXUml5yZC0DbYF6Pg9tT/IYZiGMXQS 00KNm4v7NOY0lJ1fh4eK/6+qSjVWZP/7uVRgmJRTIoYvdK91oFSbCNlFdcswLnS0LvVP 41C1KybptUFs6D2GqUmVGaFLb2yIzQpABov9TNUIyPfRvqBr8fImYbO+KVrTRjbXCMNl sh/A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=NRvrdUMQPsfy2+W9X3tI7YbnOGgdPIi8JAXEx3PrhwU=; b=SyGWweqYW3y7mB9J8aNTS7QjHqjmqW/XtRNc29uUCX0Pmt/SyKUuvKgzzchrK8rYIa gRKKkVjPHnCe25hbTOYhVTFqExdjDyMWb6MZCz0Zp/Ajxi1OQ7S0ViLREbIkg0OrbZF3 dk+LEeqakYGRzkkZG7eoM4gULVRhiD8IgEAsa2R64fCaBlp4n4X1ULDhvr1r6MaFCsAg ko/Oq2kNtgJa3hTohdYj5yG/TR7rSBsxLo+xhnfegr59+dN8ud1KV91e80NAbFcfno4g 90qH1DrdTMlgRevQM92v4S7Puf4SoETObKEvOJ6miiAyyj5HL1hg+pc8StNIZtlQiIJS 0byQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.com header.s=susede1 header.b=ZVLkF0cl; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=suse.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id j17si5243093edw.478.2021.04.11.09.49.54; Sun, 11 Apr 2021 09:50:17 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@suse.com header.s=susede1 header.b=ZVLkF0cl; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=suse.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235466AbhDKN6O (ORCPT + 99 others); Sun, 11 Apr 2021 09:58:14 -0400 Received: from mx2.suse.de ([195.135.220.15]:51918 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233514AbhDKN6N (ORCPT ); Sun, 11 Apr 2021 09:58:13 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1618149476; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=NRvrdUMQPsfy2+W9X3tI7YbnOGgdPIi8JAXEx3PrhwU=; b=ZVLkF0clR8BNYNUsYrnxe1L3zWGyMAfnbMxjAq9cBhnYfYe2wTCQdbd8pd8F/0dhTm+fmV +CEbr1ei33YEx2a8kCQwR+jouHWbwEY8yueTaOt10wbCzm/+EdCQaso6ooioqWiMjVDVHg y4J9hfWaGM+TBBSq1hT0mvILBd8xPQY= Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 08140B1C3; Sun, 11 Apr 2021 13:57:56 +0000 (UTC) Received: by ds.suse.cz (Postfix, from userid 10065) id BA905DAF1F; Sun, 11 Apr 2021 15:55:41 +0200 (CEST) From: David Sterba To: torvalds@linux-foundation.org Cc: David Sterba , linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [GIT PULL] Btrfs fix for 5.12-rc7 Date: Sun, 11 Apr 2021 15:55:41 +0200 Message-Id: X-Mailer: git-send-email 2.29.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: David Sterba Hi, here's one more patch that we'd like to get to 5.12 before release, it's changing where and how the superblock is stored in the zoned mode. It is an on-disk format change but so far there are no implications for users as the proper mkfs support hasn't been merged and is waiting for the kernel side to settle. Until now, the superblocks were derived from the zone index, but zone size can differ per device. This is changed to be based on fixed offset values, to make it independent of the device zone size. The work on that got a bit delayed, we discussed the exact locations to support potential device sizes and usecases. (Partially delayed also due to my vacation.) Having that in the same release where the zoned mode is declared usable is highly desired, there are userspace projects that need to be updated to recognize the feature. Pushing that to the next release would make things harder to test. Please pull, thanks. ---------------------------------------------------------------- The following changes since commit c1d6abdac46ca8127274bea195d804e3f2cec7ee: btrfs: fix check_data_csum() error message for direct I/O (2021-03-18 21:25:11 +0100) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.12-rc6-tag for you to fetch changes up to 53b74fa990bf76f290aa5930abfcf37424a1a865: btrfs: zoned: move superblock logging zone location (2021-04-10 12:13:16 +0200) ---------------------------------------------------------------- Naohiro Aota (1): btrfs: zoned: move superblock logging zone location fs/btrfs/zoned.c | 53 ++++++++++++++++++++++++++++++++++++++++++----------- 1 file changed, 42 insertions(+), 11 deletions(-)