linux-kernel - Re: [PATCH 0/7] V3 of the async function call patches

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 7 Jan 2009 16:17:24 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Arjan van de Ven <arjan@...radead.org>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 0/7] V3 of the async function call patches



On Wed, 7 Jan 2009, Arjan van de Ven wrote:
>
> version 3 of the async function call patches
> 
> * Dropped the ACPI part; it broke i surprising ways; needs a rethink
>   (working with Len and co on that)
> * Included asynchronous delete()

Ok, I pulled this, because I really do want the boot speedups and the 
previous version missed the last merge window, but after booting it, I 
started to worry:

My dmesg shows:

 [    2.264955] sd 5:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 [    2.264958]  sdb:<6>Freeing unused kernel memory: 408k freed

Ouch. How come that "Freeing unused kernel memory" got done in the middle 
of the sdb partition thing?

There's a async_synchronize_full() there before the free_initmem(), but 
I'm worrying that it just isn't working. Hmm? What am I missing?

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