From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Dmitry Vyukov <dvyukov@google.com>,
David Miller <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Cong Wang <xiyou.wangcong@gmail.com>,
netdev <netdev@vger.kernel.org>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: net: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected in skb_array_produce
Date: Thu, 9 Feb 2017 20:10:05 +0200 [thread overview]
Message-ID: <20170209200936-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <50038580.20299907.1486634551103.JavaMail.zimbra@redhat.com>
On Thu, Feb 09, 2017 at 05:02:31AM -0500, Jason Wang wrote:
>
>
> ----- Original Message -----
> > Hello,
> >
> > I've got the following report while running syzkaller fuzzer on mmotm
> > (git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git)
> > remotes/mmotm/auto-latest ee4ba7533626ba7bf2f8b992266467ac9fdc045e:
> >
>
> [...]
>
> >
> > other info that might help us debug this:
> >
> > Possible interrupt unsafe locking scenario:
> >
> > CPU0 CPU1
> > ---- ----
> > lock(&(&r->consumer_lock)->rlock);
> > local_irq_disable();
> > lock(&(&r->producer_lock)->rlock);
> > lock(&(&r->consumer_lock)->rlock);
> > <Interrupt>
> > lock(&(&r->producer_lock)->rlock);
> >
>
> Thanks a lot for the testing.
>
> Looks like we could address this by using skb_array_consume_bh() instead.
>
> Could you pls verify if the following patch works?
I think we should use _bh for the produce call as well,
since resizing takes the producer lock.
> diff --git a/drivers/net/tun.c b/drivers/net/tun.c
> index 8a7d6b9..a97c00d 100644
> --- a/drivers/net/tun.c
> +++ b/drivers/net/tun.c
> @@ -520,7 +520,7 @@ static void tun_queue_purge(struct tun_file *tfile)
> {
> struct sk_buff *skb;
>
> - while ((skb = skb_array_consume(&tfile->tx_array)) != NULL)
> + while ((skb = skb_array_consume_bh(&tfile->tx_array)) != NULL)
> kfree_skb(skb);
>
> skb_queue_purge(&tfile->sk.sk_write_queue);
> @@ -1458,7 +1458,7 @@ static struct sk_buff *tun_ring_recv(struct tun_file *tfile, int noblock,
> struct sk_buff *skb = NULL;
> int error = 0;
>
> - skb = skb_array_consume(&tfile->tx_array);
> + skb = skb_array_consume_bh(&tfile->tx_array);
> if (skb)
> goto out;
> if (noblock) {
> @@ -1470,7 +1470,7 @@ static struct sk_buff *tun_ring_recv(struct tun_file *tfile, int noblock,
> current->state = TASK_INTERRUPTIBLE;
>
> while (1) {
> - skb = skb_array_consume(&tfile->tx_array);
> + skb = skb_array_consume_bh(&tfile->tx_array);
> if (skb)
> break;
> if (signal_pending(current)) {
next prev parent reply other threads:[~2017-02-09 18:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 8:38 net: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected in skb_array_produce Dmitry Vyukov
2017-02-09 10:02 ` Jason Wang
2017-02-09 10:49 ` Dmitry Vyukov
2017-02-09 17:50 ` Michael S. Tsirkin
2017-02-09 17:55 ` Dmitry Vyukov
2017-02-09 18:10 ` Michael S. Tsirkin
2017-02-10 5:13 ` Jason Wang
2017-02-09 18:10 ` Michael S. Tsirkin [this message]
2017-02-10 5:17 ` Jason Wang
2017-02-18 17:28 ` Dmitry Vyukov
2017-02-18 17:35 ` Dmitry Vyukov
2017-02-19 5:18 ` Michael S. Tsirkin
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=20170209200936-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller@googlegroups.com \
--cc=xiyou.wangcong@gmail.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).