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 185973AE183 for ; Mon, 1 Jun 2026 14:47:21 +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=1780325241; cv=none; b=mSKinFBrbxwZi+P+KOBNiypxkGiYIlAC+2NSL6Xgvc11er5UVr4nsp6knSkvbZMm3habWua0IEFhxxRr2tnZlGGTdINasmjzDMSP576rTeMfMq4peXLzf1NgzTjcnwHS8UwXvFF4Z9f3JVvAEWiFvyENvILQbEuyevblp6fbTw4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780325241; c=relaxed/simple; bh=VOr2wm1ZD1uIsZ8sRYRWGWas2k3myaGPqEIH0yZmNd4=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=bXq9JScoPpS+Zq+vT/tkdOep0S6MzQ1ulSfrEKp5vN8tlizthjhkw12XPKSHw+dna86rQIj2Er7DuR6xDG1QSnjoXGiuexHVuk/cz4gWF6FScWUKuMQF030GsjRtUnUSe40rvck6R67hl5Sl7NrJdY/9AR519rnP3kdQEiW1wKU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=flnoetB8; 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="flnoetB8" Received: by smtp.kernel.org (Postfix) with ESMTPSA id C89B11F00893; Mon, 1 Jun 2026 14:47:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1780325241; bh=OUqTRMjshhyo/UdDLqmHbbioFveZxzh6v+Ohwy8R5Gw=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=flnoetB8RoDxMQJJqV2VUPVK+o9gang03rVPQQGmQKJ8dGDMRYeVDwjkDW0E77tY0 FXExgM4utiv8YZ4TluQUpAXnyG4KTJGV1zIflmc8J9Y9vTFZmKg/iMkdCpU6BeZIFt CyI6T+8gpL5CW6vrXEFqcs9Qx1b7LBY363VcHXuFJCRZy0XCSzn2eFRQ2UYkHmnl5C cptgdp2rKK2VOnfUe+iQ2N6VU9lq3wRD8YRKJwn7male4ELP2CB6DtpFAseOTLoY1I lYesWDVafJn7yiBVLGOQvpVheQtu3GfAY9v8WOutndw1tt/OGtKahC1Y+RqX9vN0jI a1peYxjyCD11g== Date: Mon, 1 Jun 2026 04:47:19 -1000 From: Tejun Heo To: Tetsuo Handa Cc: Marco Crivellari , linux-kernel@vger.kernel.org, Lai Jiangshan , Frederic Weisbecker , Sebastian Andrzej Siewior , Michal Hocko , Breno Leitao Subject: Re: [PATCH v4 0/2] workqueue: Add warnings and check WQ flags usage Message-ID: References: <20260529130640.220328-1-marco.crivellari@suse.com> <5b2dea50-2850-4876-b6e8-ba94b9a85034@I-love.SAKURA.ne.jp> 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: <5b2dea50-2850-4876-b6e8-ba94b9a85034@I-love.SAKURA.ne.jp> On Mon, Jun 01, 2026 at 07:12:28AM +0900, Tetsuo Handa wrote: > I've spent more than one year for updating all in-tree users who are > flushing kernel global workqueues. Please see a message from Linus at > https://lkml.kernel.org/r/CAHk-=whWreGjEQ6yasspzBrNnS7EQiL+SknToWt=SzUh4XomyQ@mail.gmail.com . > > Please never try to emit WARNING: or BUG: message just for letting developers > update their code. If you can't use panic() instead of WARN*() or BUG*(), you > should not use WARN*() or BUG*(). The patch author who changes the behavior of > in-tree code is responsible for updating all in-tree code. I don't think a statement this blanket makes sense. I scanned the existing linux-next tree and there were a handful that were missed (I didn't find out whether they are new ones in linux-next or ones that were misseds from mainline tho). Let's just apply the nvme-tcp patch and move on. Thanks. -- tejun