linux-kernel - Re: Q: semaphore and kmalloc(GFP

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: <200905110319.n4B3J9hc092830@www262.sakura.ne.jp>
Date:	Mon, 11 May 2009 12:19:09 +0900
From:	Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
To:	kosaki.motohiro@...fujitsu.com
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Q: semaphore and kmalloc(GFP_KERNEL)?

KOSAKI Motohiro wrote:
> > Can the kernel detect that we need to let kmalloc() fail and
> > wake up the writer process so that the writer process releases
> > the rw_semaphore and reader processes can continue?
> 
> it can't. Plus it shouldn't.
> some caller don't want kmalloc() failure.

Thanks.
Then, should I move kmalloc(GFP_KERNEL) to outside the lock whenever possible?
(I worry some lock held by the caller interferes kmalloc(GFP_KERNEL).)
--
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/