linux-kernel - Re: general protection fault in klist

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Sun, 5 Nov 2017 11:33:27 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     syzbot 
        <bot+f841f737eaae84758e88c9d3c5aaf4275c1ce556@...kaller.appspotmail.com>
Cc:     linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: Re: general protection fault in klist_put

On Sun, Nov 05, 2017 at 01:05:01AM -0700, syzbot wrote:
> Hello,
> 
> syzkaller hit the following crash on
> 36ef71cae353f88fd6e095e2aaa3e5953af1685d
> 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 output is attached.

<snip>

Thanks for reporting stuff like this, but really, this format of
reporting bugs is horrible, it does not contain any hints as to what you
were doing, nor how to reproduce it at all.

What am I supposed to do with this?  How do I know if this bug is ever
resolved?  When did it show up?  What workload caused it?

A strace really doesn't help much here, do you have a reproducer?

thanks,

greg k-h