From: David Miller <davem@davemloft.net>
To: Jason@zx2c4.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
tgraf@suug.ch, tom@herbertland.com, jbenc@redhat.com,
kuznet@ms2.inr.ac.ru
Subject: Re: [PATCH v2] ip_tunnel: disable preemption when updating per-cpu tstats
Date: Mon, 16 Nov 2015 14:17:37 -0500 (EST) [thread overview]
Message-ID: <20151116.141737.420755936779587001.davem@davemloft.net> (raw)
In-Reply-To: <1447346158-19257-1-git-send-email-Jason@zx2c4.com>
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
Date: Thu, 12 Nov 2015 17:35:58 +0100
> Drivers like vxlan use the recently introduced
> udp_tunnel_xmit_skb/udp_tunnel6_xmit_skb APIs. udp_tunnel6_xmit_skb
> makes use of ip6tunnel_xmit, and ip6tunnel_xmit, after sending the
> packet, updates the struct stats using the usual
> u64_stats_update_begin/end calls on this_cpu_ptr(dev->tstats).
> udp_tunnel_xmit_skb makes use of iptunnel_xmit, which doesn't touch
> tstats, so drivers like vxlan, immediately after, call
> iptunnel_xmit_stats, which does the same thing - calls
> u64_stats_update_begin/end on this_cpu_ptr(dev->tstats).
>
> While vxlan is probably fine (I don't know?), calling a similar function
> from, say, an unbound workqueue, on a fully preemptable kernel causes
> real issues:
>
> [ 188.434537] BUG: using smp_processor_id() in preemptible [00000000] code: kworker/u8:0/6
> [ 188.435579] caller is debug_smp_processor_id+0x17/0x20
> [ 188.435583] CPU: 0 PID: 6 Comm: kworker/u8:0 Not tainted 4.2.6 #2
> [ 188.435607] Call Trace:
> [ 188.435611] [<ffffffff8234e936>] dump_stack+0x4f/0x7b
> [ 188.435615] [<ffffffff81915f3d>] check_preemption_disabled+0x19d/0x1c0
> [ 188.435619] [<ffffffff81915f77>] debug_smp_processor_id+0x17/0x20
>
> The solution would be to protect the whole
> this_cpu_ptr(dev->tstats)/u64_stats_update_begin/end blocks with
> disabling preemption and then reenabling it.
>
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
Applied and queued up for -stable, thanks Jason
Arguably, ip6tunnel_xmit() is primarily a ->ndo_start_xmit() and
therefore could assume that it only ran inside of a BH disabled code
sequence. And as you noted, when this was turned into a general case
helper function that guarantee was no longer necessarily there.
So another fix could have been to do local_bh_disable() in the
udp_tunnel6_xmit_skb() helper.
Thanks again.
next prev parent reply other threads:[~2015-11-16 19:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 15:30 [PATCH] " Jason A. Donenfeld
2015-11-12 16:25 ` Hannes Frederic Sowa
2015-11-12 16:36 ` Jason A. Donenfeld
2015-11-12 16:52 ` Jason A. Donenfeld
2015-11-12 16:35 ` [PATCH v2] " Jason A. Donenfeld
2015-11-16 10:04 ` Hannes Frederic Sowa
2015-11-16 19:17 ` David Miller [this message]
2015-11-16 19:33 ` Jason A. Donenfeld
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=20151116.141737.420755936779587001.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Jason@zx2c4.com \
--cc=jbenc@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
--cc=tom@herbertland.com \
/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
all inboxes | Powered by JetHome®