Message ID | 20230526074551.669792-2-linan666@huaweicloud.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:994d:0:b0:3d9:f83d:47d9 with SMTP id k13csp296347vqr; Fri, 26 May 2023 00:57:16 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ5MJjw4qZ0F5YvkR/6I9HggoSb7R8R47nOo7PncyaNw8aGgz8uPLTVMrWxVoQPysrIC1YU8 X-Received: by 2002:a05:6a21:78a9:b0:10b:7400:cef7 with SMTP id bf41-20020a056a2178a900b0010b7400cef7mr1512787pzc.17.1685087836153; Fri, 26 May 2023 00:57:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1685087836; cv=none; d=google.com; s=arc-20160816; b=A2h6isERfCu2Zz3HAHv8hJOLE1L3ICNj7x2hjttA82VWH0CVeBzpMRQyTiEZuW4Jug Sa5BCVXTShOU6kkd69CAnOiD7+hBunw56iaG28LM2Ay0gCrByM3GbRidj39QlQI6H71r z/+DnCJw8UAYrYI8m4P2pYXC3FEkbQIayFVXqy2DYkRA02/hfKM/d6BHLbKgPbyWvNac mU1Xfr5oSRZ1NPMSC+sX1sGHjeJIZqb22QxMIf+dFqApghF7+2etAR8In+lvV9SssxA4 VjZ1RVUDKyMbzEmtrky0CArLO4+8sFH0ab/TzCs6jDa9fN61+QiAyR0DjtXh/wfi6zM8 2eIQ== 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=aJ4ITCYClNiTO8Ep9Y1fg85PT736vuhQIVwUmvYuJIM=; b=Alo0emhkw+gfhU9UkVOMA4BU8bJLPCmu3PEyfr76bK5Wm9Uz6aDt1AyDj83inAisIj 64WYoOjMsFlWh0ylrl2YXc2omCW+mToudTdStR8ZOUiVBLMKMid+shUok4yJVuRod+Nk cSJnwRghXONwsYH/otw8zG9CaZh0O53OQdgLsdFTEhQOyBytLnwjiVbtoZSYH0YbxVxD JOTMXR2hPtO8C2UFUcPEz/rB/3jM8WHqw8iEaW37s3KdXIDNpu9809DgUZkJ3bQxyObp QJne2US7lXUj2ucr93Bc/lC00Fg8kDHIjKrRKRQH3HdzTPZOJO29dLoNct8ymnZDeJiP QtNg== 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 j8-20020a636e08000000b00534919e40fcsi2615796pgc.626.2023.05.26.00.57.01; Fri, 26 May 2023 00:57:16 -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 S242452AbjEZHrz (ORCPT <rfc822;zhanglyra.2023@gmail.com> + 99 others); Fri, 26 May 2023 03:47:55 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42446 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236059AbjEZHrj (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Fri, 26 May 2023 03:47:39 -0400 Received: from dggsgout11.his.huawei.com (dggsgout11.his.huawei.com [45.249.212.51]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2B45512C; Fri, 26 May 2023 00:47:36 -0700 (PDT) Received: from mail02.huawei.com (unknown [172.30.67.153]) by dggsgout11.his.huawei.com (SkyGuard) with ESMTP id 4QSH842JXdz4f41Vk; Fri, 26 May 2023 15:47:32 +0800 (CST) Received: from huaweicloud.com (unknown [10.175.127.227]) by APP4 (Coremail) with SMTP id gCh0CgCX_7INZHBko+n3KA--.7888S5; Fri, 26 May 2023 15:47:33 +0800 (CST) From: linan666@huaweicloud.com To: song@kernel.org, bingjingc@synology.com, allenpeng@synology.com, alexwu@synology.com, shli@fb.com, neilb@suse.de Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org, linan122@huawei.com, yukuai3@huawei.com, yi.zhang@huawei.com, houtao1@huawei.com, yangerkun@huawei.com Subject: [PATCH v2 1/4] md/raid10: fix null-ptr-deref of mreplace in raid10_sync_request Date: Fri, 26 May 2023 15:45:48 +0800 Message-Id: <20230526074551.669792-2-linan666@huaweicloud.com> X-Mailer: git-send-email 2.31.1 In-Reply-To: <20230526074551.669792-1-linan666@huaweicloud.com> References: <20230526074551.669792-1-linan666@huaweicloud.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-CM-TRANSID: gCh0CgCX_7INZHBko+n3KA--.7888S5 X-Coremail-Antispam: 1UD129KBjvJXoW7Kw47KrWDCF4UGry7Wr43GFg_yoW8trWfp3 y7tF9rGw4UG3yjka1DA3ZrWF1SvasrJrW5Cry5W343Zr1agrZrCay8WFWYvFyDXF4Yg3yY qw1jyws8uFWxXa7anT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUmjb4IE77IF4wAFF20E14v26rWj6s0DM7CY07I20VC2zVCF04k2 6cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28IrcIa0xkI8VA2jI8067AKxVWUGw A2048vs2IY020Ec7CjxVAFwI0_Gr0_Xr1l8cAvFVAK0II2c7xJM28CjxkF64kEwVA0rcxS w2x7M28EF7xvwVC0I7IYx2IY67AKxVWDJVCq3wA2z4x0Y4vE2Ix0cI8IcVCY1x0267AKxV W8Jr0_Cr1UM28EF7xvwVC2z280aVAFwI0_GcCE3s1l84ACjcxK6I8E87Iv6xkF7I0E14v2 6rxl6s0DM2vYz4IE04k24VAvwVAKI4IrM2AIxVAIcxkEcVAq07x20xvEncxIr21l5I8CrV ACY4xI64kE6c02F40Ex7xfMcIj6xIIjxv20xvE14v26r126r1DMcIj6I8E87Iv67AKxVWU JVW8JwAm72CE4IkC6x0Yz7v_Jr0_Gr1lF7xvr2IYc2Ij64vIr41lFIxGxcIEc7CjxVA2Y2 ka0xkIwI1lw4CEc2x0rVAKj4xxMxAIw28IcxkI7VAKI48JMxC20s026xCaFVCjc4AY6r1j 6r4UMI8I3I0E5I8CrVAFwI0_Jr0_Jr4lx2IqxVCjr7xvwVAFwI0_JrI_JrWlx4CE17CEb7 AF67AKxVWUtVW8ZwCIc40Y0x0EwIxGrwCI42IY6xIIjxv20xvE14v26r1j6r1xMIIF0xvE 2Ix0cI8IcVCY1x0267AKxVW8JVWxJwCI42IY6xAIw20EY4v20xvaj40_Jr0_JF4lIxAIcV C2z280aVAFwI0_Jr0_Gr1lIxAIcVC2z280aVCY1x0267AKxVW8JVW8JrUvcSsGvfC2Kfnx nUUI43ZEXa7IU8qg43UUUUU== X-CM-SenderInfo: polqt0awwwqx5xdzvxpfor3voofrz/ X-CFilter-Loop: Reflected X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE 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?1766942662532660634?= X-GMAIL-MSGID: =?utf-8?q?1766942662532660634?= |
Series |
raid10 bugfix
|
|
Commit Message
Li Nan
May 26, 2023, 7:45 a.m. UTC
From: Li Nan <linan122@huawei.com> need_replace will be set to 1 if no-Faulty mreplace exists, and mreplace will be deref later. However, the latter check of mreplace might set mreplace to NULL, null-ptr-deref occurs if need_replace is 1 at this time. Fix it by merging two checks into one. And replace 'need_replace' with 'mreplace' because their values are always the same. Fixes: ee37d7314a32 ("md/raid10: Fix raid10 replace hang when new added disk faulty") Signed-off-by: Li Nan <linan122@huawei.com> --- drivers/md/raid10.c | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-)
Comments
On Fri, May 26, 2023 at 12:47 AM <linan666@huaweicloud.com> wrote: > > From: Li Nan <linan122@huawei.com> > > need_replace will be set to 1 if no-Faulty mreplace exists, and mreplace > will be deref later. However, the latter check of mreplace might set > mreplace to NULL, null-ptr-deref occurs if need_replace is 1 at this time. > > Fix it by merging two checks into one. And replace 'need_replace' with > 'mreplace' because their values are always the same. > > Fixes: ee37d7314a32 ("md/raid10: Fix raid10 replace hang when new added disk faulty") > Signed-off-by: Li Nan <linan122@huawei.com> > --- > drivers/md/raid10.c | 13 +++++-------- > 1 file changed, 5 insertions(+), 8 deletions(-) > > diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c > index 4fcfcb350d2b..e21502c03b45 100644 > --- a/drivers/md/raid10.c > +++ b/drivers/md/raid10.c > @@ -3438,7 +3438,6 @@ static sector_t raid10_sync_request(struct mddev *mddev, sector_t sector_nr, > int must_sync; > int any_working; > int need_recover = 0; > - int need_replace = 0; > struct raid10_info *mirror = &conf->mirrors[i]; > struct md_rdev *mrdev, *mreplace; > > @@ -3451,10 +3450,10 @@ static sector_t raid10_sync_request(struct mddev *mddev, sector_t sector_nr, > !test_bit(In_sync, &mrdev->flags)) > need_recover = 1; > if (mreplace != NULL && > - !test_bit(Faulty, &mreplace->flags)) > - need_replace = 1; > + test_bit(Faulty, &mreplace->flags)) > + mreplace = NULL; > > - if (!need_recover && !need_replace) { > + if (!need_recover && !mreplace) { > rcu_read_unlock(); > continue; > } > @@ -3470,8 +3469,6 @@ static sector_t raid10_sync_request(struct mddev *mddev, sector_t sector_nr, > rcu_read_unlock(); > continue; > } To make sure I understand the issue correctly: The null-ptr-deref only happens when the Faulty bit was set after the last check and before this check below, right? > - if (mreplace && test_bit(Faulty, &mreplace->flags)) > - mreplace = NULL; > /* Unless we are doing a full sync, or a replacement > * we only need to recover the block if it is set in > * the bitmap Thanks, Song > @@ -3594,11 +3591,11 @@ static sector_t raid10_sync_request(struct mddev *mddev, sector_t sector_nr, > bio = r10_bio->devs[1].repl_bio; > if (bio) > bio->bi_end_io = NULL; > - /* Note: if need_replace, then bio > + /* Note: if replace is not NULL, then bio > * cannot be NULL as r10buf_pool_alloc will > * have allocated it. > */ > - if (!need_replace) > + if (!mreplace) > break; > bio->bi_next = biolist; > biolist = bio; > -- > 2.31.1 >
Hi, 在 2023/05/27 5:38, Song Liu 写道: > On Fri, May 26, 2023 at 12:47 AM <linan666@huaweicloud.com> wrote: } > > To make sure I understand the issue correctly: > > The null-ptr-deref only happens when the Faulty bit was set after the > last check and before this check below, right? Yes, you're right. Thanks, Kuai > >> - if (mreplace && test_bit(Faulty, &mreplace->flags)) >> - mreplace = NULL; >> /* Unless we are doing a full sync, or a replacement >> * we only need to recover the block if it is set in >> * the bitmap > > Thanks, > Song >
Hi, 在 2023/05/26 15:45, linan666@huaweicloud.com 写道: > From: Li Nan <linan122@huawei.com> > > need_replace will be set to 1 if no-Faulty mreplace exists, and mreplace > will be deref later. However, the latter check of mreplace might set > mreplace to NULL, null-ptr-deref occurs if need_replace is 1 at this time. > > Fix it by merging two checks into one. And replace 'need_replace' with > 'mreplace' because their values are always the same. > > Fixes: ee37d7314a32 ("md/raid10: Fix raid10 replace hang when new added disk faulty") > Signed-off-by: Li Nan <linan122@huawei.com> Other than some nits below, this patch looks good to me, feel free too add: Reviewed-by: Yu Kuai <yukuai3@huawei.com> > --- > drivers/md/raid10.c | 13 +++++-------- > 1 file changed, 5 insertions(+), 8 deletions(-) > > diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c > index 4fcfcb350d2b..e21502c03b45 100644 > --- a/drivers/md/raid10.c > +++ b/drivers/md/raid10.c > @@ -3438,7 +3438,6 @@ static sector_t raid10_sync_request(struct mddev *mddev, sector_t sector_nr, > int must_sync; > int any_working; > int need_recover = 0; > - int need_replace = 0; > struct raid10_info *mirror = &conf->mirrors[i]; > struct md_rdev *mrdev, *mreplace; > > @@ -3451,10 +3450,10 @@ static sector_t raid10_sync_request(struct mddev *mddev, sector_t sector_nr, > !test_bit(In_sync, &mrdev->flags)) > need_recover = 1; > if (mreplace != NULL && > - !test_bit(Faulty, &mreplace->flags)) > - need_replace = 1; > + test_bit(Faulty, &mreplace->flags)) This can be keeped in one line. > + mreplace = NULL; > > - if (!need_recover && !need_replace) { > + if (!need_recover && !mreplace) { > rcu_read_unlock(); > continue; > } > @@ -3470,8 +3469,6 @@ static sector_t raid10_sync_request(struct mddev *mddev, sector_t sector_nr, > rcu_read_unlock(); > continue; > } > - if (mreplace && test_bit(Faulty, &mreplace->flags)) > - mreplace = NULL; > /* Unless we are doing a full sync, or a replacement > * we only need to recover the block if it is set in > * the bitmap > @@ -3594,11 +3591,11 @@ static sector_t raid10_sync_request(struct mddev *mddev, sector_t sector_nr, > bio = r10_bio->devs[1].repl_bio; > if (bio) > bio->bi_end_io = NULL; > - /* Note: if need_replace, then bio > + /* Note: if replace is not NULL, then bio > * cannot be NULL as r10buf_pool_alloc will > * have allocated it. > */ > - if (!need_replace) > + if (!mreplace) > break; > bio->bi_next = biolist; > biolist = bio; >
在 2023/5/27 5:38, Song Liu 写道: > On Fri, May 26, 2023 at 12:47 AM <linan666@huaweicloud.com> wrote: >> >> From: Li Nan <linan122@huawei.com> >> >> need_replace will be set to 1 if no-Faulty mreplace exists, and mreplace >> will be deref later. However, the latter check of mreplace might set >> mreplace to NULL, null-ptr-deref occurs if need_replace is 1 at this time. >> >> Fix it by merging two checks into one. And replace 'need_replace' with >> 'mreplace' because their values are always the same. >> >> Fixes: ee37d7314a32 ("md/raid10: Fix raid10 replace hang when new added disk faulty") >> Signed-off-by: Li Nan <linan122@huawei.com> >> --- >> drivers/md/raid10.c | 13 +++++-------- >> 1 file changed, 5 insertions(+), 8 deletions(-) >> >> diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c >> index 4fcfcb350d2b..e21502c03b45 100644 >> --- a/drivers/md/raid10.c >> +++ b/drivers/md/raid10.c >> @@ -3438,7 +3438,6 @@ static sector_t raid10_sync_request(struct mddev *mddev, sector_t sector_nr, >> int must_sync; >> int any_working; >> int need_recover = 0; >> - int need_replace = 0; >> struct raid10_info *mirror = &conf->mirrors[i]; >> struct md_rdev *mrdev, *mreplace; >> >> @@ -3451,10 +3450,10 @@ static sector_t raid10_sync_request(struct mddev *mddev, sector_t sector_nr, >> !test_bit(In_sync, &mrdev->flags)) >> need_recover = 1; >> if (mreplace != NULL && >> - !test_bit(Faulty, &mreplace->flags)) >> - need_replace = 1; >> + test_bit(Faulty, &mreplace->flags)) >> + mreplace = NULL; >> >> - if (!need_recover && !need_replace) { >> + if (!need_recover && !mreplace) { >> rcu_read_unlock(); >> continue; >> } >> @@ -3470,8 +3469,6 @@ static sector_t raid10_sync_request(struct mddev *mddev, sector_t sector_nr, >> rcu_read_unlock(); >> continue; >> } > > To make sure I understand the issue correctly: > > The null-ptr-deref only happens when the Faulty bit was set after the > last check and before this check below, right? > Yes. I will improve log in next version.
在 2023/5/27 9:21, Yu Kuai 写道: > Hi, > > 在 2023/05/26 15:45, linan666@huaweicloud.com 写道: >> From: Li Nan <linan122@huawei.com> >> >> need_replace will be set to 1 if no-Faulty mreplace exists, and mreplace >> will be deref later. However, the latter check of mreplace might set >> mreplace to NULL, null-ptr-deref occurs if need_replace is 1 at this >> time. >> >> Fix it by merging two checks into one. And replace 'need_replace' with >> 'mreplace' because their values are always the same. >> >> Fixes: ee37d7314a32 ("md/raid10: Fix raid10 replace hang when new >> added disk faulty") >> Signed-off-by: Li Nan <linan122@huawei.com> > > Other than some nits below, this patch looks good to me, feel free too > add: > > Reviewed-by: Yu Kuai <yukuai3@huawei.com> >> --- >> drivers/md/raid10.c | 13 +++++-------- >> 1 file changed, 5 insertions(+), 8 deletions(-) >> >> diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c >> index 4fcfcb350d2b..e21502c03b45 100644 >> --- a/drivers/md/raid10.c >> +++ b/drivers/md/raid10.c >> @@ -3438,7 +3438,6 @@ static sector_t raid10_sync_request(struct mddev >> *mddev, sector_t sector_nr, >> int must_sync; >> int any_working; >> int need_recover = 0; >> - int need_replace = 0; >> struct raid10_info *mirror = &conf->mirrors[i]; >> struct md_rdev *mrdev, *mreplace; >> @@ -3451,10 +3450,10 @@ static sector_t raid10_sync_request(struct >> mddev *mddev, sector_t sector_nr, >> !test_bit(In_sync, &mrdev->flags)) >> need_recover = 1; >> if (mreplace != NULL && >> - !test_bit(Faulty, &mreplace->flags)) >> - need_replace = 1; >> + test_bit(Faulty, &mreplace->flags)) > This can be keeped in one line. > OK, I will change it. Thanks for your review.
diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c index 4fcfcb350d2b..e21502c03b45 100644 --- a/drivers/md/raid10.c +++ b/drivers/md/raid10.c @@ -3438,7 +3438,6 @@ static sector_t raid10_sync_request(struct mddev *mddev, sector_t sector_nr, int must_sync; int any_working; int need_recover = 0; - int need_replace = 0; struct raid10_info *mirror = &conf->mirrors[i]; struct md_rdev *mrdev, *mreplace; @@ -3451,10 +3450,10 @@ static sector_t raid10_sync_request(struct mddev *mddev, sector_t sector_nr, !test_bit(In_sync, &mrdev->flags)) need_recover = 1; if (mreplace != NULL && - !test_bit(Faulty, &mreplace->flags)) - need_replace = 1; + test_bit(Faulty, &mreplace->flags)) + mreplace = NULL; - if (!need_recover && !need_replace) { + if (!need_recover && !mreplace) { rcu_read_unlock(); continue; } @@ -3470,8 +3469,6 @@ static sector_t raid10_sync_request(struct mddev *mddev, sector_t sector_nr, rcu_read_unlock(); continue; } - if (mreplace && test_bit(Faulty, &mreplace->flags)) - mreplace = NULL; /* Unless we are doing a full sync, or a replacement * we only need to recover the block if it is set in * the bitmap @@ -3594,11 +3591,11 @@ static sector_t raid10_sync_request(struct mddev *mddev, sector_t sector_nr, bio = r10_bio->devs[1].repl_bio; if (bio) bio->bi_end_io = NULL; - /* Note: if need_replace, then bio + /* Note: if replace is not NULL, then bio * cannot be NULL as r10buf_pool_alloc will * have allocated it. */ - if (!need_replace) + if (!mreplace) break; bio->bi_next = biolist; biolist = bio;