Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 9 Sep 2020 15:51:05 -0700
From:   Jakub Kicinski <kuba@kernel.org>
To:     Vinicius Costa Gomes <vinicius.gomes@intel.com>
Cc:     syzbot <syzbot+8267241609ae8c23b248@syzkaller.appspotmail.com>,
        davem@davemloft.net, jhs@mojatatu.com, jiri@resnulli.us,
        linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
        syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
        xiyou.wangcong@gmail.com
Subject: Re: INFO: rcu detected stall in cleanup_net (4)
Message-ID: <20200909155105.5efb291a@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
In-Reply-To: <877dt2pqeb.fsf@intel.com>
References: <000000000000db78de05aedabb5a@google.com>
        <20200909085203.5e335c61@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
        <877dt2pqeb.fsf@intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Wed, 09 Sep 2020 14:54:36 -0700 Vinicius Costa Gomes wrote:
> > Vinicius, could you please take a look at all the syzbot reports which
> > point to your commit? I know syzbot bisection is not super reliable,
> > but at least 3 reports point to your commit now, so something's
> > probably going on.  
> 
> I did take a look, and it seems that it all boils down to having too
> small (unreasonable?) intervals in the schedule, which causes the
> hrtimer handler to starve the other kernel threads.
> 
> I have a quick fix to restrict the interval values to more sensible
> values (at least equal to the time it takes to transmit the mininum
> ethernet frame size), I am testing it and I will propose it soon. But a
> proper solution will require more time.

Great, thank you!