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 8BC822F7AC1 for ; Sun, 31 May 2026 16:50:12 +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=1780246213; cv=none; b=Tssb3rV9yQfPqOfjovdAd8TlsdL1lrpNhfE3035+OixQYRdjXKJ7aK7qVId9DXGd87fmCyIwtuzOSZcvg5wBiYyTzJXJ/Cs6/2XF18nEFH6jzY0ud8pVqEj7dCMxC6h7sECCZgZ0igvxL8CAnNdppD4qerGRHILbKJCZMuAHM8o= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780246213; c=relaxed/simple; bh=4rjDUD4lLJ/BHF6Nk0FHuBkWR+9OOQGA6x596p850jc=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=uVri9FzuTmOxpI8GGyd4oFI6mVXHmvrC3puE995T1Vt/eG5Bg6smz9OZZx6YTV7PsbNrA3AlkrEBPR1Xed0whevPD/IhIfeVfcP2wCMiHt0iT2fdVrHtK0bvC03cmF6dts2LvO+wwO5kfiKqO1h31fPArtpFjQfF7KRUdGADDUk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=gI4hLGTN; 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="gI4hLGTN" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4703A1F00893; Sun, 31 May 2026 16:50:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1780246212; bh=4rjDUD4lLJ/BHF6Nk0FHuBkWR+9OOQGA6x596p850jc=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=gI4hLGTN2+juzZYwCk2zcJnEnuvodHa+pdjy5wveRbE01MgvoUaISlBk9lsGUmlvS 0/uAuXucF2E27voitkV9Bvj8lIhr3kVreQfT+o56XmZjwsUbTo2XS8loqIfk3o2ppt wbDF1N1/U7C1KzYUnVM5iUjaEaFsIH2YJwNB0/ceRO3utMjEci8hSeh2XUi3P5GZiX Ea4nBqO3kBwJ8omG/vdMAzd+YU8pY7cFUbhsWo5IsRe+NbnUlSLdAflLA0Oo3vs2CO QHUDHqRHDa0a6uxN3vJbOxst0jSQpuU1zTv5qWTsPklvDnREYzL4xB9htCRurq9BKn drTcok/ClvBow== From: Tejun Heo To: Tetsuo Handa , Marco Crivellari Cc: 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 Date: Sun, 31 May 2026 06:48:54 -1000 Message-ID: In-Reply-To: References: <20260529130640.220328-1-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-Transfer-Encoding: 7bit Sorry for the slow reply - I'm off at the moment so my latency is high. > syzbot is failing to test linux-next kernels due to commit 21c05ca88a54 > ("workqueue: Add warnings and ensure one among WQ_PERCPU or WQ_UNBOUND is > present"). > We can't tolerate linux-next being untested until all callers are fixed. Which caller is breaking which tests? Reverting 21c05ca88a54 is easy, but there's no clean point to do it: the warning is in the wq tree while the caller fixes are scattered across several subsystem trees, and there's no reasonable way to synchronize all of that outside mainline. If it's a specific caller breaking a test, fixing that one is the better path. Thanks.