From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936158AbdLSNmn (ORCPT ); Tue, 19 Dec 2017 08:42:43 -0500 Received: from mx2.suse.de ([195.135.220.15]:43327 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934436AbdLSNmh (ORCPT ); Tue, 19 Dec 2017 08:42:37 -0500 Date: Tue, 19 Dec 2017 14:42:35 +0100 From: Michal Hocko To: Dmitry Vyukov Cc: syzbot , Andrew Morton , Johannes Weiner , Hillf Danton , LKML , Linux-MM , Mel Gorman , Minchan Kim , shakeelb@google.com, syzkaller-bugs@googlegroups.com, ying.huang@intel.com, syzkaller Subject: Re: BUG: unable to handle kernel NULL pointer dereference in __list_del_entry_valid Message-ID: <20171219134235.GW2787@dhcp22.suse.cz> References: <001a11452568f5857c0560b0dc0e@google.com> <20171219130337.GU2787@dhcp22.suse.cz> <20171219132209.GV2787@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 19-12-17 14:38:35, Dmitry Vyukov wrote: > On Tue, Dec 19, 2017 at 2:22 PM, Michal Hocko wrote: > > On Tue 19-12-17 14:12:38, Dmitry Vyukov wrote: > >> On Tue, Dec 19, 2017 at 2:03 PM, Michal Hocko 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