[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20181218.145753.1550590342570044648.davem@davemloft.net>
Date: Tue, 18 Dec 2018 14:57:53 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: shamir.rabinovitch@...cle.com
Cc: linux-rdma@...r.kernel.org, rds-devel@....oracle.com,
netdev@...r.kernel.org, gerd.rausch@...cle.com,
santosh.shilimkar@...cle.com, haakon.bugge@...cle.com
Subject: Re: [PATCH rds linux-next v4 0/2] WARNING in rds_message_alloc_sgs
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.
Thank you.
Powered by blists - more mailing lists