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 39EA428488D for ; Thu, 28 May 2026 14:23:14 +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=1779978196; cv=none; b=KUh+MCdwQhkQfswoOfr6xyxV4Dt7MOKjr/bCSl0PwQAyiMlYbriKMGXZnwt+QqbpomxQ2ZCnQn85qp9FBwA7PGX2dwP/hGM4KNREe/L0rcURZ7PKF/jNZPG/5TP0EafrnZKoD/rtaFd7FgxSWtJ+bJt+u7XC7shkKCpw9HMfUDA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779978196; c=relaxed/simple; bh=ugkAFg0dwOZdGy2X4/lUKJJQOg7SF3Dklv1iMTzOQQ4=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=tE3CpcCxZXxoRo9YDrl6pTeM5Me9mChUotuDLtr1DoPfgF1Pnu36xCjDLYTqVnmJfyQZd1+r3gOXZfoYRJWqHayLGR8C98jQUsqVMIvBOvWYgFT6hhYmeQtRsjSPwtBVzuaPeJ0HydJajPGD/oWt+ObMW/VCl0lXBSQU4aEQgYQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=BvVZCrbO; 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="BvVZCrbO" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 991BA1F000E9; Thu, 28 May 2026 14:23:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1779978194; bh=iUPAD7vPGcCuMv1zjHzXre5nx73w/wwFzrh7ryEvKos=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=BvVZCrbOjMfH+IDRL8cgs2Lr9/Xq+KruovGEJV9L06IcULYhtF9Hq83g6QdMu5WXt +e4nc+nsEYy2MmoSIdrwqy3m+qxII6K1INLhjqEO7T47Xrk7WJN+wt+Akq0zB/GHFV ZQoMJrkOzZGGHIgyJnD7sP3VoRpovJZzrhAPifuxuLQp71CKJhTLgY29U+7w0u7cZj yVdtiFV+lMWLvAH4mTucQ4NRhq97Ez5OLuDvlKSOk8V4bYRhAE2Fao22521Dtsutxg 7b7n8FrQJO0047KdgcoKOyD6v4Em9lNZFffaXLM/2RW3PRg0awXqjx7rh5gLgVhQYd PBFf0hC9aqILw== Date: Thu, 28 May 2026 04:23:13 -1000 From: Tejun Heo To: Marco Crivellari Cc: linux-kernel@vger.kernel.org, Lai Jiangshan , Frederic Weisbecker , Sebastian Andrzej Siewior , Michal Hocko , Breno Leitao Subject: Re: [RFC PATCH v2 1/2] workqueue: Add warnings and fallback if system_{unbound}_wq is used Message-ID: References: <20260526150041.365392-1-marco.crivellari@suse.com> <20260526150041.365392-2-marco.crivellari@suse.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=us-ascii Content-Disposition: inline In-Reply-To: On Thu, May 28, 2026 at 04:14:03PM +0200, Marco Crivellari wrote: > That's maybe a silly observation on my side. > > If I remove the checks from where I placed them and move them deeper > (__queue_work() for example), I won't know how to print the "caller," > making it harder for people to understand which code is using the > deprecated workqueue. > > Printing the stack with dump_stack() is not doable. > > Do you have suggestions? For workqueues, identifying the work function and workqueue name should be good enough. It's not like these are difficult to find. Thanks. -- tejun