netdev - Re: [PATCH 00/16]: Kill the ipv4 routing cache.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 20 Jul 2012 09:26:14 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	bhutchings@...arflare.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH 00/16]: Kill the ipv4 routing cache.

From: Ben Hutchings <bhutchings@...arflare.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.

Every damn set of changes I've commited over the past few weeks have
used this technique, are you simply not paying attention?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html