linux-kernel - Re: [RFC 2/3] scripts/checksyscalls.sh: Make renameat optional

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: <201404231415.24869.arnd@arndb.de>
Date:	Wed, 23 Apr 2014 14:15:24 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	James Hogan <james.hogan@...tec.com>
Cc:	linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC 2/3] scripts/checksyscalls.sh: Make renameat optional

On Wednesday 23 April 2014, James Hogan wrote:
> The new renameat2 syscall provides all the functionality of renameat
> with an additional flags argument, so make renameat optional so that
> future architectures can omit it without getting a warning.
> 
> Signed-off-by: James Hogan <james.hogan@...tec.com>
> Cc: Arnd Bergmann <arnd@...db.de>
> Cc: linux-arch@...r.kernel.org
> ---
> This patch doesn't affect existing architectures, so there's no harm for
> this to wait for the v3.16 merge window.

Acked-by: Arnd Bergmann <arnd@...db.de>

I'm not actually sure how we'd arrange for new architectures not
to provide renameat() when using the generic syscall ABI, but this
patch is correct anyway.

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