[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 25 Apr 2017 10:47:31 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: Jason@...c4.com
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
David.Laight@...lab.com, kernel-hardening@...ts.openwall.com
Subject: Re: [PATCH 1/5] skbuff: return -EMSGSIZE in skb_to_sgvec to
prevent overflow
From: "Jason A. Donenfeld" <Jason@...c4.com>
Date: Tue, 25 Apr 2017 16:08:05 +0200
> This is a defense-in-depth measure in response to bugs like
> 4d6fa57b4dab0d77f4d8e9d9c73d1e63f6fe8fee.
>
> Signed-off-by: Jason A. Donenfeld <Jason@...c4.com>
Please refer to commits in the form:
$(SHA1_ID) ("Commit header line.")
That is, 12 bytes of SHA1_ID followed by the commit header line text
in both double quotes and parenthesis, like this:
4d6fa57b4dab ("macsec: avoid heap overflow in skb_to_sgvec")
Otherwise when changes get backported or applied to different trees,
they have different SHA1_ID values. The commit header text removes
any and all ambiguity.
Thank you.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
