linux-kernel - Re: + inflate-refactor-inflate-malloc-code.patch added to -mm tree

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] [day] [month] [year] [list]

Message-ID: <13565.1205333251@redhat.com>
Date:	Wed, 12 Mar 2008 14:47:31 +0000
From:	David Howells <dhowells@...hat.com>
To:	Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>
Cc:	dhowells@...hat.com, Russell King <rmk@....linux.org.uk>,
	akpm@...ux-foundation.org, mm-commits@...r.kernel.org,
	hpa@...or.com, ink@...assic.park.msu.ru, kkojima@...iij4u.or.jp,
	lethal@...ux-sh.org, mingo@...e.hu, mpm@...enic.com, rc@....org.uk,
	rth@...ddle.net, starvik@...s.com, takata@...ux-m32r.org,
	tglx@...utronix.de, ysato@...rs.sourceforge.jp,
	Byron Bradley <byron.bbradley@...il.com>,
	linux-kernel@...r.kernel.org, michael@...e-electrons.com
Subject: Re: + inflate-refactor-inflate-malloc-code.patch added to -mm tree

Thomas Petazzoni <thomas.petazzoni@...e-electrons.com> wrote:

> inflate: refactor inflate malloc code
> 
> Inflate requires some dynamic memory allocation very early in the boot
> process and this is provided with a set of four functions:
> malloc/free/gzip_mark/gzip_release.
> 
> The old inflate code used a mark/release strategy rather than
> implement free. This new version instead keeps a count on the number
> of outstanding allocations and when it hits zero, it resets the malloc
> arena.
> 
> This allows removing all the mark and release implementations and
> unifying all the malloc/free implementations.
> 
> The architecture-dependent code must define two addresses:
>  - free_mem_ptr, the address of the beginning of the area in which
>    allocations should be made
>  - free_mem_end_ptr, the address of the end of the area in which
>    allocations should be made. If set to 0, then no check is made on
>    the number of allocations, it just grows as much as needed
> 
> The architecture-dependent code can also provide an arch_decomp_wdog()
> function call. This function will be called several times during the
> decompression process, and allow to notify the watchdog that the
> system is still running. If an architecture provides such a call, then
> it must define ARCH_HAS_DECOMP_WDOG so that the generic inflate code
> calls arch_decomp_wdog().
> 
> Work initially done by Matt Mackall <mpm@...enic.com>, updated to a
> recent version of the kernel by me.
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>

Works on MN10300.

Acked-by: David Howells <dhowells@...hat.com>
--
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/