Re: INFO: rcu detected stall in kfree_skbmem

2018-05-26 Thread Dmitry Vyukov
On Mon, May 14, 2018 at 8:04 PM, Xin Long wrote: > On Mon, May 14, 2018 at 9:34 PM, Neil Horman wrote: >> On Fri, May 11, 2018 at 12:00:38PM +0200, Dmitry Vyukov wrote: >>> On Mon, Apr 30, 2018 at 8:09 PM, syzbot >>> wrote: >>> > Hello, >>> > >>> > syzbot found the following crash on: >>> > >>>

Re: INFO: rcu detected stall in kfree_skbmem

2018-05-14 Thread Xin Long
On Mon, May 14, 2018 at 9:34 PM, Neil Horman wrote: > On Fri, May 11, 2018 at 12:00:38PM +0200, Dmitry Vyukov wrote: >> On Mon, Apr 30, 2018 at 8:09 PM, syzbot >> wrote: >> > Hello, >> > >> > syzbot found the following crash on: >> > >> > HEAD commit:5d1365940a68 Merge >> > git://git.kernel.o

Re: INFO: rcu detected stall in kfree_skbmem

2018-05-14 Thread Neil Horman
On Fri, May 11, 2018 at 12:00:38PM +0200, Dmitry Vyukov wrote: > On Mon, Apr 30, 2018 at 8:09 PM, syzbot > wrote: > > Hello, > > > > syzbot found the following crash on: > > > > HEAD commit:5d1365940a68 Merge > > git://git.kernel.org/pub/scm/linux/kerne... > > git tree: net-next > > cons

Re: INFO: rcu detected stall in kfree_skbmem

2018-05-13 Thread Marcelo Ricardo Leitner
On Sun, May 13, 2018 at 03:52:01PM +0200, Dmitry Vyukov wrote: > On Fri, May 11, 2018 at 10:42 PM, Marcelo Ricardo Leitner > wrote: > > On Fri, May 11, 2018 at 12:08:33PM -0700, Eric Dumazet wrote: > >> > >> > >> On 05/11/2018 11:41 AM, Marcelo Ricardo Leitner wrote: > >> > >> > But calling ip6_xm

Re: INFO: rcu detected stall in kfree_skbmem

2018-05-13 Thread Dmitry Vyukov
On Fri, May 11, 2018 at 10:42 PM, Marcelo Ricardo Leitner wrote: > On Fri, May 11, 2018 at 12:08:33PM -0700, Eric Dumazet wrote: >> >> >> On 05/11/2018 11:41 AM, Marcelo Ricardo Leitner wrote: >> >> > But calling ip6_xmit with rcu_read_lock is expected. tcp stack also >> > does it. >> > Thus I thi

Re: INFO: rcu detected stall in kfree_skbmem

2018-05-11 Thread Marcelo Ricardo Leitner
On Fri, May 11, 2018 at 12:08:33PM -0700, Eric Dumazet wrote: > > > On 05/11/2018 11:41 AM, Marcelo Ricardo Leitner wrote: > > > But calling ip6_xmit with rcu_read_lock is expected. tcp stack also > > does it. > > Thus I think this is more of an issue with IPv6 stack. If a host has > > an extensive

Re: INFO: rcu detected stall in kfree_skbmem

2018-05-11 Thread Eric Dumazet
On 05/11/2018 11:41 AM, Marcelo Ricardo Leitner wrote: > But calling ip6_xmit with rcu_read_lock is expected. tcp stack also > does it. > Thus I think this is more of an issue with IPv6 stack. If a host has > an extensive ip6tables ruleset, it probably generates this more > easily. > >>> sctp_

Re: INFO: rcu detected stall in kfree_skbmem

2018-05-11 Thread Marcelo Ricardo Leitner
On Fri, May 11, 2018 at 12:00:38PM +0200, Dmitry Vyukov wrote: > On Mon, Apr 30, 2018 at 8:09 PM, syzbot > wrote: > > Hello, > > > > syzbot found the following crash on: > > > > HEAD commit:5d1365940a68 Merge > > git://git.kernel.org/pub/scm/linux/kerne... > > git tree: net-next > > cons

Re: INFO: rcu detected stall in kfree_skbmem

2018-05-11 Thread Dmitry Vyukov
On Mon, Apr 30, 2018 at 8:09 PM, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:5d1365940a68 Merge > git://git.kernel.org/pub/scm/linux/kerne... > git tree: net-next > console output: https://syzkaller.appspot.com/x/log.txt?id=5667997129637888 > kernel co

INFO: rcu detected stall in kfree_skbmem

2018-04-30 Thread syzbot
Hello, syzbot found the following crash on: HEAD commit:5d1365940a68 Merge git://git.kernel.org/pub/scm/linux/kerne... git tree: net-next console output: https://syzkaller.appspot.com/x/log.txt?id=5667997129637888 kernel config: https://syzkaller.appspot.com/x/.config?id=-5947642