From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933098AbcBPQin (ORCPT ); Tue, 16 Feb 2016 11:38:43 -0500 Received: from mx2.suse.de ([195.135.220.15]:51883 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932179AbcBPQim (ORCPT ); Tue, 16 Feb 2016 11:38:42 -0500 Date: Tue, 16 Feb 2016 17:38:39 +0100 From: Petr Mladek To: Tejun Heo Cc: Andrew Morton , Oleg Nesterov , Ingo Molnar , Peter Zijlstra , Steven Rostedt , "Paul E. McKenney" , Josh Triplett , Thomas Gleixner , Linus Torvalds , Jiri Kosina , Borislav Petkov , Michal Hocko , linux-mm@kvack.org, Vlastimil Babka , linux-api@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v4 07/22] kthread: Detect when a kthread work is used by more workers Message-ID: <20160216163839.GP3305@pathway.suse.cz> References: <1453736711-6703-1-git-send-email-pmladek@suse.com> <1453736711-6703-8-git-send-email-pmladek@suse.com> <20160125185747.GC3628@mtj.duckdns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160125185747.GC3628@mtj.duckdns.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon 2016-01-25 13:57:47, Tejun Heo wrote: > On Mon, Jan 25, 2016 at 04:44:56PM +0100, Petr Mladek wrote: > > +static void insert_kthread_work_sanity_check(struct kthread_worker *worker, > > + struct kthread_work *work) > > +{ > > + lockdep_assert_held(&worker->lock); > > + WARN_ON_ONCE(!irqs_disabled()); > > Isn't worker->lock gonna be a irq-safe lock? If so, why would this > need to be tested separately? I see. I'll remove it. > > + WARN_ON_ONCE(!list_empty(&work->node)); > > + /* Do not use a work with more workers, see queue_kthread_work() */ > > + WARN_ON_ONCE(work->worker && work->worker != worker); > > +} > > Is this sanity check function gonna be used from multiple places? It will be reused when implementing __queue_delayed_kthread_work(). We will want to do these checks also before setting the timer. See the 8th patch, e.g. at http://thread.gmane.org/gmane.linux.kernel.mm/144964/focus=144973 > > /* insert @work before @pos in @worker */ > > static void insert_kthread_work(struct kthread_worker *worker, > > - struct kthread_work *work, > > - struct list_head *pos) > > + struct kthread_work *work, > > + struct list_head *pos) > > { > > - lockdep_assert_held(&worker->lock); > > + insert_kthread_work_sanity_check(worker, work); > > > > list_add_tail(&work->node, pos); > > work->worker = worker; > > @@ -717,6 +730,15 @@ static void insert_kthread_work(struct kthread_worker *worker, > > * Queue @work to work processor @task for async execution. @task > > * must have been created with kthread_worker_create(). Returns %true > > * if @work was successfully queued, %false if it was already pending. > > + * > > + * Never queue a work into a worker when it is being processed by another > > + * one. Otherwise, some operations, e.g. cancel or flush, will not work > > + * correctly or the work might run in parallel. This is not enforced > > + * because it would make the code too complex. There are only warnings > > + * printed when such a situation is detected. > > I'm not sure the above paragraph adds much. It isn't that accurate to > begin with as what's being disallowed is larger scope than the above. > Isn't the paragraph below enough? Makes sense. I'll remove it. > > + * Reinitialize the work if it needs to be used by another worker. > > + * For example, when the worker was stopped and started again. > > */ > > bool queue_kthread_work(struct kthread_worker *worker, > > struct kthread_work *work) Thanks, Petr