lkml.org 
[lkml]   [2017]   [Dec]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: BUG: unable to handle kernel NULL pointer dereference in __list_del_entry_valid
On Tue 19-12-17 14:38:35, Dmitry Vyukov wrote:
> On Tue, Dec 19, 2017 at 2:22 PM, Michal Hocko <mhocko@kernel.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@kernel.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@google.com
> > while this one has 001a11452568f5857c0560b0dc0e@google.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.

> What algorithm do you propose to use to merge them?

Maybe based on the stack trace?
--
Michal Hocko
SUSE Labs

\
 
 \ /
  Last update: 2017-12-19 14:43    [W:0.110 / U:1.884 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site