From: "santosh.shilimkar@oracle.com" <santosh.shilimkar@oracle.com>
To: Eric Biggers <ebiggers3@gmail.com>,
linux-rdma@vger.kernel.org, rds-devel@oss.oracle.com
Cc: syzbot <syzbot+b51c77ef956678a65834@syzkaller.appspotmail.com>,
davem@davemloft.net, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: general protection fault in rds_ib_get_mr
Date: Wed, 4 Jul 2018 17:32:20 -0700 [thread overview]
Message-ID: <04c882dc-332e-92d6-fe76-b1dd3bedd71c@oracle.com> (raw)
In-Reply-To: <20180704213506.GH725@sol.localdomain>
On 7/4/18 2:35 PM, Eric Biggers wrote:
> On Sun, May 13, 2018 at 10:46:37PM -0700, santosh.shilimkar@oracle.com wrote:
>> On 5/13/18 2:10 PM, Eric Biggers wrote:
>>> On Wed, Mar 21, 2018 at 09:00:01AM -0700, syzbot wrote:
>>
>> [...]
>>
>>
>>> Still reproducible on Linus' tree (commit 66e1c94db3cd4) and linux-next
>>> (next-20180511). Here's a simplified reproducer:
>>>
>> Thanks for the test case !!
>>
[...]
>
> Ping; this RDS bug is still unfixed. The same reproducer I gave earlier still
> works, even when run as a non-root user. I tested upstream commit
> fc36def997cfd6 (v4.18-rc3-113-gfc36def997cfd), and linux-next commit
> bce40927669338 (next-20180704).
>
Yeah I haven't sent a fix for this yet. Downstream we have refactored
MR code and I wanted to get that upstream. With that this bug will
also get addressed. I was hoping to get that series but since some
optimisation is still pending investigations its getting delayed.
Will find out if I can fix this panic in meantime with smaller change.
Thanks for reminder.
Regards,
Santosh
next prev parent reply other threads:[~2018-07-05 0:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 16:00 general protection fault in rds_ib_get_mr syzbot
2018-05-13 21:10 ` Eric Biggers
2018-05-14 5:46 ` santosh.shilimkar
2018-07-04 21:35 ` Eric Biggers
2018-07-05 0:32 ` santosh.shilimkar [this message]
2018-07-05 7:06 ` Johannes Thumshirn
2018-07-05 16:09 ` Santosh Shilimkar
2018-07-06 8:11 ` Johannes Thumshirn
2018-07-25 3:58 ` santosh.shilimkar
2018-07-26 11:40 ` Johannes Thumshirn
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=04c882dc-332e-92d6-fe76-b1dd3bedd71c@oracle.com \
--to=santosh.shilimkar@oracle.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=syzbot+b51c77ef956678a65834@syzkaller.appspotmail.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).