mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@oracle.com>
To: linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org,
	rds-devel@oss.oracle.com
Subject: Re: general protection fault in __rds_rdma_map
Date: Mon, 27 Nov 2017 12:39:51 -0800	[thread overview]
Message-ID: <b33496ee-b34b-3529-4d2f-1d7f13d09b20@oracle.com> (raw)
In-Reply-To: <001a113f98d6216a60055efb17da@google.com>

On 11/27/2017 10:30 AM, syzbot wrote:
> Hello,
> 
> syzkaller hit the following crash on 
> e1d1ea549b57790a3d8cf6300e6ef86118d692a3
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console output is attached.
> C reproducer is attached
> syzkaller reproducer is attached. See 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__goo.gl_kgGztJ&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=hWpFvp_cTkkwMMULcvbV65orOO9Gv3OUaY0ATWhQwak&m=0pw38xYdDB2QuLTkc6b0N3240iyzMU13jwFZvLaxDSo&s=0kx55ufXFnBORomS71r4MtXomSqMRKhkHI1tGM3oPic&e= 
> 
> for information about syzkaller reproducers
> 
> 
> kasan: GPF could be caused by NULL-ptr deref or user memory access
> general protection fault: 0000 [#1] SMP KASAN
> RDS: rds_bind could not find a transport for 224.0.0.2, load rds_tcp or 
> rds_rdma?

Seems like the RDMA operation got triggered on the non RDMA transport
lead to non populated rs->rs_transport->get_mr(). Also seems like the
tests was running in the namespace and the RDMA transport doesn't
yet support it. Thanks for reporting. Will look into fix internally.

Regards,
Santosh

  reply	other threads:[~2017-11-27 20:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27 18:30 syzbot
2017-11-27 20:39 ` Santosh Shilimkar [this message]
2018-01-30 21:14 ` Eric Biggers

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=b33496ee-b34b-3529-4d2f-1d7f13d09b20@oracle.com \
    --to=santosh.shilimkar@oracle.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®