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]
Date:	Sat, 12 Jul 2014 14:32:01 +0200
From:	Jens Axboe <>
To:	Jiang Liu <>,
	Andrew Morton <>,
	Mel Gorman <>,
	David Rientjes <>,
	Mike Galbraith <>,
	Peter Zijlstra <>,
	"Rafael J . Wysocki" <>,
	Dipankar Sarma <>,
	"Paul E. McKenney" <>,
	Balbir Singh <>,
	Thomas Gleixner <>,
	Frederic Weisbecker <>,
	Jan Kara <>, Ingo Molnar <>,
	Christoph Hellwig <>,
	"Srivatsa S. Bhat" <>,
	Roman Gushchin <>,
	Xie XiuQi <>
CC:	Tony Luck <>,,,
Subject: Re: [RFC Patch V1 01/30] mm, kernel: Use cpu_to_mem()/numa_mem_id()
 to support memoryless node

On 2014-07-11 09:37, Jiang Liu wrote:
> When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
> may return a node without memory, and later cause system failure/panic
> when calling kmalloc_node() and friends with returned node id.
> So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
> memory for the/current cpu.
> If CONFIG_HAVE_MEMORYLESS_NODES is disabled, cpu_to_mem()/numa_mem_id()
> is the same as cpu_to_node()/numa_node_id().

I think blk-mq requires some of the same help, as do other places in the 
block layer. I'll take a look at that.

As for you smp.c bits here:

Acked-by: Jens Axboe <>

Jens Axboe

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists