From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from verein.lst.de (verein.lst.de [213.95.11.211])
	(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 C81AE3793A8
	for <linux-kernel@vger.kernel.org>; Thu, 30 Jul 2026 11:41:27 +0000 (UTC)
Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=213.95.11.211
ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116;
	t=1785411689; cv=none; b=d4MchhmOffSO8WKkARTQkwKPkp/FRPzXZDuF5J4Q/k85pFlkYu2VP8d92g5ve2VQ8N2hC8TiYNDgGVTV/nGwvwkCUVx4qScxRpzADYJdGQlkWElNAzjS/BbiN12+DpN9L0MN1Qk5XaW0BwLJPZDf1hylFktCjRqcBaXPQNnTzlw=
ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org;
	s=arc-20240116; t=1785411689; c=relaxed/simple;
	bh=3FSqsgtDej5AqEI4Dq8WCNGAi8/4/CDK3ba3T3U6ny4=;
	h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:
	 Content-Type:Content-Disposition:In-Reply-To; b=XSZoTgGV1HOEGU06rGWDKbF/7Pu2RBTl5abFPS4+rM1FvMS0urSWeTsJNzYldNI5clQqtY097wmA3Ls2HRopRDUcJ3UVQvngm1n82RsaCwd4ks3/05ihYoN4D01FvqGCAXo5+23frJVMVPY8+goD2YPgrX8iFLYtS4yIaWp9yHw=
ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lst.de; spf=pass smtp.mailfrom=lst.de; arc=none smtp.client-ip=213.95.11.211
Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lst.de
Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lst.de
Received: by verein.lst.de (Postfix, from userid 2407)
	id 894DF68C7B; Thu, 30 Jul 2026 13:41:23 +0200 (CEST)
Date: Thu, 30 Jul 2026 13:41:23 +0200
From: Christoph Hellwig <hch@lst.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
	Hari Mishal <harimishal1@gmail.com>, Jens Axboe <axboe@kernel.dk>,
	Sagi Grimberg <sagi@grimberg.me>, Hannes Reinecke <hare@suse.de>,
	Kanchan Joshi <joshi.k@samsung.com>,
	Nitesh Shetty <nj.shetty@samsung.com>,
	linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] nvme: drop WARN_ON_ONCE on write_stream bounds
 check
Message-ID: <20260730114123.GB25956@lst.de>
References: <20260725135111.14041-1-harimishal1@gmail.com> <20260725135111.14041-3-harimishal1@gmail.com> <amdqKEI44SKwq-K2@kbusch-mbp> <2026072748-unpopular-onlooker-4a2b@gregkh> <amfg_OFiyDadWb3v@kbusch-mbp> <2026072849-uproar-aqua-07c3@gregkh> <20260728051838.GA20593@lst.de> <2026072834-buffoon-entwine-ed16@gregkh>
Precedence: bulk
X-Mailing-List: linux-kernel@vger.kernel.org
List-Id: <linux-kernel.vger.kernel.org>
List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org>
List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2026072834-buffoon-entwine-ed16@gregkh>
User-Agent: Mutt/1.5.17 (2007-11-01)

On Tue, Jul 28, 2026 at 08:58:00AM +0200, Greg Kroah-Hartman wrote:
[... monster quote mostly dropped, please stick mail netiquette]
> > but a debug setup you get what you pay for, and I'm really tired of
> > all these totally stupid attempts to make WARN_ON the new BUG_ON.
> > It is not, and that's for a reason.
> 
> I'm tired of it too, but again, if this can be hit by something a user
> does, it ends up being a DoS on the machine :(

So let's kill parnic_on_warn?  Or tain the kernel when it is set so
that anyone enaling it knows they have to keep the pieces when it
breaks?