From: Joel Colledge <joel.colledge@linbit.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@kernel.org>,
Christian Loehle <christian.loehle@arm.com>,
dm-devel@lists.linux.dev
Subject: [PATCH 0/1] dm-delay: fix hung task issue
Date: Fri, 26 Apr 2024 09:21:34 +0200 [thread overview]
Message-ID: <20240426072135.291206-1-joel.colledge@linbit.com> (raw)
Hi,
The tests for DRBD encountered an issue with dm-delay when testing with
a 6.8 series kernel. Specifically on Ubuntu 24.04 "Noble". Here is a
minimal reproducer:
virter vm run --name dm-delay-test --id 10 --wait-ssh ubuntu-noble
virter vm ssh dm-delay-test
# truncate -s 100M /file
# loop_dev=$(losetup -f --show /file)
# echo "0 $(blockdev --getsz $loop_dev) delay $loop_dev 0 0" | dmsetup create delay-volume
After a few minutes, the following is printed to the kernel log:
[ 246.919123] INFO: task dm-delay-flush-:1256 blocked for more than 122 seconds.
[ 246.922543] Not tainted 6.8.0-31-generic #31-Ubuntu
[ 246.923753] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 246.924932] task:dm-delay-flush- state:D stack:0 pid:1256 tgid:1256 ppid:2 flags:0x00004000
[ 246.924940] Call Trace:
[ 246.924950] <TASK>
[ 246.924980] __schedule+0x27c/0x6b0
[ 246.925002] ? __pfx_flush_worker_fn+0x10/0x10 [dm_delay]
[ 246.925011] schedule+0x33/0x110
[ 246.925016] schedule_preempt_disabled+0x15/0x30
[ 246.925035] kthread+0xb1/0x120
...
This bug appears to have been introduced in Linux v6.7.
The following patch fixes the issue.
Best regards,
Joel
Joel Colledge (1):
dm-delay: fix hung task introduced by kthread mode
drivers/md/dm-delay.c | 1 +
1 file changed, 1 insertion(+)
--
2.34.1
next reply other threads:[~2024-04-26 7:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 7:21 Joel Colledge [this message]
2024-04-26 7:21 ` [PATCH 1/1] dm-delay: fix hung task introduced by kthread mode Joel Colledge
2024-04-30 14:28 ` Christian Loehle
2024-04-30 14:44 ` Joel Colledge
2024-04-30 15:26 ` Christian Loehle
2024-04-30 16:12 ` Joel Colledge
2024-05-01 8:26 ` Christian Loehle
2024-05-03 22:56 ` Benjamin Marzinski
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=20240426072135.291206-1-joel.colledge@linbit.com \
--to=joel.colledge@linbit.com \
--cc=agk@redhat.com \
--cc=christian.loehle@arm.com \
--cc=dm-devel@lists.linux.dev \
--cc=mpatocka@redhat.com \
--cc=snitzer@kernel.org \
/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).