From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: bhutchings@solarflare.com, netdev@vger.kernel.org
Subject: Re: [PATCH 00/16]: Kill the ipv4 routing cache.
Date: Fri, 20 Jul 2012 18:43:54 +0200 [thread overview]
Message-ID: <1342802634.2626.7718.camel@edumazet-glaptop> (raw)
In-Reply-To: <20120720.092614.1285553995467252576.davem@davemloft.net>
On Fri, 2012-07-20 at 09:26 -0700, David Miller wrote:
> From: Ben Hutchings <bhutchings@solarflare.com>
> Date: Fri, 20 Jul 2012 16:09:29 +0100
>
> > On Thu, 2012-07-19 at 14:34 -0700, David Miller wrote:
> >> The ipv4 routing cache is non-deterministic, performance wise, and is
> >> subject to reasonably easy to launch denial of service attacks.
> > [...]
> >
> > This is a great explanation, but it still doesn't appear to be going
> > into the commit log...
>
> What in the world do you mean?
>
> When I actually commit this stuff, I'll have it all in a branch and
> merge it into net-next's master using "git merge --no-ff" and then use
> the merge commit to add this commit message test.
I am not familiar with this "git merge --no-ff", so the following
might be completely irrelevant :
It would be nice if you can copy the changelog of 00/16 to 01/16
01/16 has no changelog, and it probably can confuse git users in the
future, since this patch is not trivial.
next prev parent reply other threads:[~2012-07-20 16:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 21:34 [PATCH 00/16]: Kill the ipv4 routing cache David Miller
2012-07-20 15:09 ` Ben Hutchings
2012-07-20 16:26 ` David Miller
2012-07-20 16:43 ` Eric Dumazet [this message]
2012-07-20 17:42 ` David Miller
2012-07-20 17:22 ` Ben Hutchings
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=1342802634.2626.7718.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--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