From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: syzbot
<bot+aaf54a8c644d559d34dedcf3126aac68a20c9e63@syzkaller.appspotmail.com>
Cc: netdev@vger.kernel.org, rds-devel@oss.oracle.com,
syzkaller-bugs@googlegroups.com
Subject: Re: BUG: unable to handle kernel NULL pointer dereference in rds_send_xmit
Date: Mon, 18 Dec 2017 08:55:24 -0500 [thread overview]
Message-ID: <20171218135524.GA26203@oracle.com> (raw)
In-Reply-To: <001a1145ac5480242305609956b3@google.com>
On (12/18/17 00:43), syzbot wrote:
> BUG: unable to handle kernel NULL pointer dereference at 0000000000000028
> program syz-executor6 is using a deprecated SCSI ioctl, please convert it to
> SG_IO
> IP: rds_send_xmit+0x80/0x930 net/rds/send.c:186
conn->c_trans is at offset 0x28.
Both this and https://marc.info/?l=linux-netdev&m=151360062922798&w=2
are manifestations of the same bug: somehow the cp_send_w is still
getting queued incorrectly after the conn destroy is initiated (commit
681648e67d fixes one such window, maybe there are others).
Let me look at how this slipped through the cracks.
--Sowmini
next prev parent reply other threads:[~2017-12-18 13:55 UTC|newest]
Thread overview: 8+ 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 [this message]
[not found] ` <001a1145ac5480242305609956b3-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
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:22 ` [rds-devel] " Sowmini Varadhan
2018-01-30 22:22 ` Eric Biggers
2018-01-30 22:28 ` Sowmini Varadhan
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=20171218135524.GA26203@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=bot+aaf54a8c644d559d34dedcf3126aac68a20c9e63@syzkaller.appspotmail.com \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.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;
as well as URLs for NNTP newsgroup(s).