Bug#1087602: linux: io_uring deadlock (6.1.115 regression)
control: reassign 1087734 src:linux
control: tag 1087734 + confirmed upstream
control: forcemerge 1087734 1087602
control: affects 1087602 chromium
Hi,
On 2024-11-15 22:31, Aurelien Jarno wrote:
> Source: linux
> Version: 6.1.115-1
> Severity: important
> Tags: upstream
> X-Debbugs-Cc: dsa@debian.org
>
> Dear maintainers,
>
> Since the last Bookworm point release, the build daemons often run into
> a io_uring deadlock when building chromium:
>
> [123733.312356] INFO: task iou-sqp-2625111:2625119 blocked for more than 120 seconds.
> [123733.313547] Not tainted 6.1.0-27-amd64 #1 Debian 6.1.115-1
> [123733.314418] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> [123733.315543] task:iou-sqp-2625111 state:D stack:0 pid:2625119 ppid:2625110 flags:0x00004000
> [123733.315548] Call Trace:
> [123733.315550] <TASK>
> [123733.315556] __schedule+0x34d/0x9e0
> [123733.315583] schedule+0x5a/0xd0
> [123733.315586] schedule_preempt_disabled+0x11/0x20
> [123733.315589] __mutex_lock.constprop.0+0x399/0x700
> [123733.315594] io_sq_thread+0x26e/0x4e0
> [123733.315600] ? cpuusage_read+0x10/0x10
> [123733.315604] ? io_sqd_handle_event+0xd0/0xd0
> [123733.315607] ret_from_fork+0x22/0x30
> [123733.315613] </TASK>
>
> We have observed that 3 times on amd64, and once on arm64, so it's not a
> random issue, although so far we only observed this problem when
> building chromium. There was no such issue with kernel 6.1.112-1.
The problem also happens when building nodejs on at least the amd64,
mips64el and s390x build daemons. I am convinced that this is the same
bug than #1087734. The correct upstream fix is (it went into 6.1.116):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8d09a88ef9d3cb7d21d45c39b7b7c31298d23998
I am therefore merging both bugs.
Regards
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://aurel32.net
Reply to: