[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6f6a4be5-99e8-de34-595d-f5b30c61c7ec@oracle.com>
Date: Tue, 18 Dec 2018 15:02:24 -0800
From: Santosh Shilimkar <santosh.shilimkar@...cle.com>
To: David Miller <davem@...emloft.net>, shamir.rabinovitch@...cle.com
Cc: linux-rdma@...r.kernel.org, rds-devel@....oracle.com,
netdev@...r.kernel.org, gerd.rausch@...cle.com,
haakon.bugge@...cle.com
Subject: Re: [PATCH rds linux-next v4 0/2] WARNING in rds_message_alloc_sgs
On 12/18/2018 2:57 PM, David Miller wrote:
> From: Shamir Rabinovitch <shamir.rabinovitch@...cle.com>
> Date: Sun, 16 Dec 2018 09:01:07 +0200
>
>> From: shamir rabinovitch <shamir.rabinovitch@...cle.com>
>>
>> This patch set fix google syzbot rds bug found in linux-next.
>> The first patch solve the syzbot issue.
>> The second patch fix issue mentioned by Leon Romanovsky that
>> drivers should not call WARN_ON as result from user input.
>>
>> syzbot bug report can be foud here: https://lkml.org/lkml/2018/10/31/28
>>
>> v1->v2:
>> - patch 1: make rds_iov_vector fields name more descriptive (Hakon)
>> - patch 1: fix potential mem leak in rds_rm_size if krealloc fail
>> (Hakon)
>> v2->v3:
>> - patch 2: harden rds_sendmsg for invalid number of sgs (Gerd)
>> v3->v4
>> - Santosh a.b. on both patches + repost to net-dev
>
> Does this bug exist in 'net' too? It really should target the 'net'
> tree if so, and then we can queue these fixes up for -stable too.
>
yes, the bug exist in net too.
Shamir, please check if these apply cleanly to Dave's 'net' tree.
Regards,
Santosh
Powered by blists - more mailing lists