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-next>] [day] [month] [year] [list]
Date:   Fri,  6 Oct 2017 08:36:33 -0500
From:   Luis Felipe Sandoval Castro 
        <luis.felipe.sandoval.castro@...el.com>
To:     linux-mm@...ck.org, linux-kernel@...r.kernel.org
Cc:     akpm@...ux-foundation.org, vbabka@...e.cz, mhocko@...e.com,
        mingo@...nel.org, rientjes@...gle.com, n-horiguchi@...jp.nec.com,
        salls@...ucsb.edu,
        Luis Felipe Sandoval Castro 
        <luis.felipe.sandoval.castro@...el.com>
Subject: [PATCH v1][cover-letter] mm/mempolicy.c: Fix get_nodes() off-by-one error.

According to mbind() and set_mempolicy()'s man pages the argument "maxnode"
specifies the max number of bits in the "nodemask" (which is also to be passed
to these functions) that should be considered for the memory policy. If maxnode
= 2, only two bits are to be considered thus valid node masks are: 0b00, 0b01,
0b10 and 0b11.

In systems with multiple NUMA nodes, sometimes it is useful to set strict
memory policies like MPOL_BIND to restric memory allocations to a single node
maybe because it is the closest node or because is a high bandwidth node,
however an off-by-one error in get_nodes() the function that copies the node
mask from user space requires users to pass maxnode = actual_maxnode + 1 to
mbind()/set_mempolicy(), for instance with 2 nodes maxnode = 3.

Below some code to exemplify this behavior, on a system with 2 NUMA nodes to
force memory allocation on node 1, nodemask = 2 (0b10) and maxnode should be 2,
however if maxnode = 2 set_mempolicy() fails with error code 22, to make this
code work maxnode = 3.  The proposed patch fixes this issue, allowing users to
use maxnode = 2.


// compile with  gcc -std=c99 -lnuma test.c -o test

#define _GNU_SOURCE

#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <errno.h>
#include <sched.h>
#include <numa.h>
#include <numaif.h>

#define NUMBER_OF_LETTERS 26

int main() {
	int cpu = sched_getcpu();
	int node = numa_node_of_cpu(cpu);
	printf("process running on CPU %d numa node %d\n", cpu, node);

	// 2 == 0b10 allocate memory on NUMA node 1
	unsigned long nodemask = 2; 

	// with maxnode = 3 this code works on a system with 2 NUMA nodes
	unsigned long maxnode = 2;

	if (set_mempolicy(MPOL_BIND, &nodemask, maxnode)) {
		printf("set_mempolicy() failed with error code: %d, error string: %s\n",
			errno, strerror(errno));
		exit(-1);
	}

	char *ptr = (char*)malloc(NUMBER_OF_LETTERS * sizeof(char));

	for (int i = 0; i < NUMBER_OF_LETTERS; i++)
	ptr[i] = i + 'a';

	printf("freeing memory...\n");
	free(ptr);

	return 0;
}

Luis Felipe Sandoval Castro (1):
  mm/mempolicy.c: Fix get_nodes() off-by-one error.

 mm/mempolicy.c | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

-- 
1.8.3.1

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ