Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Sender: Tejun Heo <htejun@gmail.com>
Date:   Wed, 4 Jan 2023 12:26:19 -1000
From:   Tejun Heo <tj@kernel.org>
To:     Richard Clark <richard.xnu.clark@gmail.com>
Cc:     jiangshanlai@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] workqueue: Add a new flag to spot the potential UAF error
Message-ID: <Y7X9CwLpuV/M4I+X@slm.duckdns.org>
References: <20221213043936.6345-1-richard.xnu.clark@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20221213043936.6345-1-richard.xnu.clark@gmail.com>
Precedence: bulk

On Tue, Dec 13, 2022 at 12:39:36PM +0800, Richard Clark wrote:
> Currently if the user queues a new work item unintentionally
> into a wq after the destroy_workqueue(wq), the work still can
> be queued and scheduled without any noticeable kernel message
> before the end of a RCU grace period.
> 
> As a debug-aid facility, this commit adds a new flag
> __WQ_DESTROYING to spot that issue by triggering a kernel WARN
> message.
> 
> Signed-off-by: Richard Clark <richard.xnu.clark@gmail.com>

Applied to wq/for-6.3 w/ whitespace adjustments.

Thanks.

-- 
tejun