From: David Miller <davem@davemloft.net>
To: shamir.rabinovitch@oracle.com
Cc: linux-rdma@vger.kernel.org, rds-devel@oss.oracle.com,
netdev@vger.kernel.org, gerd.rausch@oracle.com,
santosh.shilimkar@oracle.com, haakon.bugge@oracle.com
Subject: Re: [PATCH rds linux-next v4 0/2] WARNING in rds_message_alloc_sgs
Date: Tue, 18 Dec 2018 14:57:53 -0800 (PST) [thread overview]
Message-ID: <20181218.145753.1550590342570044648.davem@davemloft.net> (raw)
In-Reply-To: <20181216070109.6758-1-shamir.rabinovitch@oracle.com>
From: Shamir Rabinovitch <shamir.rabinovitch@oracle.com>
Date: Sun, 16 Dec 2018 09:01:07 +0200
> From: shamir rabinovitch <shamir.rabinovitch@oracle.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.
next prev parent reply other threads:[~2018-12-18 22:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-16 7:01 [PATCH rds linux-next v4 0/2] WARNING in rds_message_alloc_sgs Shamir Rabinovitch
2018-12-16 7:01 ` [PATCH rds linux-next v4 1/2] net/rds: fix warn " Shamir Rabinovitch
2018-12-16 7:01 ` [PATCH rds linux-next v4 2/2] net/rds: remove user triggered WARN_ON in rds_sendmsg Shamir Rabinovitch
2018-12-18 22:57 ` David Miller [this message]
2018-12-18 23:02 ` [PATCH rds linux-next v4 0/2] WARNING in rds_message_alloc_sgs Santosh Shilimkar
2018-12-19 10:54 ` Shamir Rabinovitch
2018-12-19 18:00 ` Santosh Shilimkar
2018-12-19 18:22 ` David Miller
2018-12-19 18:26 ` Santosh Shilimkar
2018-12-19 18:30 ` David Miller
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=20181218.145753.1550590342570044648.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gerd.rausch@oracle.com \
--cc=haakon.bugge@oracle.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=santosh.shilimkar@oracle.com \
--cc=shamir.rabinovitch@oracle.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).