From: Harvey Tite <HarvT@pm.me>
To: dapeng1.mi@linux.intel.com
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
octavia.togami@gmail.com, peterz@infradead.org,
regressions@lists.linux.dev, stable@vger.kernel.org
Subject: Re: [REGRESSION] bisected: perf: hang when using async-profiler caused by perf: Fix the POLL_HUP delivery breakage
Date: Mon, 03 Nov 2025 01:24:44 +0000 [thread overview]
Message-ID: <9f94b9b5-0a8a-4f37-8355-0b5461d6ad30@pm.me> (raw)
Hello hope everyone is well, just following up on this bug report, this
appears to have been patched here
https://lore.kernel.org/lkml/20251015051828.12809-1-dapeng1.mi@linux.intel.com/
thanks to Dapeng Mi; however, the patch email does not appear to have
CCed the regressions or stable list.
On 2025/10/15 Peter Zijlstra wrote:
> So yeah, I suppose this works. Let me go queue this up.
In regard to the patch, hence I assume the patch is approved for
implementation in future versions.
This is a critical bug causing widespread irrecoverable system freezes
reported by many users with many differing setups, including myself.
Notably it is being triggered by a minecraft mod called spark with at
least 150 million aggregate downloads
(https://www.curseforge.com/minecraft/mc-mods/spark
https://github.com/lucko/spark/issues/530).
If at all possible I would love to request that this please be
implemented/backported to kernels 6.17 and 6.18.
Thank you.
next reply other threads:[~2025-11-03 1:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 1:24 Harvey Tite [this message]
2025-11-03 9:24 ` [REGRESSION] bisected: perf: hang when using async-profiler caused by perf: Fix the POLL_HUP delivery breakage Peter Zijlstra
-- strict thread matches above, loose matches on Subject: below --
2025-10-11 8:31 Octavia Togami
2025-10-13 2:34 ` Mi, Dapeng
2025-10-13 6:55 ` Octavia Togami
2025-10-14 6:40 ` Mi, Dapeng
2025-10-14 20:13 ` Octavia Togami
2025-10-15 0:27 ` Mi, Dapeng
2025-10-13 8:05 ` Peter Zijlstra
2025-10-13 8:38 ` Mi, Dapeng
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=9f94b9b5-0a8a-4f37-8355-0b5461d6ad30@pm.me \
--to=harvt@pm.me \
--cc=dapeng1.mi@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=octavia.togami@gmail.com \
--cc=peterz@infradead.org \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.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