From: David Miller <davem@davemloft.net>
To: Jason@zx2c4.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
David.Laight@aculab.com, kernel-hardening@lists.openwall.com
Subject: Re: [PATCH 1/5] skbuff: return -EMSGSIZE in skb_to_sgvec to prevent overflow
Date: Tue, 25 Apr 2017 10:47:31 -0400 (EDT) [thread overview]
Message-ID: <20170425.104731.631398016575024152.davem@davemloft.net> (raw)
In-Reply-To: <20170425140809.23881-1-Jason@zx2c4.com>
From: "Jason A. Donenfeld" <Jason@zx2c4.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@zx2c4.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.
next prev parent reply other threads:[~2017-04-25 14:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 14:08 [PATCH 1/5] skbuff: return -EMSGSIZE in skb_to_sgvec to prevent overflow Jason A. Donenfeld
2017-04-25 14:08 ` [PATCH 2/5] ipsec: check return value of skb_to_sgvec always Jason A. Donenfeld
2017-04-25 14:08 ` [PATCH 3/5] rxrpc: " Jason A. Donenfeld
2017-04-25 14:08 ` [PATCH 4/5] macsec: " Jason A. Donenfeld
2017-04-25 14:08 ` [PATCH 5/5] virtio_net: " Jason A. Donenfeld
2017-04-25 14:16 ` [PATCH v2 1/5] skbuff: return -EMSGSIZE in skb_to_sgvec to prevent overflow Jason A. Donenfeld
2017-04-25 14:21 ` [PATCH v3 " Jason A. Donenfeld
2017-04-25 14:47 ` David Miller [this message]
2017-04-25 15:04 ` [PATCH v4 " Jason A. Donenfeld
2017-04-25 15:17 ` David Miller
2017-04-25 15:52 ` [PATCH v5 " Jason A. Donenfeld
2017-04-25 15:52 ` [PATCH v5 2/5] ipsec: check return value of skb_to_sgvec always Jason A. Donenfeld
2017-04-25 15:52 ` [PATCH v5 3/5] rxrpc: " Jason A. Donenfeld
2017-04-25 15:52 ` [PATCH v5 4/5] macsec: " Jason A. Donenfeld
2017-04-25 15:52 ` [PATCH v5 5/5] virtio_net: " Jason A. Donenfeld
2017-04-25 18:47 ` [PATCH v6 1/5] skbuff: return -EMSGSIZE in skb_to_sgvec to prevent overflow Jason A. Donenfeld
2017-04-25 18:47 ` [PATCH v6 2/5] ipsec: check return value of skb_to_sgvec always Jason A. Donenfeld
2017-04-25 18:47 ` [PATCH v6 3/5] rxrpc: " Jason A. Donenfeld
2017-04-28 11:41 ` Sabrina Dubroca
2017-04-28 13:29 ` Jason A. Donenfeld
2017-04-25 18:47 ` [PATCH v6 4/5] macsec: " Jason A. Donenfeld
2017-04-25 18:47 ` [PATCH v6 5/5] virtio_net: " Jason A. Donenfeld
2017-04-27 9:21 ` [PATCH v6 1/5] skbuff: return -EMSGSIZE in skb_to_sgvec to prevent overflow Jason A. Donenfeld
2017-04-27 11:30 ` Sabrina Dubroca
2017-04-27 12:04 ` Jason A. Donenfeld
2017-04-27 14:54 ` David Laight
2017-04-27 15:54 ` David Miller
2017-04-28 16:18 ` Sabrina Dubroca
2017-04-28 22:47 ` Jason A. Donenfeld
2017-04-25 15:42 ` [PATCH " Sergei Shtylyov
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=20170425.104731.631398016575024152.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=David.Laight@aculab.com \
--cc=Jason@zx2c4.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).