Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S272796AbTG3Hg7 (ORCPT ); Wed, 30 Jul 2003 03:36:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S272798AbTG3Hg6 (ORCPT ); Wed, 30 Jul 2003 03:36:58 -0400 Received: from mx1.elte.hu ([157.181.1.137]:8620 "EHLO mx1.elte.hu") by vger.kernel.org with ESMTP id S272796AbTG3Hg5 (ORCPT ); Wed, 30 Jul 2003 03:36:57 -0400 Date: Wed, 30 Jul 2003 09:34:40 +0200 (CEST) From: Ingo Molnar Reply-To: Ingo Molnar To: Andrea Arcangeli Cc: Andrew Morton , , Subject: Re: PATCH: Race in 2.6.0-test2 timer code In-Reply-To: <20030730073458.GA23835@dualathlon.random> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 741 Lines: 23 On Wed, 30 Jul 2003, Andrea Arcangeli wrote: > The thing triggered simply by running setitimer in one function, while > the it_real_fn was running in the other cpu. I don't see how 2.6 can > have fixed this, it_real_fun can still trivially call add_timer while > you run inside do_setitimer in 2.6 too. [...] This is not a race that can happen. itimer does this: del_timer_sync(); add_timer(); how can the add_timer() still happen while it_real_fn is still running on another CPU? Ingo - 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/