linux-kernel - Re: [RFC 3/3] asm-generic: Drop renameat syscall from default list

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]

Date:	Wed, 23 Apr 2014 13:41:37 +0100
From:	James Hogan <james.hogan@...tec.com>
To:	Arnd Bergmann <arnd@...db.de>, Miklos Szeredi <mszeredi@...e.cz>
Cc:	linux-arch@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Vineet Gupta <vgupta@...opsys.com>,
	Catalin Marinas <catalin.marinas@....com>,
	Will Deacon <will.deacon@....com>,
	ARM Kernel List <linux-arm-kernel@...ts.infradead.org>,
	Mark Salter <msalter@...hat.com>,
	Aurelien Jacquiot <a-jacquiot@...com>,
	linux-c6x-dev@...ux-c6x.org, Richard Kuo <rkuo@...eaurora.org>,
	linux-hexagon@...r.kernel.org, metag <linux-metag@...r.kernel.org>,
	Jonas Bonn <jonas@...thpole.se>, linux@...ts.openrisc.net,
	Chen Liqin <liqin.linux@...il.com>,
	Lennox Wu <lennox.wu@...il.com>,
	Chris Metcalf <cmetcalf@...era.com>,
	Guan Xuetao <gxt@...c.pku.edu.cn>
Subject: Re: [RFC 3/3] asm-generic: Drop renameat syscall from default list

On 23 April 2014 13:18, Arnd Bergmann <arnd@...db.de> wrote:
> On Wednesday 23 April 2014, James Hogan wrote:
>> The new renameat2 syscall provides all the functionality provided by the
>> renameat syscall and adds flags, so future architectures won't need to
>> include renameat.
>>
>> Therefore drop the renameat syscall from the generic syscall list unless
>> __ARCH_WANT_RENAMEAT is defined by the architecture's unistd.h prior to
>> including asm-generic/unistd.h, and adjust all architectures using the
>> generic syscall list to define it so that no in-tree architectures are
>> affected.
>
> I should have read this one before replying to patch 2 ;-)
>
>> Signed-off-by: James Hogan <james.hogan@...tec.com>
>> Cc: Arnd Bergmann <arnd@...db.de>
>> Cc: linux-arch@...r.kernel.org
>> Cc: Vineet Gupta <vgupta@...opsys.com>
>> Cc: Catalin Marinas <catalin.marinas@....com>
>> Cc: Will Deacon <will.deacon@....com>
>> Cc: linux-arm-kernel@...ts.infradead.org
>> Cc: Mark Salter <msalter@...hat.com>
>> Cc: Aurelien Jacquiot <a-jacquiot@...com>
>> Cc: linux-c6x-dev@...ux-c6x.org
>> Cc: Richard Kuo <rkuo@...eaurora.org>
>> Cc: linux-hexagon@...r.kernel.org
>> Cc: linux-metag@...r.kernel.org
>> Cc: Jonas Bonn <jonas@...thpole.se>
>> Cc: linux@...ts.openrisc.net
>> Cc: Chen Liqin <liqin.linux@...il.com>
>> Cc: Lennox Wu <lennox.wu@...il.com>
>> Cc: Chris Metcalf <cmetcalf@...era.com>
>> Cc: Guan Xuetao <gxt@...c.pku.edu.cn>
>> ---
>> Is this the approach we want to take to keep the default syscall list
>> minimal? We could for example have made renameat2 use the renameat
>> syscall number for new arches, but it seemed best to leave a gap for new
>> arches to improve consistency of numbering.
>
> I think leaving the hole is best.
>
>> This patch is a no-op for arches in tree, so there's no harm for this to
>> wait for the v3.16 merge window.
>
> Sounds good. I guess I'll have to put this into my asm-generic tree
> then, unless I can get the nios2 maintainers to pick it up.

Okay, thanks.

> If you don't mind, can you submit the first two patches to Linus
> directly?

It appears Miklos Szeredi beat me to it with patch 1 (adding renameat2
syscall to asm-generic unistd.h), and will be submitting it to Linus
at some point as part of his renameat2 series.
Miklos: Do you think it makes sense for you to include my second patch
in your series too since it's renameat2 related?
http://marc.info/?l=linux-kernel&m=139824773305016&w=2

Otherwise I'm happy to take it or both patches for v3.15.

Cheers
James
--
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/