linux-kernel - Re: zram: zsmalloc calls sleeping function from atomic context

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: <53283671.1030509@citrix.com>
Date:	Tue, 18 Mar 2014 12:05:05 +0000
From:	David Vrabel <david.vrabel@...rix.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
	Minchan Kim <minchan@...nel.org>,
	Nitin Gupta <ngupta@...are.org>,
	Jerome Marchand <jmarchan@...hat.com>,
	<linux-kernel@...r.kernel.org>,
	Dietmar Hahn <dietmar.hahn@...fujitsu.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: zram: zsmalloc calls sleeping function from atomic context

On 17/03/14 23:01, Andrew Morton wrote:
> 
> OK, thanks.  David, there's our atomic unmap and there are probably
> others.  Converting a previously-atomic utility function into one which
> can sleep is going to be difficult.

I think we should drop these patches.  I think Fujitsu were doing
something particularly odd with an out-of-tree driver.

> Or can this code which vmaps 50GB be changed to unmap it in 16MB chunks
> via unmap_kernel_range(), with a cond_resched() in the loop?

This sounds like something the people from Fujitsu can explore.

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