From: Mike Snitzer <snitzer@kernel.org>
To: yangerkun <yangerkun@huaweicloud.com>
Cc: yangerkun@huawei.com, dm-devel@redhat.com,
Bart Van Assche <bvanassche@acm.org>,
agk@redhat.com
Subject: Re: [dm-devel] dm-crypt: fix softlockup in dmcrypt_write
Date: Mon, 27 Feb 2023 13:06:27 -0500 [thread overview]
Message-ID: <Y/zxI4wK8trtuJgV@redhat.com> (raw)
In-Reply-To: <Y/zwVCNDrdAbzC7a@redhat.com>
On Mon, Feb 27 2023 at 1:03P -0500,
Mike Snitzer <snitzer@kernel.org> wrote:
> On Mon, Feb 27 2023 at 12:55P -0500,
> Mike Snitzer <snitzer@kernel.org> wrote:
>
> > On Sun, Feb 26 2023 at 8:31P -0500,
> > yangerkun <yangerkun@huaweicloud.com> wrote:
> >
> > >
> > >
> > > 在 2023/2/26 10:01, Bart Van Assche 写道:
> > > > On 2/22/23 19:19, yangerkun wrote:
> > > > > @@ -1924,6 +1926,10 @@ static int dmcrypt_write(void *data)
> > > > > BUG_ON(rb_parent(write_tree.rb_node));
> > > > > + if (time_is_before_jiffies(start_time + HZ)) {
> > > > > + schedule();
> > > > > + start_time = jiffies;
> > > > > + }
> > > >
> > > > Why schedule() instead of cond_resched()?
> > >
> > > cond_resched may not really schedule, which may trigger the problem too, but
> > > it seems after 1 second, it may never happend?
> >
> > I had the same question as Bart when reviewing your homegrown
> > conditional schedule(). Hopefully you can reproduce this issue? If
> > so, please see if simply using cond_resched() fixes the issue.
>
> This seems like a more appropriate patch:
>
> diff --git a/drivers/md/dm-crypt.c b/drivers/md/dm-crypt.c
> index 87c5706131f2..faba1be572f9 100644
> --- a/drivers/md/dm-crypt.c
> +++ b/drivers/md/dm-crypt.c
> @@ -1937,6 +1937,7 @@ static int dmcrypt_write(void *data)
> io = crypt_io_from_node(rb_first(&write_tree));
> rb_erase(&io->rb_node, &write_tree);
> kcryptd_io_write(io);
> + cond_resched();
> } while (!RB_EMPTY_ROOT(&write_tree));
> blk_finish_plug(&plug);
> }
or:
diff --git a/drivers/md/dm-crypt.c b/drivers/md/dm-crypt.c
index 87c5706131f2..3ba2fd3e4358 100644
--- a/drivers/md/dm-crypt.c
+++ b/drivers/md/dm-crypt.c
@@ -1934,6 +1934,7 @@ static int dmcrypt_write(void *data)
*/
blk_start_plug(&plug);
do {
+ cond_resched();
io = crypt_io_from_node(rb_first(&write_tree));
rb_erase(&io->rb_node, &write_tree);
kcryptd_io_write(io);
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2023-02-27 18:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 3:19 [dm-devel] [PATCH] dm-crypt: fix softlockup in dmcrypt_write yangerkun
2023-02-26 2:01 ` Bart Van Assche
2023-02-27 1:31 ` yangerkun
2023-02-27 17:55 ` [dm-devel] " Mike Snitzer
2023-02-27 18:03 ` Mike Snitzer
2023-02-27 18:06 ` Mike Snitzer [this message]
2023-02-28 1:40 ` yangerkun
2023-03-06 18:02 ` Mikulas Patocka
2023-03-06 18:16 ` Bart Van Assche
2023-03-06 19:03 ` Mikulas Patocka
2023-02-28 1:25 ` yangerkun
2023-02-28 7:22 ` yangerkun
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=Y/zxI4wK8trtuJgV@redhat.com \
--to=snitzer@kernel.org \
--cc=agk@redhat.com \
--cc=bvanassche@acm.org \
--cc=dm-devel@redhat.com \
--cc=yangerkun@huawei.com \
--cc=yangerkun@huaweicloud.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;
as well as URLs for NNTP newsgroup(s).