linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot
	<bot+83f46cd25e266359cd056c91f6ecd20b04eddf42@syzkaller.appspotmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Hillf Danton <hillf.zj@alibaba-inc.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux-MM <linux-mm@kvack.org>,
	Mel Gorman <mgorman@techsingularity.net>,
	Minchan Kim <minchan@kernel.org>,
	shakeelb@google.com, syzkaller-bugs@googlegroups.com,
	ying.huang@intel.com, syzkaller <syzkaller@googlegroups.com>
Subject: Re: BUG: unable to handle kernel NULL pointer dereference in __list_del_entry_valid
Date: Tue, 19 Dec 2017 14:42:35 +0100	[thread overview]
Message-ID: <20171219134235.GW2787@dhcp22.suse.cz> (raw)
In-Reply-To: <CACT4Y+aqFuVToOQH8RnfahhonaQ=qvq5JTvL-9aAKBQAa7UOug@mail.gmail.com>

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

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2017-12-19 13:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19 12:47 syzbot
2017-12-19 13:03 ` Michal Hocko
2017-12-19 13:12   ` Dmitry Vyukov
2017-12-19 13:22     ` Michal Hocko
2017-12-19 13:38       ` Dmitry Vyukov
2017-12-19 13:42         ` Michal Hocko [this message]
2017-12-19 13:54           ` Dmitry Vyukov
2017-12-19 16:40           ` Dmitry Vyukov
2017-12-20  9:20             ` Michal Hocko
2017-12-20  9:24               ` Dmitry Vyukov
2017-12-20 10:00                 ` Michal Hocko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171219134235.GW2787@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bot+83f46cd25e266359cd056c91f6ecd20b04eddf42@syzkaller.appspotmail.com \
    --cc=dvyukov@google.com \
    --cc=hannes@cmpxchg.org \
    --cc=hillf.zj@alibaba-inc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=minchan@kernel.org \
    --cc=shakeelb@google.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=syzkaller@googlegroups.com \
    --cc=ying.huang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox