From: Eric Biggers <ebiggers3@gmail.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Santosh Shilimkar <santosh.shilimkar@oracle.com>,
syzbot
<bot+d3f5d339869eb8cd834d2c9f0a88bf4f05c29781@syzkaller.appspotmail.com>,
David Miller <davem@davemloft.net>,
LKML <linux-kernel@vger.kernel.org>,
linux-rdma@vger.kernel.org, netdev <netdev@vger.kernel.org>,
rds-devel@oss.oracle.com, syzkaller-bugs@googlegroups.com
Subject: Re: BUG: spinlock bad magic (2)
Date: Tue, 30 Jan 2018 14:28:11 -0800 [thread overview]
Message-ID: <20180130222811.yxfiqnlx3la3vyyw@gmail.com> (raw)
In-Reply-To: <CACT4Y+Zoat=3j7B--D=pLK=SU0zhNA2yw0O0cEwj_p6vSBfM7g@mail.gmail.com>
On Mon, Dec 18, 2017 at 06:01:30PM +0100, 'Dmitry Vyukov' via syzkaller-bugs wrote:
> On Mon, Dec 18, 2017 at 5:46 PM, Santosh Shilimkar
> <santosh.shilimkar@oracle.com> 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 <syzkaller@googlegroups.com>
> > 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.
#syz dup: BUG: unable to handle kernel NULL pointer dereference in rds_send_xmit
next prev parent reply other threads:[~2018-01-30 22:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001a113fae28c2fd6605609c97a2@google.com>
2017-12-18 16:46 ` Santosh Shilimkar
2017-12-18 17:01 ` Dmitry Vyukov
2018-01-30 22:28 ` Eric Biggers [this message]
2018-01-31 3:49 ` santosh.shilimkar
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=20180130222811.yxfiqnlx3la3vyyw@gmail.com \
--to=ebiggers3@gmail.com \
--cc=bot+d3f5d339869eb8cd834d2c9f0a88bf4f05c29781@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=santosh.shilimkar@oracle.com \
--cc=syzkaller-bugs@googlegroups.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
all inboxes | Powered by JetHome®