linux-kernel - Re: BUG: unable to handle kernel NULL pointer dereference in __list_del_entry

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]

Message-ID: <CACT4Y+YqwhSyxRAGVQNQBqKPVe4WKa=5ZyKfW78qY9CDOs1r3w@mail.gmail.com>
Date:   Tue, 19 Dec 2017 17:40:19 +0100
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     Michal Hocko <mhocko@...nel.org>
Cc:     syzbot 
        <bot+83f46cd25e266359cd056c91f6ecd20b04eddf42@...kaller.appspotmail.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Johannes Weiner <hannes@...xchg.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Linux-MM <linux-mm@...ck.org>,
        Mel Gorman <mgorman@...hsingularity.net>,
        Minchan Kim <minchan@...nel.org>, shakeelb@...gle.com,
        syzkaller-bugs@...glegroups.com, ying.huang@...el.com,
        syzkaller <syzkaller@...glegroups.com>
Subject: Re: BUG: unable to handle kernel NULL pointer dereference in __list_del_entry_valid

On Tue, Dec 19, 2017 at 2:42 PM, Michal Hocko <mhocko@...nel.org> wrote:
>> >> > Can we silence this duplicates [1] please?
>> >> >
>> >> > [1] http://lkml.kernel.org/r/001a1140f57806ebef05608b25a5@google.com
>> >>
>> >> Hi Michal,
>> >>
>> >> What exactly do you mean?
>> >>
>> >> These 2 are the same email with the same Message-ID just on different
>> >> mailing lists. I don't see anything wrong here.
>> >
>> > Hmm the other one has Message-id: 001a1140f57806ebef05608b25a5@...gle.com
>> > while this one has 001a11452568f5857c0560b0dc0e@...gle.com
>>
>> Ah, I see.
>> These are reported separately because the crashes are titled
>> differently. Kernel titled one as "general protection fault" and
>> another as "BUG: unable to handle kernel NULL pointer dereference".
>
> Ahh, OK, so I've missed that part ;) I just thought it was duplicate
> because the report seemed very familiar.


So are these duplicates? If yes, we need to tell this syzbot:

> 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.