Re: general protection fault in __lock_acquire (2)

2018-01-26 Thread Eric Biggers
On Thu, Nov 02, 2017 at 03:55:00AM -0700, syzbot wrote: > Hello, > > syzkaller hit the following crash on > fa8785e862ef644f742558f1a8c91eca6f3f0004 > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console o

Re: general protection fault in __lock_acquire (2)

2017-12-03 Thread Cong Wang
On Sun, Dec 3, 2017 at 4:33 PM, syzbot wrote: > syzkaller has found reproducer for the following crash on > fb7516d42478ebc8e2f00efb76ef96f7b68fd8d3 > git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw console ou

Re: syzbot:dup: general protection fault in __lock_acquire (2)

2017-11-08 Thread Dmitry Vyukov
But commands must be in email body, i.e.: #syz dup: general protection fault in __lock_acquire (2) I've updated the email template to clarify that it's meant to be email body to avoid confusion in future: https://github.com/google/syzkaller/commit/9547ae3a85db67e4d3abe9ee7782a41b782a790

syzbot:dup: general protection fault in __lock_acquire (2)

2017-11-05 Thread Jon Maloy
The problem was already known, but the solution is non-trivial, and needs some more review and testing before I can submit it. ///Jon Maloy > -Original Message- > From: syzbot > [mailto:bot+0cea668556ca5b811dc9725d82edbd87fea4defb@syzkaller.appsp > otmail.com] > Sent: Sunday, November 0