From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-186.mta1.migadu.com (out-186.mta1.migadu.com [95.215.58.186]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6F29B21423C for ; Wed, 8 Oct 2025 03:03:40 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.186 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1759892622; cv=none; b=CAvuGcU/m5+sfbkuCbF4mDcQOQAKV/P4eZYhyVIcjAbMfCeML6nTRRRFmx0vvmpJxWgAPe6TJOWRgbrSsa7lm+yDJBjsAIJ9MJl9ZzV5B+PrZsH3dQ00bCaW9fLaLVSNsngZh8K0E+VTvAydghwt6f3Lz27FwoyOlonf6kbrJ9o= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1759892622; c=relaxed/simple; bh=5yStW0L1wEARM1VcACJHqDCy7X/TSWEwGB67a2Fqnmg=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=YPx1XKIQX3ui3ZW32ot900fUdqMU+yct+3uHKyyjsqKG8WqgBC5kNNw49FTrvDooQVMXpnPjuDl/EBv5IvAnZ4Uro9JFcNk0SjQ3UBE2SUjkoL9r4XD1zONG7c6XKZ6cFBzI/rUxqeOodo4EH80Z9CkKVTflokc6S0uWQ9Xf5Ys= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=T/3jXx84; arc=none smtp.client-ip=95.215.58.186 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="T/3jXx84" Message-ID: <56784853-b653-4587-b850-b03359306366@linux.dev> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1759892608; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=vSRrtrvWgwS90ySr5nF6OQKQum7o9S6zWNvqm6k9XvM=; b=T/3jXx84Rfw++V6z2MKJJv5c/rPYfsL5Ui23RZkEQx9CDR0WnlRFujpQtx7DTK8morvqzQ fGf+hxuXI0wGprlzykRqYh0W/J+sSVWQbdk1l39Qun/FBJqNpmP2TIBlXlxC4mcFM9II/u MInrvhq4Nld0p1caXSOIDmVSFa3ddig= Date: Wed, 8 Oct 2025 11:03:18 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Subject: Re: [PATCH v2 1/1] hung_task: fix warnings caused by unaligned lock pointers Content-Language: en-US To: Finn Thain , Andrew Morton , Geert Uytterhoeven , Eero Tamminen Cc: Kent Overstreet , 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 References: <20250909145243.17119-1-lance.yang@linux.dev> <99410857-0e72-23e4-c60f-dea96427b85a@linux-m68k.org> <20251007135600.6fc4a031c60b1384dffaead1@linux-foundation.org> X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Lance Yang In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_OUT 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. > > 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).