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 EC4F737757C
	for <linux-kernel@vger.kernel.org>; Thu, 16 Jul 2026 19:12:13 +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=1784229134; cv=none; b=ApBUwmmhpOYTOCYOyxQn/l/AqzaGz6Ym0rhTiLSLPNURSK1qhhRTthNPBZo5xq6JItKqz8ujMQYX5qnb1dUz96aQ+35ATsJKDnw921q2TXQgbod+WbuR/TZuYILuqACuONttwdccsk9lVV/1h8AGv9A93AKaV7lS7qVVFkvCCm0=
ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org;
	s=arc-20240116; t=1784229134; c=relaxed/simple;
	bh=AY2NEmA5AWvv4TnoKYv+Gsluj4HiKwah1g/hh/rrX0A=;
	h=Message-ID:From:To:Cc:Subject:In-Reply-To:References:Date; b=EP0/AI/ZZzMElZzrCDR0snKimD9HJwyTcPzbHPGe+VGACLCe2x4U+HLYVNlGcGrQIdFYZcIk/R/MZXJ0RX3J/T84fX5wPMqjYEszbyrIWy/qBwh7qdkuOvy6dAcyHGJezvlrCBYJHQo/WjbYF4enfKVP70sGErZdPUjKKyVS8wg=
ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=R2ezS2wl; 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="R2ezS2wl"
Received: by smtp.kernel.org (Postfix) with ESMTPSA id 68DC21F000E9;
	Thu, 16 Jul 2026 19:12:13 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org;
	s=k20260515; t=1784229133;
	bh=mWdAVeyyy99lTSVSJEpn0EVodWx6d5kOk6z9gqFVUCQ=;
	h=From:To:Cc:Subject:In-Reply-To:References:Date;
	b=R2ezS2wlSW/yS0kd6yHbq6P/zmUXj/dwKwoiW64j8rk+cd3/UOV0m69RSHtGIQ0yT
	 wWU4DgjbPgTZye0zbY4hy7QY80R7B1JxOb0MaRJcZ2BG6XpLHYcbtfCZZ6X5vPmHzm
	 pdD4bpTbaQhoqJ4w9/PRMWtTHO/z9H5QeZYNK5TYzTN4Bj+ipRLYkt9VywxUrLyvT1
	 iVZD2cYRyF3fjHxylQTxivtOHwf/rPooSX/88tsqmBP8SsvKmwKhgsmWbxUgkcMqlC
	 dleFruUFWS6ycQff2Twb8t1TbCodny2NihlzPjYKsQRcC6dHWgHLSod13IHbYCe6Xp
	 WFa+W7ULTpAZQ==
Message-ID: <2a16a87877d77da5328082e50e9a7293@kernel.org>
From: Tejun Heo <tj@kernel.org>
To: Zqiang <qiang.zhang@linux.dev>
Cc: jiangshanlai@gmail.com, linux-kernel@vger.kernel.org,
 Bradley Morgan <include@grrlz.net>
Subject: Re: [PATCH] workqueue: Use raise_softirq() to trigger softirq in
 irq_work handler
In-Reply-To: <20260716095637.23547-1-qiang.zhang@linux.dev>
References: <20260716095637.23547-1-qiang.zhang@linux.dev>
Date: Thu, 16 Jul 2026 09:05:42 -1000
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>

Hello,

Applied to wq/for-7.1-fixes with the description reworded and the
following tags added:

  Fixes: 2f34d7337d98 ("workqueue: Fix queue_work_on() with BH workqueues")
  Cc: stable@vger.kernel.org # v6.9+

The Fixes target differs from the suggested 4cb1ef64609f. There, the
raises ran under pool->lock with IRQs disabled. The irq_work handlers
were added later by 2f34d7337d98 which moved the remote-CPU raise out of
kick_pool(). Also picked up Bradley's Reviewed-by.

Thanks.

-- 
tejun