linux-kernel - Re: [RFC PATCH v1 14/31] ARC: syscall support

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: <50A38F12.8030501@imgtec.com>
Date:	Wed, 14 Nov 2012 12:31:14 +0000
From:	James Hogan <james.hogan@...tec.com>
To:	Arnd Bergmann <arnd@...db.de>
CC:	Jonas Bonn <jonas.bonn@...il.com>,
	Vineet Gupta <Vineet.Gupta1@...opsys.com>,
	<linux-arch@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	<tglx@...utronix.de>, Markos <markos.chandras@...tec.com>
Subject: Re: [RFC PATCH v1 14/31] ARC: syscall support

On 14/11/12 12:23, Arnd Bergmann wrote:
> On Tuesday 13 November 2012, James Hogan wrote:
>> Hopefully with several architecture maintainers asking for this it might
>> get somewhere, but indeed we're aware of the feedback problem on that list.
>>
>> The points that I've considered for defaulting to old syscalls:
>> * doesn't change existing behaviour of other architectures, so is simply
>> less risk of breaking them.
>> * could possibly make uClibc slightly smaller if it doesn't have to add
>> extra arguments.
> 
> The second argument is not very good when you consider that it means adding
> the same wrapper into the kernel rather than into uClibc, where it can
> be stripped out when unused (e.g. for static compilation) and doesn't
> have to be present in memory since the library is in pageable user space
> memory, while the kernel side implementation would always have to
> present.

The context is existing architectures which already have to support the
deprecated syscalls pretty much forever (in addition to the new ones),
and therefore can't strip out the kernel side implementation anyway.

I don't see any of these arguments (either way) as holding too much
weight to be honest though.

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/