From: Sander Eikelenboom <linux@eikelenboom.it>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Jon Christopherson <jon@jons.org>,
David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
xen-devel@lists.xen.org, david.vrabel@citrix.com
Subject: Re: Linux 4.2-rc6 regression: RIP: e030:[<ffffffff8110fb18>] [<ffffffff8110fb18>] detach_if_pending+0x18/0x80
Date: Mon, 17 Aug 2015 20:27:42 +0200 [thread overview]
Message-ID: <ae0cbd0dc71333ea44e4e756c8a004b3@eikelenboom.it> (raw)
In-Reply-To: <1439831928.32680.11.camel@edumazet-glaptop2.roam.corp.google.com>
On 2015-08-17 19:18, Eric Dumazet wrote:
> From: Eric Dumazet <edumazet@google.com>
>
> On Mon, 2015-08-17 at 16:25 +0200, Sander Eikelenboom wrote:
>> Monday, August 17, 2015, 4:21:47 PM, you wrote:
>>
>> > On Mon, 2015-08-17 at 09:02 -0500, Jon Christopherson wrote:
>> >> This is very similar to the behavior I am seeing in this bug:
>> >>
>> >> https://bugzilla.kernel.org/show_bug.cgi?id=102911
>>
>> > OK, but have you applied the fix ?
>>
>> > http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=83fccfc3940c4a2db90fd7e7079f5b465cd8c6af
>>
>> > It will be part of net iteration from David Miller to Linus Torvald.
>>
>>
>> I did have that patch in for my last report.
>> But i don't think he had (looking at the second part of his oops).
>>
>
> Then can you try following fix as well ?
>
> Thanks !
Running now :)
>
> [PATCH] timer: fix a race in __mod_timer()
>
> lock_timer_base() can not catch following :
>
> CPU1 ( in __mod_timer()
> timer->flags |= TIMER_MIGRATING;
> spin_unlock(&base->lock);
> base = new_base;
> spin_lock(&base->lock);
> timer->flags &= ~TIMER_BASEMASK;
> CPU2 (in lock_timer_base())
> see timer base is cpu0 base
> spin_lock_irqsave(&base->lock,
> *flags);
> if (timer->flags == tf)
> return base; // oops, wrong base
> timer->flags |= base->cpu // too late
>
> We must write timer->flags in one go, otherwise we can fool other cpus.
>
> Fixes: bc7a34b8b9eb ("timer: Reduce timer migration overhead if
> disabled")
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> ---
> kernel/time/timer.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/time/timer.c b/kernel/time/timer.c
> index 5e097fa9faf7..84190f02b521 100644
> --- a/kernel/time/timer.c
> +++ b/kernel/time/timer.c
> @@ -807,8 +807,8 @@ __mod_timer(struct timer_list *timer, unsigned long
> expires,
> spin_unlock(&base->lock);
> base = new_base;
> spin_lock(&base->lock);
> - timer->flags &= ~TIMER_BASEMASK;
> - timer->flags |= base->cpu;
> + WRITE_ONCE(timer->flags,
> + (timer->flags & ~TIMER_BASEMASK) | base->cpu);
> }
> }
next prev parent reply other threads:[~2015-08-17 18:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 19:19 linux
2015-08-12 20:41 ` Eric Dumazet
2015-08-12 20:50 ` linux
2015-08-12 21:40 ` David Miller
2015-08-12 21:46 ` Sander Eikelenboom
2015-08-12 22:41 ` Eric Dumazet
2015-08-14 22:09 ` Sander Eikelenboom
2015-08-14 22:16 ` Sander Eikelenboom
2015-08-14 22:39 ` Eric Dumazet
2015-08-17 9:09 ` Sander Eikelenboom
2015-08-17 13:37 ` Eric Dumazet
2015-08-17 13:48 ` Sander Eikelenboom
2015-08-17 14:02 ` Jon Christopherson
2015-08-17 14:21 ` Eric Dumazet
2015-08-17 14:25 ` Sander Eikelenboom
2015-08-17 15:16 ` Jon Christopherson
2015-08-17 17:18 ` Eric Dumazet
2015-08-17 18:27 ` Sander Eikelenboom [this message]
2015-08-17 19:13 ` Thomas Gleixner
2015-08-18 0:05 ` Jon Christopherson
2015-08-18 13:36 ` [tip:timers/urgent] timer: Write timer->flags atomically tip-bot for Eric Dumazet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ae0cbd0dc71333ea44e4e756c8a004b3@eikelenboom.it \
--to=linux@eikelenboom.it \
--cc=davem@davemloft.net \
--cc=david.vrabel@citrix.com \
--cc=eric.dumazet@gmail.com \
--cc=jon@jons.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome