From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754455AbdBIR6b (ORCPT ); Thu, 9 Feb 2017 12:58:31 -0500 Received: from mx1.redhat.com ([209.132.183.28]:60222 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754433AbdBIR6a (ORCPT ); Thu, 9 Feb 2017 12:58:30 -0500 Date: Thu, 9 Feb 2017 19:50:11 +0200 From: "Michael S. Tsirkin" To: Dmitry Vyukov Cc: Jason Wang , David Miller , Eric Dumazet , LKML , Cong Wang , netdev , syzkaller Subject: Re: net: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected in skb_array_produce Message-ID: <20170209194943-mutt-send-email-mst@kernel.org> References: <50038580.20299907.1486634551103.JavaMail.zimbra@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Thu, 09 Feb 2017 17:50:13 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 09, 2017 at 11:49:30AM +0100, Dmitry Vyukov wrote: > On Thu, Feb 9, 2017 at 11:02 AM, 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); > >> > >> 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? > > No, I can't test it, sorry. This happened once on bots. And bots > currently test only upstream versions. Which trees are tested? Will linux-next help? > > > 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)) { > > > > -- > > You received this message because you are subscribed to the Google Groups "syzkaller" group. > > To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller+unsubscribe@googlegroups.com. > > For more options, visit https://groups.google.com/d/optout.