From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933086AbcFTUXK (ORCPT ); Mon, 20 Jun 2016 16:23:10 -0400 Received: from mail-yw0-f195.google.com ([209.85.161.195]:33612 "EHLO mail-yw0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751790AbcFTUXC (ORCPT ); Mon, 20 Jun 2016 16:23:02 -0400 Date: Mon, 20 Jun 2016 16:20:53 -0400 From: Tejun Heo To: Petr Mladek 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 v9 09/12] kthread: Initial support for delayed kthread work Message-ID: <20160620202053.GA3262@mtj.duckdns.org> References: <1466075851-24013-1-git-send-email-pmladek@suse.com> <1466075851-24013-10-git-send-email-pmladek@suse.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1466075851-24013-10-git-send-email-pmladek@suse.com> User-Agent: Mutt/1.6.1 (2016-04-27) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, On Thu, Jun 16, 2016 at 01:17:28PM +0200, Petr Mladek wrote: > +/** > + * kthread_delayed_work_timer_fn - callback that queues the associated kthread > + * delayed work when the timer expires. > + * @__data: pointer to the data associated with the timer > + * > + * The format of the function is defined by struct timer_list. > + * It should have been called from irqsafe timer with irq already off. > + */ > +void kthread_delayed_work_timer_fn(unsigned long __data) > +{ > + struct kthread_delayed_work *dwork = > + (struct kthread_delayed_work *)__data; > + struct kthread_work *work = &dwork->work; > + struct kthread_worker *worker = work->worker; > + > + /* > + * This might happen when a pending work is reinitialized. > + * It means that it is used a wrong way. > + */ > + if (WARN_ON_ONCE(!worker)) > + return; > + > + spin_lock(&worker->lock); > + /* Work must not be used with more workers, see kthread_queue_work(). */ ^ ditto, this reads weird Other than that, Acked-by: Tejun Heo Thanks. -- tejun