From: Ben Hutchings <ben@decadent.org.uk>
To: Jiri Slaby <jslaby@suse.cz>, Michal Kubecek <mkubecek@suse.cz>,
stable@vger.kernel.org
Cc: Sabrina Dubroca <sd@queasysnail.net>, netdev@vger.kernel.org
Subject: Re: [PATCH stable-3.2 stable-3.12] net: fix checksum check in skb_copy_and_csum_datagram_iovec()
Date: Tue, 05 Jan 2016 16:40:08 +0000 [thread overview]
Message-ID: <1452012008.2768.82.camel@decadent.org.uk> (raw)
In-Reply-To: <568BF0FD.4010208@suse.cz>
[-- Attachment #1: Type: text/plain, Size: 616 bytes --]
On Tue, 2016-01-05 at 17:36 +0100, Jiri Slaby wrote:
> On 12/28/2015, 03:01 PM, Michal Kubecek wrote:
> > Recent fix "net: add length argument to
> > skb_copy_and_csum_datagram_iovec" added to some pre-3.19 stable
> > branches, namely
> >
> > stable-3.2.y: commit 127500d724f8
> > stable-3.12.y: commit 3e1ac3aafbd0
>
> Applied this fix to 3.12. Thanks!
[...]
You don't want this, you want Eric's fix (commit 197c949e7, "udp:
properly support MSG_PEEK with truncated buffers") although that's not
upstream yet.
Ben.
--
Ben Hutchings
Tomorrow will be cancelled due to lack of interest.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2016-01-05 16:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 14:01 [PATCH stable-3.2 stable-3.12] net: fix checksum check in skb_copy_and_csum_datagram_iovec() Michal Kubecek
2015-12-28 14:29 ` Sabrina Dubroca
2015-12-28 15:38 ` Michal Kubecek
2015-12-28 17:10 ` Eric Dumazet
2015-12-30 13:51 ` [PATCH net-next] udp: properly support MSG_PEEK with truncated buffers Eric Dumazet
2015-12-30 22:39 ` Herbert Xu
2016-01-04 22:25 ` David Miller
2016-01-05 16:36 ` [PATCH stable-3.2 stable-3.12] net: fix checksum check in skb_copy_and_csum_datagram_iovec() Jiri Slaby
2016-01-05 16:40 ` Ben Hutchings [this message]
2016-01-05 16:41 ` Jiri Slaby
2016-01-13 11:02 ` Ben Hutchings
2016-01-13 14:51 ` Eric Dumazet
2016-01-15 18:16 ` Luis Henriques
2016-01-15 18:16 ` Luis Henriques
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=1452012008.2768.82.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=jslaby@suse.cz \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.