From: Thomas Huth <thuth@linux.vnet.ibm.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org, Vlad Yasevich <vyasevic@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>
Subject: Re: macvtap bug: using smp_processor_id() in preemptible code
Date: Thu, 8 Aug 2013 15:56:34 +0200 [thread overview]
Message-ID: <20130808155634.239dbc2d@thhw500> (raw)
In-Reply-To: <1375968072.4004.92.camel@edumazet-glaptop>
Am Thu, 08 Aug 2013 06:21:12 -0700
schrieb Eric Dumazet <eric.dumazet@gmail.com>:
> On Thu, 2013-08-08 at 10:25 +0200, Thomas Huth wrote:
>
> > Thank you very much for your fast reply and the fix, it indeed fixes
> > the messages about macvtap_do_read!
> > However, I now noticed that there are more messages, which I just did
> > not see before because my dmesg output was already flooded with the
> > messages about macvtap_do_read. The other messages are all about
> > macvlan_start_xmit:
> >
> > BUG: using smp_processor_id() in preemptible [00000000] code: vhost-45897/45898
> > caller is macvlan_start_xmit+0x10a/0x1b4 [macvlan]
> > CPU: 1 PID: 45898 Comm: vhost-45897 Not tainted 3.11.0-bisecttest #16
> > 00000001189b3960 00000001189b3970 0000000000000002 0000000000000000
> > 00000001189b3a00 00000001189b3978 00000001189b3978 00000000001127b4
> > 0000000000000000 0000000000000001 0000000000000000 000000000000000b
> > 0000000000000060 000003fe00000008 0000000000000000 00000001189b39d0
> > 00000000006ea2f0 00000000001127b4 00000001189b3960 00000001189b39b0
> > Call Trace:
> > ([<00000000001126ee>] show_trace+0x126/0x144)
> > [<00000000001127d2>] show_stack+0xc6/0xd4
> > [<000000000068bdb8>] dump_stack+0x74/0xd4
> > [<0000000000481132>] debug_smp_processor_id+0xf6/0x114
> > [<000003ff802b72ca>] macvlan_start_xmit+0x10a/0x1b4 [macvlan]
> > [<000003ff802ea69a>] macvtap_get_user+0x982/0xbc4 [macvtap]
> > [<000003ff802ea92a>] macvtap_sendmsg+0x4e/0x60 [macvtap]
> > [<000003ff8031947c>] handle_tx+0x494/0x5ec [vhost_net]
> > [<000003ff8028f77c>] vhost_worker+0x15c/0x1c4 [vhost]
> > [<000000000015f3ac>] kthread+0xd8/0xe4
> > [<000000000069356e>] kernel_thread_starter+0x6/0xc
> > [<0000000000693568>] kernel_thread_starter+0x0/0xc
> > 2 locks held by vhost-45897/45898:
> > #0: (&vq->mutex){+.+.+.}, at: [<000003ff8031903c>] handle_tx+0x54/0x5ec [vhost_net]
> > #1: (rcu_read_lock){.+.+..}, at: [<000003ff802ea53c>] macvtap_get_user+0x824/0xbc4 [macvtap]
> >
> > Do you also have got an idea how to silence these messages?
>
> Sure, please try following cumulative patch, thanks !
>
> diff --git a/drivers/net/macvtap.c b/drivers/net/macvtap.c
> index a98fb0e..b51db2a 100644
> --- a/drivers/net/macvtap.c
> +++ b/drivers/net/macvtap.c
> @@ -818,10 +818,13 @@ static ssize_t macvtap_get_user(struct macvtap_queue *q, struct msghdr *m,
> skb_shinfo(skb)->tx_flags |= SKBTX_DEV_ZEROCOPY;
> skb_shinfo(skb)->tx_flags |= SKBTX_SHARED_FRAG;
> }
> - if (vlan)
> + if (vlan) {
> + local_bh_disable();
> macvlan_start_xmit(skb, vlan->dev);
> - else
> + local_bh_enable();
> + } else {
> kfree_skb(skb);
> + }
> rcu_read_unlock();
>
> return total_len;
> @@ -912,8 +915,11 @@ static ssize_t macvtap_put_user(struct macvtap_queue *q,
> done:
> rcu_read_lock();
> vlan = rcu_dereference(q->vlan);
> - if (vlan)
> + if (vlan) {
> + preempt_disable();
> macvlan_count_rx(vlan, copied - vnet_hdr_len, ret == 0, 0);
> + preempt_enable();
> + }
> rcu_read_unlock();
>
> return ret ? ret : copied;
This patch now silences all error messages! Great, thank you very much!
If you submit this patch, you can add my
Tested-by: Thomas Huth <thuth@linux.vnet.ibm.com>
if you like.
Thomas
next prev parent reply other threads:[~2013-08-08 13:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 14:43 macvtap bug: using smp_processor_id() in preemptible code Thomas Huth
2013-08-07 15:26 ` Eric Dumazet
2013-08-08 8:25 ` Thomas Huth
2013-08-08 13:21 ` Eric Dumazet
2013-08-08 13:56 ` Thomas Huth [this message]
2013-08-08 14:04 ` Eric Dumazet
2013-08-08 15:06 ` [PATCH] macvtap: fix two races Eric Dumazet
2013-08-09 17:16 ` Vlad Yasevich
2013-08-09 17:41 ` Eric Dumazet
2013-08-09 18:01 ` Vlad Yasevich
2013-08-12 4:50 ` David Miller
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=20130808155634.239dbc2d@thhw500 \
--to=thuth@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=vyasevic@redhat.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;
as well as URLs for NNTP newsgroup(s).