[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <04c882dc-332e-92d6-fe76-b1dd3bedd71c@oracle.com>
Date: Wed, 4 Jul 2018 17:32:20 -0700
From: "santosh.shilimkar@...cle.com" <santosh.shilimkar@...cle.com>
To: Eric Biggers <ebiggers3@...il.com>, linux-rdma@...r.kernel.org,
rds-devel@....oracle.com
Cc: syzbot <syzbot+b51c77ef956678a65834@...kaller.appspotmail.com>,
davem@...emloft.net, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: Re: general protection fault in rds_ib_get_mr
On 7/4/18 2:35 PM, Eric Biggers wrote:
> On Sun, May 13, 2018 at 10:46:37PM -0700, santosh.shilimkar@...cle.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
Powered by blists - more mailing lists