From: Ka-Cheong Poon <ka-cheong.poon@oracle.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, santosh.shilimkar@oracle.com,
rds-devel@oss.oracle.com
Subject: Re: [PATCH net-next] net/rds: Fix info leak in rds6_inc_info_copy()
Date: Tue, 27 Aug 2019 11:18:50 +0800 [thread overview]
Message-ID: <7bed2cb9-0e26-f64e-5c4e-6e656f143c78@oracle.com> (raw)
In-Reply-To: <20190824.142047.32032287178584562.davem@davemloft.net>
On 8/25/19 5:20 AM, David Miller wrote:
> From: Ka-Cheong Poon <ka-cheong.poon@oracle.com>
> Date: Wed, 21 Aug 2019 20:18:24 -0700
>
>> The rds6_inc_info_copy() function has a couple struct members which
>> are leaking stack information. The ->tos field should hold actual
>> information and the ->flags field needs to be zeroed out.
>>
>> Fixes: 3eb450367d08 ("rds: add type of service(tos) infrastructure")
>> Fixes: b7ff8b1036f0 ("rds: Extend RDS API for IPv6 support")
>> Reported-by: 黄ID蝴蝶 <butterflyhuangxx@gmail.com>
>> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>> Signed-off-by: Ka-Cheong Poon <ka-cheong.poon@oracle.com>
>
> Why would an info leak bug fix, present in current kernels, be targetted
> at 'net-next' instead of 'net'?
>
> Please retarget this at 'net' properly, thank you.
Retarget patch sent. Thanks.
--
K. Poon
ka-cheong.poon@oracle.com
prev parent reply other threads:[~2019-08-27 3:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 3:18 [PATCH net-next] net/rds: Fix info leak in rds6_inc_info_copy() Ka-Cheong Poon
2019-08-23 6:32 ` santosh.shilimkar
2019-08-24 21:20 ` David Miller
2019-08-27 3:18 ` Ka-Cheong Poon [this message]
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=7bed2cb9-0e26-f64e-5c4e-6e656f143c78@oracle.com \
--to=ka-cheong.poon@oracle.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=santosh.shilimkar@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).