Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936936AbdLRRB7 (ORCPT ); Mon, 18 Dec 2017 12:01:59 -0500 Received: from mail-pg0-f65.google.com ([74.125.83.65]:32949 "EHLO mail-pg0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S936791AbdLRRBw (ORCPT ); Mon, 18 Dec 2017 12:01:52 -0500 X-Google-Smtp-Source: ACJfBotl15+bKgfGCA46fX+0AU2FL9e2jsOj4jun5YA+R/Ow7HSCEVNXsXnGMAMnXwrmlJ+mWQBVIXcqC3x6eXgK5kU= MIME-Version: 1.0 In-Reply-To: <6dbd4f85-f3f2-97f3-5b82-451276fbf877@oracle.com> References: <001a113fae28c2fd6605609c97a2@google.com> <6dbd4f85-f3f2-97f3-5b82-451276fbf877@oracle.com> From: Dmitry Vyukov Date: Mon, 18 Dec 2017 18:01:30 +0100 Message-ID: Subject: Re: BUG: spinlock bad magic (2) To: Santosh Shilimkar Cc: syzbot , David Miller , LKML , linux-rdma@vger.kernel.org, netdev , rds-devel@oss.oracle.com, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1186 Lines: 35 On Mon, Dec 18, 2017 at 5:46 PM, Santosh Shilimkar wrote: > On 12/18/2017 4:36 AM, syzbot wrote: >> >> Hello, >> >> syzkaller hit the following crash on >> 6084b576dca2e898f5c101baef151f7bfdbb606d >> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master >> compiler: gcc (GCC) 7.1.1 20170620 >> .config is attached >> Raw console output is attached. >> >> Unfortunately, I don't have any reproducer for this bug yet. >> > [...] > >> BUG: unable to handle kernel NULL pointer dereference at 0000000000000028 >> IP: rds_send_xmit+0x80/0x930 net/rds/send.c:186 > > > This one seems to be same bug as reported as below. > > BUG: unable to handle kernel NULL pointer dereference in rds_send_xmit Hi Santosh, The proper syntax to tell syzbot about dups is this (from email footer): > See https://goo.gl/tpsmEJ for details. > Please credit me with: Reported-by: 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.