linux-kernel - Allocating sys_membarrier syscall number on other archs

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]

Message-ID: <1721242013.30076.1440648282669.JavaMail.zimbra@efficios.com>
Date:	Thu, 27 Aug 2015 04:04:42 +0000 (UTC)
From:	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	linux-api <linux-api@...r.kernel.org>
Subject: Allocating sys_membarrier syscall number on other archs

Hi Andrew,

The sys_membarrier patches you have in your tree target
x86 32-64 and generic, but I did not allocate the system call
number on other architectures to minimize the amount of
collisions, and because I do not have all those architectures
handy.

How would you recommend to proceed to allocate those ?

sys_membarrier is pretty much architecture agnostic: it
takes two integer parameters, and the only function it calls,
synchronize_sched(), is available on all architectures.

Thanks,

Mathieu

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
--
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/