netdev - Re: ip_gre headroom allocation

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: <20090611.030922.91415233.davem@davemloft.net>
Date:	Thu, 11 Jun 2009 03:09:22 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	timo.teras@....fi
Cc:	netdev@...r.kernel.org, herbert@...dor.apana.org.au,
	kuznet@....inr.ac.ru
Subject: Re: ip_gre headroom allocation

From: Timo Teräs <timo.teras@....fi>
Date: Thu, 11 Jun 2009 11:22:34 +0300

> I'm not entirely sure about this, but shouldn't we do something like
> the below to make ip_gre allocation enough headroom for paths where
> e.g. xfrm transformations take place (as a speed optimization)?

This should be handled by the code one level up that allocates
the SKB.

And as routes get stacked, the MTUs and headroom values get adjusted
up to the root.

At least that's how it's supposed to work :-)

Otherwise we'd need a similar hack in ipip.c too.
--
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