From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: David Miller <davem@davemloft.net>,
santosh.shilimkar@oracle.com, rds-devel@oss.oracle.com,
bot+aaf54a8c644d559d34dedcf3126aac68a20c9e63@syzkaller.appspotmail.com,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [rds-devel] BUG: unable to handle kernel NULL pointer dereference in rds_send_xmit
Date: Tue, 30 Jan 2018 17:28:16 -0500 [thread overview]
Message-ID: <20180130222816.GU22848@oracle.com> (raw)
In-Reply-To: <20180130222228.q23csjr5l666v3o5@gmail.com>
On (01/30/18 14:22), Eric Biggers wrote:
>
> I assume you weren't able to reproduce this? This crash hasn't been
> seen again,
:
> I am invalidating the bug for syzbot so it will report the same crash
> signature
> again if it occurs, but if you think there is a real bug feel free to keep
> looking into it.
correct I was not able to reproduce this. However based on code
inspecion, I came up with
commit 3db6e0d172c94bd9953a1347c55ffb64b1d2e74f
rds: use RCU to synchronize work-enqueue with connection teardown
Marking it invalid sounds good to me.
--Sowmini
prev parent reply other threads:[~2018-01-30 22:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 8:43 BUG: unable to handle kernel NULL pointer dereference in rds_send_xmit syzbot
2017-12-18 13:55 ` Sowmini Varadhan
[not found] ` <001a1145ac5480242305609956b3-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2017-12-18 16:28 ` Santosh Shilimkar
2017-12-18 16:28 ` Santosh Shilimkar
2017-12-18 17:12 ` David Miller
[not found] ` <20171218.121213.289437104214632276.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2017-12-18 17:16 ` Santosh Shilimkar
2017-12-18 17:16 ` Santosh Shilimkar
2017-12-18 17:22 ` [rds-devel] " Sowmini Varadhan
2018-01-30 22:22 ` Eric Biggers
2018-01-30 22:28 ` Sowmini Varadhan [this message]
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=20180130222816.GU22848@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=bot+aaf54a8c644d559d34dedcf3126aac68a20c9e63@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=ebiggers3@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.