From: Yu Kuai <yukuai1@huaweicloud.com>
To: Xiao Ni <xni@redhat.com>, Yu Kuai <yukuai1@huaweicloud.com>
Cc: song@kernel.org, linux-raid@vger.kernel.org,
linux-kernel@vger.kernel.org, yi.zhang@huawei.com,
yangerkun@huawei.com, "yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH md-6.13 5/5] md/md-bitmap: move bitmap_{start, end}write to md upper layer
Date: Fri, 22 Nov 2024 16:32:25 +0800 [thread overview]
Message-ID: <e3319ea0-f9aa-6048-c620-4e72f2b10b31@huaweicloud.com> (raw)
In-Reply-To: <CALTww28ZRFo6BwqzriVpoOuqbfygKrU0HuOhhUxLe9cBBDY-ZQ@mail.gmail.com>
Hi,
在 2024/11/22 11:14, Xiao Ni 写道:
>> Ok, one place that I found is that raid5 can do extra end write while
>> stripe->dev[].towrite is NULL, the null checking is missing. I'll
>> mention that in the next version.
> Does this can cause the deadlock?
Not deadlock, the bit counter will underflow and reach COUNTER_MAX, and
bitmap_startwrite() can wait forever for the counter.
Thanks,
Kuai
next prev parent reply other threads:[~2024-11-22 8:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 11:41 [PATCH md-6.13 0/5] md/md-bitmap: move bitmap_{start,end}write " Yu Kuai
2024-11-18 11:41 ` [PATCH md-6.13 1/5] md/md-bitmap: factor behind write counters out from bitmap_{start/end}write() Yu Kuai
2024-11-22 2:16 ` Xiao Ni
2024-11-18 11:41 ` [PATCH md-6.13 2/5] md/md-bitmap: remove the last parameter for bimtap_ops->endwrite() Yu Kuai
2024-11-18 11:41 ` [PATCH md-6.13 3/5] md: add a new callback pers->bitmap_sector() Yu Kuai
2024-11-22 2:17 ` Xiao Ni
2024-11-18 11:41 ` [PATCH md-6.13 4/5] md/raid5: implement pers->bitmap_sector() Yu Kuai
2024-11-18 11:41 ` [PATCH md-6.13 5/5] md/md-bitmap: move bitmap_{start, end}write to md upper layer Yu Kuai
2024-11-19 9:49 ` [PATCH md-6.13 4/5] md/raid5: implement pers->bitmap_sector() Jack Wang
2024-11-19 10:58 ` Yu Kuai
2024-11-19 15:29 ` Jack Wang
2024-11-21 8:10 ` Jinpu Wang
2024-11-21 8:33 ` Yu Kuai
2024-11-21 8:40 ` Jinpu Wang
2024-11-21 8:44 ` Yu Kuai
2024-11-21 8:46 ` Jinpu Wang
2024-11-21 9:30 ` Christian Theune
2024-11-21 11:01 ` Yu Kuai
2024-11-21 12:05 ` Christian Theune
2024-11-21 12:21 ` Christian Theune
2024-11-21 12:37 ` Yu Kuai
2024-11-21 16:14 ` Christian Theune
2024-11-22 2:06 ` [PATCH md-6.13 5/5] md/md-bitmap: move bitmap_{start, end}write to md upper layer Xiao Ni
2024-11-22 2:45 ` Yu Kuai
2024-11-22 3:14 ` Xiao Ni
2024-11-22 8:32 ` Yu Kuai [this message]
2024-11-23 3:55 ` Xiao Ni
2024-11-25 1:15 ` Yu Kuai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e3319ea0-f9aa-6048-c620-4e72f2b10b31@huaweicloud.com \
--to=yukuai1@huaweicloud.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=song@kernel.org \
--cc=xni@redhat.com \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®