linux-kernel - Re: [PATCH 1/1] x86: syscalls: sys_setrlimit64/sys_getrlimit64 calls to provide FSIZE limits

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

Message-Id: <200901301904.52328.arnd@arndb.de>
Date:	Fri, 30 Jan 2009 19:04:51 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	Narendra Prasad Madanapalli <narendramind@...il.com>
Cc:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	torvalds@...l.org, linux-api@...r.kernel.org,
	mtk.manpages@...glemail.com
Subject: Re: [PATCH 1/1] x86: syscalls: sys_setrlimit64/sys_getrlimit64 calls  to provide FSIZE limits > 2^32-1

On Friday 30 January 2009, Narendra Prasad Madanapalli wrote:
> Can you provide me more information on how to port these system calls
> to 32-on-64 kernel.

Your interface has compatible calling conventions between 32 and 64
bit user programs, so for x86, all you need to do is to add them to
arch/x86/ia32/ia32entry.S in the same way as you did for
arch/x86/kernel/syscall_table_32.S.
For the other architectures, the respective maintainers will take
care of this if your patch gets accepted. Unfortunately, each
architecture has a different way of adding the compat system
calls.

	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/