linux-kernel - Re: BUG: spinlock bad magic (2)

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Mon, 18 Dec 2017 18:01:30 +0100
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     Santosh Shilimkar <santosh.shilimkar@...cle.com>
Cc:     syzbot 
        <bot+d3f5d339869eb8cd834d2c9f0a88bf4f05c29781@...kaller.appspotmail.com>,
        David Miller <davem@...emloft.net>,
        LKML <linux-kernel@...r.kernel.org>, linux-rdma@...r.kernel.org,
        netdev <netdev@...r.kernel.org>, rds-devel@....oracle.com,
        syzkaller-bugs@...glegroups.com
Subject: Re: BUG: spinlock bad magic (2)

On Mon, Dec 18, 2017 at 5:46 PM, Santosh Shilimkar
<santosh.shilimkar@...cle.com> wrote:
> On 12/18/2017 4:36 AM, syzbot wrote:
>>
>> Hello,
>>
>> syzkaller hit the following crash on
>> 6084b576dca2e898f5c101baef151f7bfdbb606d
>> 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.
>>
>> Unfortunately, I don't have any reproducer for this bug yet.
>>
> [...]
>
>> BUG: unable to handle kernel NULL pointer dereference at 0000000000000028
>> IP: rds_send_xmit+0x80/0x930 net/rds/send.c:186
>
>
> This one seems to be same bug as reported as below.
>
> BUG: unable to handle kernel NULL pointer dereference in rds_send_xmit

Hi Santosh,

The proper syntax to tell syzbot about dups is this (from email footer):

> See https://goo.gl/tpsmEJ for details.
> Please credit me with: Reported-by: syzbot <syzkaller@...glegroups.com>
> syzbot will keep track of this bug report.
> To mark this as a duplicate of another syzbot report, please reply with:
> #syz dup: exact-subject-of-another-report
> Note: all commands must start from beginning of the line in the email body.