From: Finn Thain <fthain@linux-m68k.org>
To: Lance Yang <lance.yang@linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Eero Tamminen <oak@helsinkinet.fi>,
Kent Overstreet <kent.overstreet@linux.dev>,
amaindex@outlook.com, anna.schumaker@oracle.com,
boqun.feng@gmail.com, ioworker0@gmail.com,
joel.granados@kernel.org, jstultz@google.com,
leonylgao@tencent.com, linux-kernel@vger.kernel.org,
linux-m68k@lists.linux-m68k.org, longman@redhat.com,
mhiramat@kernel.org, mingo@redhat.com, mingzhe.yang@ly.com,
peterz@infradead.org, rostedt@goodmis.org,
senozhatsky@chromium.org, tfiga@chromium.org, will@kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2 1/1] hung_task: fix warnings caused by unaligned lock pointers
Date: Wed, 8 Oct 2025 17:14:51 +1100 (AEDT) [thread overview]
Message-ID: <693a62e0-a2b5-113b-d5d9-ffb7f2521d6c@linux-m68k.org> (raw)
In-Reply-To: <56784853-b653-4587-b850-b03359306366@linux.dev>
On Wed, 8 Oct 2025, Lance Yang wrote:
> On 2025/10/8 08:40, Finn Thain wrote:
> >
> > On Tue, 7 Oct 2025, Andrew Morton wrote:
> >
> >> Getting back to the $Subject at hand, are people OK with proceeding
> >> with Lance's original fix?
> >>
> >
> > Lance's patch is probably more appropriate for -stable than the patch I
> > proposed -- assuming a fix is needed for -stable.
>
> Thanks!
>
> Apart from that, I believe this fix is still needed for the hung task
> detector itself, to prevent unnecessary warnings in a few unexpected
> cases.
>
Can you be more specific about those cases? A fix for a theoretical bug
doesn't qualify for -stable branches. But if it's a fix for a real bug, I
have misunderstood Andrew's question...
> >
> > Besides those two alternatives, there is also a workaround:
> > $ ./scripts/config -d DETECT_HUNG_TASK_BLOCKER
> > which may be acceptable to the interested parties (i.e. m68k users).
> >
> > I don't have a preference. I'll leave it up to the bug reporters (Eero
> > and Geert).
>
next prev parent reply other threads:[~2025-10-08 6:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 14:52 [PATCH v2 1/1] hung_task: fix warnings caused by unaligned lock pointers Lance Yang
2025-09-09 16:46 ` Kent Overstreet
2025-09-09 16:55 ` John Paul Adrian Glaubitz
2025-09-09 19:02 ` Kent Overstreet
2025-09-10 0:45 ` Finn Thain
2025-09-10 7:34 ` Geert Uytterhoeven
2025-09-10 7:37 ` John Paul Adrian Glaubitz
2025-09-10 0:07 ` Finn Thain
2025-09-10 0:51 ` Kent Overstreet
2025-09-10 1:35 ` Finn Thain
2025-09-10 1:48 ` Kent Overstreet
2025-09-10 6:40 ` Finn Thain
2025-09-10 6:52 ` Andreas Schwab
2025-09-10 7:39 ` John Paul Adrian Glaubitz
2025-09-10 7:45 ` Geert Uytterhoeven
2025-09-10 8:02 ` Finn Thain
2025-09-10 11:26 ` Andreas Schwab
2025-09-10 7:36 ` Geert Uytterhoeven
2025-09-10 11:57 ` Kent Overstreet
2025-10-07 20:56 ` Andrew Morton
2025-10-08 0:40 ` Finn Thain
2025-10-08 3:03 ` Lance Yang
2025-10-08 6:14 ` Finn Thain [this message]
2025-10-08 7:09 ` Lance Yang
2025-10-08 7:23 ` Lance Yang
2025-10-08 10:12 ` Finn Thain
2025-10-08 13:48 ` Lance Yang
2025-10-08 21:55 ` Finn Thain
2025-10-09 2:01 ` Lance Yang
2025-10-09 4:04 ` Andrew Morton
2025-10-09 7:11 ` Geert Uytterhoeven
2025-10-14 10:11 ` David Laight
2025-10-08 12:56 ` Eero Tamminen
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=693a62e0-a2b5-113b-d5d9-ffb7f2521d6c@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=amaindex@outlook.com \
--cc=anna.schumaker@oracle.com \
--cc=boqun.feng@gmail.com \
--cc=geert@linux-m68k.org \
--cc=ioworker0@gmail.com \
--cc=joel.granados@kernel.org \
--cc=jstultz@google.com \
--cc=kent.overstreet@linux.dev \
--cc=lance.yang@linux.dev \
--cc=leonylgao@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=longman@redhat.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=mingzhe.yang@ly.com \
--cc=oak@helsinkinet.fi \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=stable@vger.kernel.org \
--cc=tfiga@chromium.org \
--cc=will@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).