netdev - Re: ppp_deflate + kmalloc

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, 24 Jun 2011 10:02:40 -0400
From:	James Carlson <carlsonj@...kingcode.com>
To:	Martin Jackson <mjackson220.list@...il.com>
CC:	paulus@...ba.org, linux-ppp@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: ppp_deflate + kmalloc

Martin Jackson wrote:
> In our android froyo-based system (omap3 hardware), we are getting the
> following problem where the ppp driver cannot kmalloc enough memory
> for the decomp buffer in the ppp driver.
> 
> Trying to make a 4th-order kmalloc (I think that amounts to 64kB)
> seems ambitious. I do not understand why vmalloc is not being used
> here, like it is for the compression buffer. Is using vmalloc here an
> acceptable solution?

The code here shouldn't need contiguous pages, so vmalloc (even if
"slower") shouldn't be a problem.

But a higher-level question might be why you're bothering with RFC 1979
Deflate compression at all on this platform.  I'd expect that you're
most likely going to end up talking to commercially-produced PPP servers
(possibly 3GPP or similar) at the other end, and very, very few of them
offer data compression with either RFC 1977 (BSD Compression) or RFC
1979.  ("Very, very few" is probably being generous ...)

If it's always going to be negotiated away in practice, and if you're
having trouble with memory constraints, why not just ditch the baggage?

-- 
James Carlson         42.703N 71.076W         <carlsonj@...kingcode.com>
--
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