[v3,1/3] ext4: fix incorrect calculate 'reserved' in '__es_remove_extent' when enable bigalloc feature
Message ID | 20221203025941.2661302-2-yebin@huaweicloud.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:adf:f944:0:0:0:0:0 with SMTP id q4csp1177746wrr; Fri, 2 Dec 2022 18:42:40 -0800 (PST) X-Google-Smtp-Source: AA0mqf5maOpgViLwY8OTwKElNvjoHGCyf/rohxamEBJjEMZY7ICWEYr/Ws6TSgfuSnxuGANUu0ik X-Received: by 2002:a17:903:3052:b0:189:651c:f023 with SMTP id u18-20020a170903305200b00189651cf023mr40216550pla.78.1670035360282; Fri, 02 Dec 2022 18:42:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1670035360; cv=none; d=google.com; s=arc-20160816; b=nb+Y7lo03s5RC0dNwp1srsbnLKTQmzYI1zUk6TR9d0ffL3BkbV6kG0TzU8zTWpWOQg lv8Defq6kmRiOKB3M99g1LRh+ionZO7KhSzWC1hC0ZS5QIXJJoz9jvKlfqKkaLarJJkm lsdBeqe/HqkbpAXeGRvpkEx2O4jCB28fAL72NmC2Di3uUCpeoosVdmUSp2vKkOXtAKVt 0GBA9qk8Qe3ZIyai1HToKW/VaXC69um/XwQMqBtDnUv/csU2bqY0zmOcwj7r5KltzshV 2nBUU5+QHtu9c8N4ilXV/Ln5pGfPA2EDRwx9ws5206hZJqyTskqQgX3F97lhD2XZHAHF bJYQ== 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 :references:in-reply-to:message-id:date:subject:cc:to:from; bh=QwLVCnorOx9RTIPk9aJh0KkTp4DaqH8NSA/oA68UZCM=; b=uVuRZ9cd6M8SgxrtkDJH7b0WMl/QWOyK9ywyB6zRXkGZ02DfdPT2UHFiLl6SuPcU+s 17vX4Svrt1sBjLmcM8AB2jE+AG1Qv2RsVrtQHVi4NLYnzHOHZ2lVHKKUFI788IWsfglE lQhyoR72ohzQBEuCLCnop26XXVc5b6HWUGvC7fw7VK+GEkcbZ5ov+UsBrFwF3wg3RGd7 6jsA7BiUS2ZAX2XsZZc/Jl9EvprTmJgxeaLRm+Z1OIE7Nz7YnLy6HtOQh6XCSoIKUY7b OLsvFdRQjyZTaVtJo4nHElCnuog+3F/hrPpnj65aRDFiZAzgC5t0vH9UfwGgORugjFRw SBnQ== 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 Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id p6-20020a170902ebc600b00187085e0aacsi8450366plg.549.2022.12.02.18.42.27; Fri, 02 Dec 2022 18:42:40 -0800 (PST) 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 S235235AbiLCCiv (ORCPT <rfc822;lhua1029@gmail.com> + 99 others); Fri, 2 Dec 2022 21:38:51 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56780 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235190AbiLCCip (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Fri, 2 Dec 2022 21:38:45 -0500 Received: from dggsgout11.his.huawei.com (dggsgout11.his.huawei.com [45.249.212.51]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 374CDEC096; Fri, 2 Dec 2022 18:38:44 -0800 (PST) Received: from mail02.huawei.com (unknown [172.30.67.153]) by dggsgout11.his.huawei.com (SkyGuard) with ESMTP id 4NPDWy3QBcz4f3p15; Sat, 3 Dec 2022 10:38:38 +0800 (CST) Received: from huaweicloud.com (unknown [10.175.127.227]) by APP4 (Coremail) with SMTP id gCh0CgDXSNavtopjXug+Bg--.58501S5; Sat, 03 Dec 2022 10:38:41 +0800 (CST) From: Ye Bin <yebin@huaweicloud.com> To: tytso@mit.edu, adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org Cc: linux-kernel@vger.kernel.org, jack@suse.cz, Ye Bin <yebin10@huawei.com>, syzbot+05a0f0ccab4a25626e38@syzkaller.appspotmail.com Subject: [PATCH v3 1/3] ext4: fix incorrect calculate 'reserved' in '__es_remove_extent' when enable bigalloc feature Date: Sat, 3 Dec 2022 10:59:39 +0800 Message-Id: <20221203025941.2661302-2-yebin@huaweicloud.com> X-Mailer: git-send-email 2.31.1 In-Reply-To: <20221203025941.2661302-1-yebin@huaweicloud.com> References: <20221203025941.2661302-1-yebin@huaweicloud.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-CM-TRANSID: gCh0CgDXSNavtopjXug+Bg--.58501S5 X-Coremail-Antispam: 1UD129KBjvJXoWxJF1UXr1rXF4UJF45CryrCrg_yoW5Jr45p3 y8Ar4UWryfuw1UW3yftw1j9rn29a4UCr47WFs3t343uFy5A3sagr10kFs0vFWYqrWIgw4D XFWrtw12q3WUGaDanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUvGb4IE77IF4wAFF20E14v26ryj6rWUM7CY07I20VC2zVCF04k2 6cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28IrcIa0xkI8VA2jI8067AKxVWUGw A2048vs2IY020Ec7CjxVAFwI0_JFI_Gr1l8cAvFVAK0II2c7xJM28CjxkF64kEwVA0rcxS w2x7M28EF7xvwVC0I7IYx2IY67AKxVWDJVCq3wA2z4x0Y4vE2Ix0cI8IcVCY1x0267AKxV W8Jr0_Cr1UM28EF7xvwVC2z280aVAFwI0_GcCE3s1l84ACjcxK6I8E87Iv6xkF7I0E14v2 6rxl6s0DM2AIxVAIcxkEcVAq07x20xvEncxIr21l5I8CrVACY4xI64kE6c02F40Ex7xfMc Ij6xIIjxv20xvE14v26r1j6r18McIj6I8E87Iv67AKxVWUJVW8JwAm72CE4IkC6x0Yz7v_ Jr0_Gr1lF7xvr2IYc2Ij64vIr41l42xK82IYc2Ij64vIr41l4I8I3I0E4IkC6x0Yz7v_Jr 0_Gr1lx2IqxVAqx4xG67AKxVWUJVWUGwC20s026x8GjcxK67AKxVWUGVWUWwC2zVAF1VAY 17CE14v26r126r1DMIIYrxkI7VAKI48JMIIF0xvE2Ix0cI8IcVAFwI0_Jr0_JF4lIxAIcV C0I7IYx2IY6xkF7I0E14v26r4j6F4UMIIF0xvE42xK8VAvwI8IcIk0rVWUJVWUCwCI42IY 6I8E87Iv67AKxVWUJVW8JwCI42IY6I8E87Iv6xkF7I0E14v26r4j6r4UJbIYCTnIWIevJa 73UjIFyTuYvjxUzl1vUUUUU X-CM-SenderInfo: p1hex046kxt4xhlfz01xgou0bp/ X-CFilter-Loop: Reflected X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, 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: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1751158998433488962?= X-GMAIL-MSGID: =?utf-8?q?1751158998433488962?= |
Series |
Fix two issues about bigalloc feature
|
|
Commit Message
Ye Bin
Dec. 3, 2022, 2:59 a.m. UTC
From: Ye Bin <yebin10@huawei.com> Syzbot report issue as follows: EXT4-fs error (device loop0): ext4_validate_block_bitmap:398: comm rep: bg 0: block 5: invalid block bitmap EXT4-fs (loop0): Delayed block allocation failed for inode 18 at logical offset 0 with max blocks 32 with error 28 EXT4-fs (loop0): This should not happen!! Data will be lost EXT4-fs (loop0): Total free blocks count 0 EXT4-fs (loop0): Free/Dirty block details EXT4-fs (loop0): free_blocks=0 EXT4-fs (loop0): dirty_blocks=32 EXT4-fs (loop0): Block reservation details EXT4-fs (loop0): i_reserved_data_blocks=2 EXT4-fs (loop0): Inode 18 (00000000845cd634): i_reserved_data_blocks (1) not cleared! Above issue happens as follows: Assume: sbi->s_cluster_ratio = 16 Step1: Insert delay block [0, 31] -> ei->i_reserved_data_blocks=2 Step2: ext4_writepages mpage_map_and_submit_extent -> return failed mpage_release_unused_pages -> to release [0, 30] ext4_es_remove_extent -> remove lblk=0 end=30 __es_remove_extent -> len1=0 len2=31-30=1 __es_remove_extent: ... if (len2 > 0) { ... if (len1 > 0) { ... } else { es->es_lblk = end + 1; es->es_len = len2; ... } if (count_reserved) count_rsvd(inode, lblk, orig_es.es_len - len1 - len2, &orig_es, &rc); goto out; -> will return but didn't calculate 'reserved' ... Step3: ext4_destroy_inode -> trigger "i_reserved_data_blocks (1) not cleared!" To solve above issue if 'len2>0' call 'get_rsvd()' before goto out. Reported-by: syzbot+05a0f0ccab4a25626e38@syzkaller.appspotmail.com Fixes: 8fcc3a580651 ("ext4: rework reserved cluster accounting when invalidating pages") Signed-off-by: Ye Bin <yebin10@huawei.com> --- fs/ext4/extents_status.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
Comments
* Ye Bin <yebin@huaweicloud.com>: > From: Ye Bin <yebin10@huawei.com> > > Syzbot report issue as follows: > EXT4-fs error (device loop0): ext4_validate_block_bitmap:398: comm rep: bg 0: block 5: invalid block bitmap > EXT4-fs (loop0): Delayed block allocation failed for inode 18 at logical offset 0 with max blocks 32 with error 28 > EXT4-fs (loop0): This should not happen!! Data will be lost > > EXT4-fs (loop0): Total free blocks count 0 > EXT4-fs (loop0): Free/Dirty block details > EXT4-fs (loop0): free_blocks=0 > EXT4-fs (loop0): dirty_blocks=32 > EXT4-fs (loop0): Block reservation details > EXT4-fs (loop0): i_reserved_data_blocks=2 > EXT4-fs (loop0): Inode 18 (00000000845cd634): i_reserved_data_blocks (1) not cleared! > > Above issue happens as follows: > Assume: > sbi->s_cluster_ratio = 16 > Step1: Insert delay block [0, 31] -> ei->i_reserved_data_blocks=2 > Step2: > ext4_writepages > mpage_map_and_submit_extent -> return failed > mpage_release_unused_pages -> to release [0, 30] > ext4_es_remove_extent -> remove lblk=0 end=30 > __es_remove_extent -> len1=0 len2=31-30=1 > __es_remove_extent: > ... > if (len2 > 0) { > ... > if (len1 > 0) { > ... > } else { > es->es_lblk = end + 1; > es->es_len = len2; > ... > } > if (count_reserved) > count_rsvd(inode, lblk, orig_es.es_len - len1 - len2, &orig_es, &rc); > goto out; -> will return but didn't calculate 'reserved' > ... > Step3: ext4_destroy_inode -> trigger "i_reserved_data_blocks (1) not cleared!" > > To solve above issue if 'len2>0' call 'get_rsvd()' before goto out. > > Reported-by: syzbot+05a0f0ccab4a25626e38@syzkaller.appspotmail.com > Fixes: 8fcc3a580651 ("ext4: rework reserved cluster accounting when invalidating pages") > Signed-off-by: Ye Bin <yebin10@huawei.com> > --- > fs/ext4/extents_status.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/fs/ext4/extents_status.c b/fs/ext4/extents_status.c > index cd0a861853e3..7ada374ff27d 100644 > --- a/fs/ext4/extents_status.c > +++ b/fs/ext4/extents_status.c > @@ -1371,7 +1371,7 @@ static int __es_remove_extent(struct inode *inode, ext4_lblk_t lblk, > if (count_reserved) > count_rsvd(inode, lblk, orig_es.es_len - len1 - len2, > &orig_es, &rc); > - goto out; > + goto out_get_reserved; > } > > if (len1 > 0) { > @@ -1413,6 +1413,7 @@ static int __es_remove_extent(struct inode *inode, ext4_lblk_t lblk, > } > } > > +out_get_reserved: > if (count_reserved) > *reserved = get_rsvd(inode, end, es, &rc); > out: The length of some lines in the commit description - probably those which are log output - is resulting in a checkpatch warning. It generally prefers lines to be a maximum of 75 characters (and Ted usually likes them limited to 72 characters. See my comment to patch #3. I'm not sure what Ted would want here, though I'd probably break them at 72 characters or less. Otherwise, the patch looks good. Feel free to add: Reviewed-by: Eric Whitney <enwlinux@gmail.com> > -- > 2.31.1 >
* Eric Whitney <enwlinux@gmail.com>: > * Ye Bin <yebin@huaweicloud.com>: > > From: Ye Bin <yebin10@huawei.com> > > > > Syzbot report issue as follows: > > EXT4-fs error (device loop0): ext4_validate_block_bitmap:398: comm rep: bg 0: block 5: invalid block bitmap > > EXT4-fs (loop0): Delayed block allocation failed for inode 18 at logical offset 0 with max blocks 32 with error 28 > > EXT4-fs (loop0): This should not happen!! Data will be lost > > > > EXT4-fs (loop0): Total free blocks count 0 > > EXT4-fs (loop0): Free/Dirty block details > > EXT4-fs (loop0): free_blocks=0 > > EXT4-fs (loop0): dirty_blocks=32 > > EXT4-fs (loop0): Block reservation details > > EXT4-fs (loop0): i_reserved_data_blocks=2 > > EXT4-fs (loop0): Inode 18 (00000000845cd634): i_reserved_data_blocks (1) not cleared! > > > > Above issue happens as follows: > > Assume: > > sbi->s_cluster_ratio = 16 > > Step1: Insert delay block [0, 31] -> ei->i_reserved_data_blocks=2 > > Step2: > > ext4_writepages > > mpage_map_and_submit_extent -> return failed > > mpage_release_unused_pages -> to release [0, 30] > > ext4_es_remove_extent -> remove lblk=0 end=30 > > __es_remove_extent -> len1=0 len2=31-30=1 > > __es_remove_extent: > > ... > > if (len2 > 0) { > > ... > > if (len1 > 0) { > > ... > > } else { > > es->es_lblk = end + 1; > > es->es_len = len2; > > ... > > } > > if (count_reserved) > > count_rsvd(inode, lblk, orig_es.es_len - len1 - len2, &orig_es, &rc); > > goto out; -> will return but didn't calculate 'reserved' > > ... > > Step3: ext4_destroy_inode -> trigger "i_reserved_data_blocks (1) not cleared!" > > > > To solve above issue if 'len2>0' call 'get_rsvd()' before goto out. > > > > Reported-by: syzbot+05a0f0ccab4a25626e38@syzkaller.appspotmail.com > > Fixes: 8fcc3a580651 ("ext4: rework reserved cluster accounting when invalidating pages") > > Signed-off-by: Ye Bin <yebin10@huawei.com> > > --- > > fs/ext4/extents_status.c | 3 ++- > > 1 file changed, 2 insertions(+), 1 deletion(-) > > > > diff --git a/fs/ext4/extents_status.c b/fs/ext4/extents_status.c > > index cd0a861853e3..7ada374ff27d 100644 > > --- a/fs/ext4/extents_status.c > > +++ b/fs/ext4/extents_status.c > > @@ -1371,7 +1371,7 @@ static int __es_remove_extent(struct inode *inode, ext4_lblk_t lblk, > > if (count_reserved) > > count_rsvd(inode, lblk, orig_es.es_len - len1 - len2, > > &orig_es, &rc); > > - goto out; > > + goto out_get_reserved; > > } > > > > if (len1 > 0) { > > @@ -1413,6 +1413,7 @@ static int __es_remove_extent(struct inode *inode, ext4_lblk_t lblk, > > } > > } > > > > +out_get_reserved: > > if (count_reserved) > > *reserved = get_rsvd(inode, end, es, &rc); > > out: > > The length of some lines in the commit description - probably those which are > log output - is resulting in a checkpatch warning. It generally prefers lines > to be a maximum of 75 characters (and Ted usually likes them limited to 72 > characters. See my comment to patch #3. I'm not sure what Ted would want here, > though I'd probably break them at 72 characters or less. > > Otherwise, the patch looks good. Feel free to add: > Looks good. As before, feel free to add: > Reviewed-by: Eric Whitney <enwlinux@gmail.com> > > > -- > > 2.31.1 > >
* Eric Whitney <enwlinux@gmail.com>: > * Eric Whitney <enwlinux@gmail.com>: > > * Ye Bin <yebin@huaweicloud.com>: > > > From: Ye Bin <yebin10@huawei.com> > > > > > > Syzbot report issue as follows: > > > EXT4-fs error (device loop0): ext4_validate_block_bitmap:398: comm rep: bg 0: block 5: invalid block bitmap > > > EXT4-fs (loop0): Delayed block allocation failed for inode 18 at logical offset 0 with max blocks 32 with error 28 > > > EXT4-fs (loop0): This should not happen!! Data will be lost > > > > > > EXT4-fs (loop0): Total free blocks count 0 > > > EXT4-fs (loop0): Free/Dirty block details > > > EXT4-fs (loop0): free_blocks=0 > > > EXT4-fs (loop0): dirty_blocks=32 > > > EXT4-fs (loop0): Block reservation details > > > EXT4-fs (loop0): i_reserved_data_blocks=2 > > > EXT4-fs (loop0): Inode 18 (00000000845cd634): i_reserved_data_blocks (1) not cleared! > > > > > > Above issue happens as follows: > > > Assume: > > > sbi->s_cluster_ratio = 16 > > > Step1: Insert delay block [0, 31] -> ei->i_reserved_data_blocks=2 > > > Step2: > > > ext4_writepages > > > mpage_map_and_submit_extent -> return failed > > > mpage_release_unused_pages -> to release [0, 30] > > > ext4_es_remove_extent -> remove lblk=0 end=30 > > > __es_remove_extent -> len1=0 len2=31-30=1 > > > __es_remove_extent: > > > ... > > > if (len2 > 0) { > > > ... > > > if (len1 > 0) { > > > ... > > > } else { > > > es->es_lblk = end + 1; > > > es->es_len = len2; > > > ... > > > } > > > if (count_reserved) > > > count_rsvd(inode, lblk, orig_es.es_len - len1 - len2, &orig_es, &rc); > > > goto out; -> will return but didn't calculate 'reserved' > > > ... > > > Step3: ext4_destroy_inode -> trigger "i_reserved_data_blocks (1) not cleared!" > > > > > > To solve above issue if 'len2>0' call 'get_rsvd()' before goto out. > > > > > > Reported-by: syzbot+05a0f0ccab4a25626e38@syzkaller.appspotmail.com > > > Fixes: 8fcc3a580651 ("ext4: rework reserved cluster accounting when invalidating pages") > > > Signed-off-by: Ye Bin <yebin10@huawei.com> > > > --- > > > fs/ext4/extents_status.c | 3 ++- > > > 1 file changed, 2 insertions(+), 1 deletion(-) > > > > > > diff --git a/fs/ext4/extents_status.c b/fs/ext4/extents_status.c > > > index cd0a861853e3..7ada374ff27d 100644 > > > --- a/fs/ext4/extents_status.c > > > +++ b/fs/ext4/extents_status.c > > > @@ -1371,7 +1371,7 @@ static int __es_remove_extent(struct inode *inode, ext4_lblk_t lblk, > > > if (count_reserved) > > > count_rsvd(inode, lblk, orig_es.es_len - len1 - len2, > > > &orig_es, &rc); > > > - goto out; > > > + goto out_get_reserved; > > > } > > > > > > if (len1 > 0) { > > > @@ -1413,6 +1413,7 @@ static int __es_remove_extent(struct inode *inode, ext4_lblk_t lblk, > > > } > > > } > > > > > > +out_get_reserved: > > > if (count_reserved) > > > *reserved = get_rsvd(inode, end, es, &rc); > > > out: > > > > The length of some lines in the commit description - probably those which are > > log output - is resulting in a checkpatch warning. It generally prefers lines > > to be a maximum of 75 characters (and Ted usually likes them limited to 72 > > characters. See my comment to patch #3. I'm not sure what Ted would want here, > > though I'd probably break them at 72 characters or less. > > > > Otherwise, the patch looks good. Feel free to add: > > > > Looks good. As before, feel free to add: > > > Reviewed-by: Eric Whitney <enwlinux@gmail.com> > Whoops. Please disregard - wrong patch. Eric
diff --git a/fs/ext4/extents_status.c b/fs/ext4/extents_status.c index cd0a861853e3..7ada374ff27d 100644 --- a/fs/ext4/extents_status.c +++ b/fs/ext4/extents_status.c @@ -1371,7 +1371,7 @@ static int __es_remove_extent(struct inode *inode, ext4_lblk_t lblk, if (count_reserved) count_rsvd(inode, lblk, orig_es.es_len - len1 - len2, &orig_es, &rc); - goto out; + goto out_get_reserved; } if (len1 > 0) { @@ -1413,6 +1413,7 @@ static int __es_remove_extent(struct inode *inode, ext4_lblk_t lblk, } } +out_get_reserved: if (count_reserved) *reserved = get_rsvd(inode, end, es, &rc); out: