From: Eric Dumazet <erdnetdev@gmail.com>
To: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH] ndisc: Ensure to reserve header space for encapsulation.
Date: Wed, 26 Dec 2012 11:21:33 -0800 [thread overview]
Message-ID: <1356549693.20133.20875.camel@edumazet-glaptop> (raw)
In-Reply-To: <50DB4B3D.2050800@linux-ipv6.org>
On Thu, 2012-12-27 at 04:08 +0900, YOSHIFUJI Hideaki wrote:
> Current code does not make sense, at least.
>
> Please refer to my previous posting: "[GIT PULL net-next 01/17]
> ndisc: Fix size calculation for headers." around Dec/19.
>
> My previous patch did remove MAX_HEADER from allocation.
Yes, but the changelog was misleading, and David misunderstood it.
If you really explain why its safe to remove MAX_HEADER, I think
your patch would make sense.
prev parent reply other threads:[~2012-12-26 19:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-25 14:39 [PATCH] ndisc: Ensure to reserve header space for encapsulation YOSHIFUJI Hideaki
2012-12-26 16:48 ` Eric Dumazet
2012-12-26 19:08 ` YOSHIFUJI Hideaki
2012-12-26 19:21 ` Eric Dumazet [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=1356549693.20133.20875.camel@edumazet-glaptop \
--to=erdnetdev@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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