Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756018Ab1CKQYT (ORCPT ); Fri, 11 Mar 2011 11:24:19 -0500 Received: from www.tglx.de ([62.245.132.106]:37305 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753009Ab1CKQYP (ORCPT ); Fri, 11 Mar 2011 11:24:15 -0500 Date: Fri, 11 Mar 2011 17:23:36 +0100 (CET) From: Thomas Gleixner To: Oleg Nesterov cc: Alexander Shishkin , Alexander Viro , Greg Kroah-Hartman , Feng Tang , Michael Tokarev , Marcelo Tosatti , John Stultz , Chris Friesen , Kay Sievers , "Kirill A. Shutemov" , Artem Bityutskiy , Davide Libenzi , Michael Kerrisk , linux-api@vger.kernel.org, Andrew Morton , linux-kernel@vger.kernel.org Subject: Re: timerfd-add-tfd_notify_clock_set-to-watch-for-clock-changes.patch added to -mm tree In-Reply-To: <20110311135023.GA23552@redhat.com> Message-ID: References: <20110311135023.GA23552@redhat.com> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1078 Lines: 31 On Fri, 11 Mar 2011, Oleg Nesterov wrote: > > @@ -218,10 +266,12 @@ SYSCALL_DEFINE4(timerfd_settime, int, uf > > * it to the new values. > > */ > > for (;;) { > > + spin_lock(¬ifiers_lock); > > spin_lock_irq(&ctx->wqh.lock); > > - if (hrtimer_try_to_cancel(&ctx->tmr) >= 0) > > + if (!list_empty(¬ifiers_list) || hrtimer_try_to_cancel(&ctx->tmr) >= 0) > > break; > > Confused. Why do we check the global notifiers_list? > > IOW. Suppose that this list is not empty and timerfd_settime() is called > without TFD_NOTIFY_CLOCK_SET. Now we are going to reprogramm the timer > without stopping it? > > And. What if timerfd_settime(TFD_NOTIFY_CLOCK_SET, utmr => NULL) is called > twice? timerfd_setup() blindly does list_add(), and we corrupt the list, no? And why is this hack in -mm at all ? Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/