linux-kernel - Re: kernel BUGs when removing largish files with the SLOB allocator

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: <17162.1157365295@warthog.cambridge.redhat.com>
Date:	Mon, 04 Sep 2006 11:21:35 +0100
From:	David Howells <dhowells@...hat.com>
To:	Aubrey <aubreylee@...il.com>
Cc:	linux-kernel@...r.kernel.org, mpm@...enic.com, dhowells@...hat.com,
	davidm@...pgear.com, gerg@...pgear.com
Subject: Re: kernel BUGs when removing largish files with the SLOB allocator 

Aubrey <aubreylee@...il.com> wrote:

> Is there any solution/patch to fix the issue?

Make the SLOB allocator mark its pages PG_slab, just like the SLAB allocator
does.  I think this should be okay as the SLOB allocator and the SLAB
allocator seem to be mutually exclusive.

Using PG_slab would also give an instant check to things like SLOB's kfree().

> +#ifdef CONFIG_SLAB
>        if (PageSlab(page))
> +#endif

This is not a valid workaround as the object won't necessarily have been
allocated from a slab (shared ramfs mappings and SYSV SHM for example).  You
may not pass to ksize() objects allocated by means other than SLAB/SLOB.

David

-- 
VGER BF report: H 1.12398e-05
-
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/