From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: joe@ovn.org, netdev@vger.kernel.org, fw@strlen.de,
hannes@stressinduktion.org, pshelar@ovn.org
Subject: Re: [PATCH net] ipv4: early demux should be aware of fragments
Date: Fri, 29 Jan 2016 12:24:37 -0800 (PST) [thread overview]
Message-ID: <20160129.122437.2258453843319826058.davem@davemloft.net> (raw)
In-Reply-To: <1454080926.7627.49.camel@edumazet-glaptop2.roam.corp.google.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Fri, 29 Jan 2016 07:22:06 -0800
> On Wed, 2016-01-27 at 17:02 -0500, David Miller wrote:
>> From: Eric Dumazet <eric.dumazet@gmail.com>
>> Date: Tue, 26 Jan 2016 16:59:42 -0800
>>
>> > From: Eric Dumazet <edumazet@google.com>
>> >
>> > We should not assume a valid protocol header is present,
>> > as this is not the case for IPv4 fragments.
>> >
>> > Lets avoid extra cache line misses and potential bugs
>> > if we actually find a socket and incorrectly uses its dst.
>> >
>> > Signed-off-by: Eric Dumazet <edumazet@google.com>
>>
>> Applied, thanks.
>
> David, I do not see this patch in net tree ?
This should be fixed now, thanks for letting me know.
next prev parent reply other threads:[~2016-01-29 20:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 23:49 [PATCH net] inet: frag: Always orphan skbs inside ip_defrag() Joe Stringer
2016-01-23 1:22 ` Eric Dumazet
2016-01-26 1:11 ` Joe Stringer
2016-01-26 5:58 ` Eric Dumazet
2016-01-27 0:59 ` [PATCH net] ipv4: early demux should be aware of fragments Eric Dumazet
2016-01-27 22:02 ` David Miller
2016-01-29 15:22 ` Eric Dumazet
2016-01-29 20:24 ` David Miller [this message]
2016-01-29 20:57 ` Eric Dumazet
2016-01-27 2:16 ` [PATCH net] inet: frag: Always orphan skbs inside ip_defrag() Joe Stringer
2016-01-29 0:02 ` David Miller
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=20160129.122437.2258453843319826058.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=fw@strlen.de \
--cc=hannes@stressinduktion.org \
--cc=joe@ovn.org \
--cc=netdev@vger.kernel.org \
--cc=pshelar@ovn.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).