linux-kernel - Re: [PATCH V6 6/6] mips: Add entry for new mlock2 syscall

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: <20150730143252.GF25552@linux-mips.org>
Date:	Thu, 30 Jul 2015 16:32:52 +0200
From:	Ralf Baechle <ralf@...ux-mips.org>
To:	Eric B Munson <emunson@...mai.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-mips@...ux-mips.org, linux-api@...r.kernel.org,
	linux-arch@...r.kernel.org, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH V6 6/6] mips: Add entry for new mlock2 syscall

On Wed, Jul 29, 2015 at 11:42:55AM -0400, Eric B Munson wrote:

> A previous commit introduced the new mlock2 syscall, add entries for the
> MIPS architecture.

Looking good, so

Acked-by: Ralf Baechle <ralf@...ux-mips.org>

Recently somebody else was floating around a patch that was adding
three syscalls.  Not sure if in the end the adding the syscall part to
non-x86 was dropped.  Just mentioning in case there are any conflicts;
in particulary nobody should rely on syscall numbers unless they're
for something in Linus' tree!

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