netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: kangjielu@gmail.com
Cc: sfeldma@gmail.com, roopa@cumulusnetworks.com, jiri@mellanox.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	taesoo@gatech.edu, insu@gatech.edu, kjlu@gatech.edu
Subject: Re: [PATCH] fix infoleak in rtnetlink
Date: Wed, 04 May 2016 16:20:06 -0400 (EDT)	[thread overview]
Message-ID: <20160504.162006.1942398564535378585.davem@davemloft.net> (raw)
In-Reply-To: <1462308384-6315-1-git-send-email-kjlu@gatech.edu>

From: Kangjie Lu <kangjielu@gmail.com>
Date: Tue,  3 May 2016 16:46:24 -0400

> The stack object “map” has a total size of 32 bytes. Its last 4
> bytes are padding generated by compiler. These padding bytes are
> not initialized and sent out via “nla_put”.
> 
> Signed-off-by: Kangjie Lu <kjlu@gatech.edu>

Applied.

      reply	other threads:[~2016-05-04 20:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-03 20:46 [PATCH] fix infoleak in rtnetlink Kangjie Lu
2016-05-04 20:20 ` David Miller [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=20160504.162006.1942398564535378585.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=insu@gatech.edu \
    --cc=jiri@mellanox.com \
    --cc=kangjielu@gmail.com \
    --cc=kjlu@gatech.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=roopa@cumulusnetworks.com \
    --cc=sfeldma@gmail.com \
    --cc=taesoo@gatech.edu \
    /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).