From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) (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 B1B2738D6A9 for ; Thu, 20 Aug 2026 06:16:51 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=193.142.43.55 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787206613; cv=none; b=KhfvYShEKcyLhKvYZztMcBp8Bt18VdydpFj88+FFU4EjNjwZPeNzlrs78g8yCrfhHlpTaXQG+qZoNG80Bol8cCQJE9SyY6zR5kAUWG3pCDIZODHfJSW6Q4Zwgay9aLHkgo3XXHlIWJuoMJDICgpfInWoBtNJwEWb8lZtkZnhc54= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787206613; c=relaxed/simple; bh=svDi0uCRE64okVDztLa++jDkjBuhgs/aHn9Npvw0JyY=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=GMqQsa7YXSb99NAGrF5YCCbQsFjGPvTd113ZYAqJogw1b0HK7dAF6mAl8BYtNi4lWQEC9JpZbkFE5QhPsSU7VGJTCyuf5cjvtKQqRGnWBz0YRsfnvXvihEJttGMXvlsuX9GYZ7zDp3nB6YhfF2s4RYg++Hjq7C2xxjCiG8K6vMY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de; spf=pass smtp.mailfrom=linutronix.de; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=hpTXOWak; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b=NoXQoDK4; arc=none smtp.client-ip=193.142.43.55 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linutronix.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linutronix.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="hpTXOWak"; dkim=permerror (0-bit key) header.d=linutronix.de header.i=@linutronix.de header.b="NoXQoDK4" Date: Thu, 20 Aug 2026 08:16:48 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1787206609; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=VxGMD31pkk5tfQXQecvbqMvmetKrKGtr2+1zv4FTyBY=; b=hpTXOWakkSx9cEBak9c9yXzHT2oe5b/ZuXly3mNej3KECub47SjhjnUkfKtlsBRlOi026m jKsZ0OFCOdBG1e1JfB8Mkxer/gt0/AwF+Sp8sA/WJYVUQB0dzpH3wjf/5bzp/4hwcrrIeE SIjaTag9Oji8G8DKn7GwS3ggmBz6oZXCB9NWUkSp3KUfsepN2EAAK/Yq4SJrOXlN6GStQ3 88dcTATvU9fVEYerVFJInigflTNPmLMO/QV8P89JaDTxts2JzOHSUf8+HOeNPovYpzC6kJ x42ZPedE3WDd0Ptx7YNhvzqaenE8foto8oBPvPP8LsHShsFPgbb7XMf1PfUk8A== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1787206609; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=VxGMD31pkk5tfQXQecvbqMvmetKrKGtr2+1zv4FTyBY=; b=NoXQoDK4ig7IBm186vdFs3o8SUhZz0IK3GV2sH2sxm3eDK5WFu/yQlC8lkzjyYACgi0vMt r2JX4uu60GFnQMBw== From: Sebastian Andrzej Siewior To: Tejun Heo Cc: Lai Jiangshan , Thomas Gleixner , Peter Zijlstra , linux-kernel@vger.kernel.org Subject: Re: [PATCH] workqueue: Use raise_softirq() in bh_pool_kick_.*() Message-ID: <20260820061648.XK4lUX7t@linutronix.de> References: <20260819141909.e2ZfmB3y@linutronix.de> <795f747c1cd5e69c73843408c139bfef@kernel.org> 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=utf-8 Content-Disposition: inline In-Reply-To: <795f747c1cd5e69c73843408c139bfef@kernel.org> On 2026-08-19 10:41:44 [-1000], Tejun Heo wrote: > Hello, Sebastian. Hi, > On Wed, Aug 19, 2026 at 04:19:09PM +0200, Sebastian Andrzej Siewior wrote: > > Use raise_softirq() in bh_pool_kick_.*() to avoid a warning in > > PREEMPT_RT. > > The same fix was applied last month: > > df42c49ec865 ("workqueue: Use raise_softirq() to trigger softirq in > irq_work handler") > > but I mistakenly applied it to the already closed for-7.1-fixes branch > and it never reached mainline. It's now cherry-picked to > wq/for-7.3-fixes and will go to mainline and then -stable this cycle. > Thanks for the fix and sorry about the confusion. no worries. Sebastian