From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-185.mta0.migadu.com (out-185.mta0.migadu.com [91.218.175.185]) (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 467862110E for ; Sun, 28 Jun 2026 04:48:06 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.185 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782622090; cv=none; b=L9PkFXAdyhYKsFpjNMotmFibfih65geE0quCSyIFLd/oZLLFnWP7XFdDp8TRe9AuGeqpe1tDDVLbH0192LO4Fwxo5fWaiLA9f2P2J7J161YPM91UcjRZ77s3WVJ9O62hmDunoAqTaQ9jf3T9O6A1/NpPRaAzznXYNjnVp0mKh64= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782622090; c=relaxed/simple; bh=S9SyVVK/8x3vn7cBg1BSwzdEfRMg1Xh5bnYKZfa2lPU=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version:Content-Type; b=OyXTQkE3p2IK7qbUZsUXCmWrepZsX4s5jM9KEa88pfycugVDbR++Xj4f8wI1NhZKr3Dxg97+xOUVONby+MIlkWuZKpylWAcLCbBvmrIa6mFnMOV/pSRmer5HQUMqrn0jGOjUaj/4v+2x2kEmDa26eUptgLx9qtOVOoBu/TKTXH4= 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=DfL6T0x6; arc=none smtp.client-ip=91.218.175.185 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="DfL6T0x6" X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1782622085; 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=S9SyVVK/8x3vn7cBg1BSwzdEfRMg1Xh5bnYKZfa2lPU=; b=DfL6T0x6FAQ2qmiQsaerd/rqy2nWAyAUoxjRZRalwHHjCQMojCBfCNo1YE3fKxvzk6fcuS tM1Fl9DMQkrizcLOTGDcpOqGBYIheYa4wQV/96Lf9CwNlC180LlDPW72XY42aAaOmD/49j MikzTZyhPO0eqJRBsRCW55de2Skmj44= From: Lance Yang To: atomlin@atomlin.com Cc: akpm@linux-foundation.org, lance.yang@linux.dev, mhiramat@kernel.org, pmladek@suse.com, linux-kernel@vger.kernel.org, david.laight.linux@gmail.com, neelx@suse.com, sean@ashe.io, chjohnst@gmail.com, steve@abita.co, mproche@gmail.com, nick.lange@gmail.com Subject: Re: [PATCH v4] hung_task: Deduplicate identical hang reports using explicit blocker tracking Date: Sun, 28 Jun 2026 12:47:50 +0800 Message-Id: <20260628044750.32878-1-lance.yang@linux.dev> In-Reply-To: <20260627205733.90983-1-atomlin@atomlin.com> References: <20260627205733.90983-1-atomlin@atomlin.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Migadu-Flow: FLOW_OUT Sorry, but NACK from me. Aaron, please slow down a bit here! I already said in v2 that the discussion didn't feel settled, and asked you to wait before another spin. v3 didn't settle it either ... Replying to comments is *not* the same as settling review ... If any reviewer/maintainer still doesn't agree this should go in, please read the room a bit and stop spining new versions until we agree on the next move. If v3 didn't settle it (i.e. we didn't agree on the next move), please don't just spin v4. Step back first: what real problem does this solve? If this isn't really a real-world problem at all, why keep spinning it? At that point it starts looking less like review and more like patch churn. That usually doesnt land, it just *burns* reviewer time ... I'd rather spend review time on patches where we at least agree the problem is real. I assume you'd prefer that too :) So yeah, still a NACK from me. If new versions keep coming before the discussion settles, I'll keep NACKing them ... Thanks, Lance