linux-kernel - Re: [ 150/184] ipv4: check rt_genid in dst

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]

Message-ID: <20130607150057.GF19006@1wt.eu>
Date:	Fri, 7 Jun 2013 17:00:57 +0200
From:	Willy Tarreau <w@....eu>
To:	Benjamin LaHaise <bcrl@...ck.org>
Cc:	Ben Hutchings <ben@...adent.org.uk>, linux-kernel@...r.kernel.org,
	stable@...r.kernel.org,
	Timo Teräs <timo.teras@....fi>
Subject: Re: [ 150/184] ipv4: check rt_genid in dst_check

On Fri, Jun 07, 2013 at 10:58:06AM -0400, Benjamin LaHaise wrote:
> On Fri, Jun 07, 2013 at 07:07:33AM +0100, Ben Hutchings wrote:
> > > This commit is based on the above, with the addition of verifying blackhole
> > > routes in the same manner.
> > 
> > That addition doesn't seem to correspond to anything in mainline.  Why
> > should 2.6.32 differ?
> 
> Fixing the issue with blackhole routes as it was accomplished in mainline 
> would require pulling in a lot more code, and people were not interested 
> in pulling in all of the dependencies given the much higher risk of trying 
> to select the right subset of changes to include.  The addition of the 
> single line of "dst->obsolete = -1;" in ipv4_dst_blackhole() was much 
> easier to verify, and is in the spirit of the patch in question.  This is 
> the minimal set of changes to fix the bug in question.

Thank you Ben, I'll add this description to the existing commit message.

Best regards,
Willy

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/