Re: WARNING in kernfs_add_one

2018-05-07 Thread Tetsuo Handa
On 2018/05/06 7:07, Greg KH wrote: >> More likely wireless territory > > Ugh, that's what I get for writing emails before coffee in the > morning... > > Yes, you are right, this looks like a wireless issue. > > Now cc: linux-wireless. > Nope, if you look at previous fault injection messages...

Re: WARNING in kernfs_add_one

2018-05-07 Thread Tetsuo Handa
On 2018/05/06 7:07, Greg KH wrote: >> More likely wireless territory > > Ugh, that's what I get for writing emails before coffee in the > morning... > > Yes, you are right, this looks like a wireless issue. > > Now cc: linux-wireless. > Nope, if you look at previous fault injection messages...

Re: WARNING in kernfs_add_one

2018-05-07 Thread Johannes Berg
On Mon, 2018-05-07 at 11:33 +0200, Dmitry Vyukov wrote: > On Mon, May 7, 2018 at 10:43 AM, Johannes Berg > wrote: > > On Sat, 2018-05-05 at 15:07 -0700, Greg KH wrote: > > > > > > > > syzbot found the following crash on: > > > > Maybe it should learn to differentiate

Re: WARNING in kernfs_add_one

2018-05-07 Thread Johannes Berg
On Mon, 2018-05-07 at 11:33 +0200, Dmitry Vyukov wrote: > On Mon, May 7, 2018 at 10:43 AM, Johannes Berg > wrote: > > On Sat, 2018-05-05 at 15:07 -0700, Greg KH wrote: > > > > > > > > syzbot found the following crash on: > > > > Maybe it should learn to differentiate warnings, if it's going to

Re: WARNING in kernfs_add_one

2018-05-07 Thread Dmitry Vyukov
On Mon, May 7, 2018 at 10:43 AM, Johannes Berg wrote: > On Sat, 2018-05-05 at 15:07 -0700, Greg KH wrote: > >> > > > syzbot found the following crash on: > > Maybe it should learn to differentiate warnings, if it's going to set > panic_on_warn :-) How? Note that this

Re: WARNING in kernfs_add_one

2018-05-07 Thread Dmitry Vyukov
On Mon, May 7, 2018 at 10:43 AM, Johannes Berg wrote: > On Sat, 2018-05-05 at 15:07 -0700, Greg KH wrote: > >> > > > syzbot found the following crash on: > > Maybe it should learn to differentiate warnings, if it's going to set > panic_on_warn :-) How? Note that this is not specific to syzbot.

Re: WARNING in kernfs_add_one

2018-05-07 Thread Johannes Berg
On Sat, 2018-05-05 at 15:07 -0700, Greg KH wrote: > > > > syzbot found the following crash on: Maybe it should learn to differentiate warnings, if it's going to set panic_on_warn :-) I get why, but still, at least differentiating in the emails wouldn't be bad. > > > > kernfs: ns required in

Re: WARNING in kernfs_add_one

2018-05-07 Thread Johannes Berg
On Sat, 2018-05-05 at 15:07 -0700, Greg KH wrote: > > > > syzbot found the following crash on: Maybe it should learn to differentiate warnings, if it's going to set panic_on_warn :-) I get why, but still, at least differentiating in the emails wouldn't be bad. > > > > kernfs: ns required in

Re: WARNING in kernfs_add_one

2018-05-05 Thread Greg KH
On Sat, May 05, 2018 at 10:43:45AM -0700, Eric Dumazet wrote: > > > On 05/05/2018 09:40 AM, Greg KH wrote: > > On Sat, May 05, 2018 at 08:47:02AM -0700, syzbot wrote: > >> Hello, > >> > >> syzbot found the following crash on: > >> > >> HEAD commit:8fb11a9a8d51 net/ipv6: rename rt6_next to

Re: WARNING in kernfs_add_one

2018-05-05 Thread Greg KH
On Sat, May 05, 2018 at 10:43:45AM -0700, Eric Dumazet wrote: > > > On 05/05/2018 09:40 AM, Greg KH wrote: > > On Sat, May 05, 2018 at 08:47:02AM -0700, syzbot wrote: > >> Hello, > >> > >> syzbot found the following crash on: > >> > >> HEAD commit:8fb11a9a8d51 net/ipv6: rename rt6_next to

Re: WARNING in kernfs_add_one

2018-05-05 Thread Eric Dumazet
On 05/05/2018 09:40 AM, Greg KH wrote: > On Sat, May 05, 2018 at 08:47:02AM -0700, syzbot wrote: >> Hello, >> >> syzbot found the following crash on: >> >> HEAD commit:8fb11a9a8d51 net/ipv6: rename rt6_next to fib6_next >> git tree: net-next >> console output:

Re: WARNING in kernfs_add_one

2018-05-05 Thread Eric Dumazet
On 05/05/2018 09:40 AM, Greg KH wrote: > On Sat, May 05, 2018 at 08:47:02AM -0700, syzbot wrote: >> Hello, >> >> syzbot found the following crash on: >> >> HEAD commit:8fb11a9a8d51 net/ipv6: rename rt6_next to fib6_next >> git tree: net-next >> console output:

Re: WARNING in kernfs_add_one

2018-05-05 Thread Greg KH
On Sat, May 05, 2018 at 08:47:02AM -0700, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:8fb11a9a8d51 net/ipv6: rename rt6_next to fib6_next > git tree: net-next > console output: https://syzkaller.appspot.com/x/log.txt?x=14b2723780 > kernel config:

Re: WARNING in kernfs_add_one

2018-05-05 Thread Greg KH
On Sat, May 05, 2018 at 08:47:02AM -0700, syzbot wrote: > Hello, > > syzbot found the following crash on: > > HEAD commit:8fb11a9a8d51 net/ipv6: rename rt6_next to fib6_next > git tree: net-next > console output: https://syzkaller.appspot.com/x/log.txt?x=14b2723780 > kernel config:

WARNING in kernfs_add_one

2018-05-05 Thread syzbot
Hello, syzbot found the following crash on: HEAD commit:8fb11a9a8d51 net/ipv6: rename rt6_next to fib6_next git tree: net-next console output: https://syzkaller.appspot.com/x/log.txt?x=14b2723780 kernel config: https://syzkaller.appspot.com/x/.config?x=c416c61f3cd96be dashboard

WARNING in kernfs_add_one

2018-05-05 Thread syzbot
Hello, syzbot found the following crash on: HEAD commit:8fb11a9a8d51 net/ipv6: rename rt6_next to fib6_next git tree: net-next console output: https://syzkaller.appspot.com/x/log.txt?x=14b2723780 kernel config: https://syzkaller.appspot.com/x/.config?x=c416c61f3cd96be dashboard