Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754306Ab1CKN7Z (ORCPT ); Fri, 11 Mar 2011 08:59:25 -0500 Received: from mx1.redhat.com ([209.132.183.28]:49452 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752785Ab1CKN7W (ORCPT ); Fri, 11 Mar 2011 08:59:22 -0500 Date: Fri, 11 Mar 2011 14:50:23 +0100 From: Oleg Nesterov To: Alexander Shishkin Cc: Thomas Gleixner , 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 Message-ID: <20110311135023.GA23552@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 953 Lines: 26 > @@ -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? Oleg. -- 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/