[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACT4Y+aqFuVToOQH8RnfahhonaQ=qvq5JTvL-9aAKBQAa7UOug@mail.gmail.com>
Date: Tue, 19 Dec 2017 14:38:35 +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>,
Hillf Danton <hillf.zj@...baba-inc.com>,
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:22 PM, Michal Hocko <mhocko@...nel.org> wrote:
> On Tue 19-12-17 14:12:38, Dmitry Vyukov wrote:
>> On Tue, Dec 19, 2017 at 2:03 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".
What algorithm do you propose to use to merge them?
Powered by blists - more mailing lists