linux-kernel - Re: [patch] SLQB v2

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: <Pine.LNX.4.64.0805011825420.13697@schroedinger.engr.sgi.com>
Date:	Thu, 1 May 2008 18:28:57 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Nick Piggin <npiggin@...e.de>
cc:	"Ahmed S. Darwish" <darwish.07@...il.com>,
	Linux Memory Management List <linux-mm@...ck.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [patch] SLQB v2

On Fri, 2 May 2008, Nick Piggin wrote:

> But overloading struct page values happens in other places too. Putting
> everything into struct page is not scalable. We could also make kmalloc

Well lets at least attempt to catch the biggest users. Also makes code 
clearer if you f.e. use page->first_page instead of page->private for 
compound pages.

kmalloc is intended to return an arbitrary type. struct page has a defined 
format that needs to be respected.

--
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/