From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Gleixner Subject: Re: Soft lockup issue in Linux 4.1.9 Date: Fri, 2 Oct 2015 23:04:29 +0200 (CEST) Message-ID: References: <1443650383.13282.10.camel@daevel.fr> <560D1223.3070606@googlemail.com> <560D1C5A.3050508@googlemail.com> <1443819583.32531.55.camel@edumazet-glaptop2.roam.corp.google.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Eric Dumazet , =?ISO-8859-15?Q?Holger_Hoffst=E4tte?= , "David S. Miller" , "Eric W. Biederman" , Stephen Hemminger , Greg Kroah-Hartman , LKML , stable@vger.kernel.org, netdev To: Eric Dumazet Return-path: In-Reply-To: <1443819583.32531.55.camel@edumazet-glaptop2.roam.corp.google.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Fri, 2 Oct 2015, Eric Dumazet wrote: > On Fri, 2015-10-02 at 22:04 +0200, Thomas Gleixner wrote: > > > What makes sure, that the timer cannot be readded while that timer > > callback is running? > > What is exactly your question ? CPU0 CPU1 timer expires callback add timer timer_pending() == true ===> del_timer_sync() I was just curious how this is prevented as I got lost in the networking code as usual :) Thanks, tglx