From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 7731941D234 for ; Tue, 28 Jul 2026 09:46:52 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785232013; cv=none; b=mANoqDHch6cJyVmPOVxHzhWBQ4dFPhdJWQ5rxvR0r84fFS01K6g6BiGywrMserfoEpx1wjvMY4pYVsISQvpyQWhbQ/qfXqhr0q0g3F8x+e0tK8YQmEISCgIahPL/Va/xUIg8DaXlmYQy1mHsxmIorl1hhdl5GwV7elzYvkkQy0k= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785232013; c=relaxed/simple; bh=Vc3jXUM2W6zu7lnqk439F+rCtZE+woy4zZvXECQwmSs=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=U8AdDpXDJPbyUPnodosGwoY1BR6jf5KrTjHeTi3G2Hnm5HV6gWCmSGBCVNtcnE0cCL+j1xqwWplXG+P/fRfEKDuVIrVeTrghcsJLfIWNUdg+kowF0ik9cVcriDwnGg3pupYEdTRifztZSjqbYy6nrr89ajL/QkmoQ0dCBTBzH54= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=kzbH5b++; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="kzbH5b++" Received: by smtp.kernel.org (Postfix) with ESMTPSA id AB4F21F00A3A; Tue, 28 Jul 2026 09:46:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1785232012; bh=Vc3jXUM2W6zu7lnqk439F+rCtZE+woy4zZvXECQwmSs=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=kzbH5b++P56dBT9OomdhoXkuWXNgUq9124nIITIO00UmO7d2kz/WodyPnoPMk6ahB JsuTB9mB6kRm6F3TvdesP5Us5SMIfrYqzA9QAbDWhSYcFR3XLI7UvaSITWSMyuMY9l bJoVX/SBjrcu51PRfqHsMsnMCFmxzyyLaY0V7cTcDBoCZFXDRtoC9jpyxoJuOMsH6D UouqB9g/Ua4peA+ENAVqueOWV18YEbIsFtcBNa9lQWAVjAzIgxB9qqU6BfP0Al1BVt w094FNuSvXVRctHB2d2oANXXNcxIOS+iWvTz2ynQ9obJsPoZsjjxgl1+kXZXO6gXgy o4bRA90hu6nFg== Date: Tue, 28 Jul 2026 03:46:50 -0600 From: Keith Busch To: Greg Kroah-Hartman Cc: Christoph Hellwig , Hari Mishal , Jens Axboe , Sagi Grimberg , Hannes Reinecke , Kanchan Joshi , Nitesh Shetty , 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: References: <20260725135111.14041-1-harimishal1@gmail.com> <20260725135111.14041-3-harimishal1@gmail.com> <2026072748-unpopular-onlooker-4a2b@gregkh> <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: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2026072834-buffoon-entwine-ed16@gregkh> On Tue, Jul 28, 2026 at 08:58:00AM +0200, Greg Kroah-Hartman wrote: > 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 :( Why do you think has something to do with what a user does? The filesystem and block layers own the write stream, and the contract is it has to be within the reported limits. If it's not, there's a filesystem bug; nothing to do with the user.