lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 2 Oct 2015 23:04:29 +0200 (CEST) From: Thomas Gleixner <tglx@...utronix.de> To: Eric Dumazet <eric.dumazet@...il.com> cc: Eric Dumazet <edumazet@...gle.com>, Holger Hoffstätte <holger.hoffstaette@...glemail.com>, "David S. Miller" <davem@...emloft.net>, "Eric W. Biederman" <ebiederm@...ssion.com>, Stephen Hemminger <stephen@...workplumber.org>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, LKML <linux-kernel@...r.kernel.org>, stable@...r.kernel.org, netdev <netdev@...r.kernel.org> Subject: Re: Soft lockup issue in Linux 4.1.9 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 -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists