linux-kernel - [patch 0/2] make kcmp own config entry

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-next>] [day] [month] [year] [list]

Message-Id: <20130219064800.719149796@openvz.org>
Date:	Tue, 19 Feb 2013 10:48:00 +0400
From:	Cyrill Gorcunov <gorcunov@...nvz.org>
To:	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Cc:	ebiederm@...ssion.com, xemul@...allels.com, hpa@...or.com,
	akpm@...ux-foundation.org
Subject: [patch 0/2] make kcmp own config entry

Hi guys, kcmp syscall (according to git log) is being wired up for a number
of architectures other than x86 (where it was developed initially). But the
main Makefile which controling its compilation is still x86 dependant.

Thus I think kcmp may deserve own config entry unrelated to arch type it
is being compiled for. In case if some particular arch doesn't support it
ENOSYS should be returned. This small set also wires up kcmp for ARM.

Please take a look, thanks!

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