From: Michael Kerrisk <mtk.manpages@googlemail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: narendramind@spikesource.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, torvalds@osdl.org,
linux-abi@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH 1/1] x86: syscalls: sys_setrlimit64/sys_getrlimit64 calls to provide FSIZE limits > 2^32-1
Date: Tue, 27 Jan 2009 01:46:23 +0100 [thread overview]
Message-ID: <497E595F.2010708@gmail.com> (raw)
In-Reply-To: <200901262004.16364.arnd@arndb.de>
Arnd Bergmann wrote:
> On Friday 23 January 2009, narendramind@spikesource.com wrote:
>> The solution to this problem would require new setrlimit64() and
>> getrlimit64() system calls on x86, and the existing 32-bit system calls
>> would need to be retained so that existing binaries would still run.
>
> When adding new syscalls, please Cc: linux-abi@vger.kernel.org and
Arnd -- I think you meant linux-api, not linux-abi.
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
git://git.kernel.org/pub/scm/docs/man-pages/man-pages.git
man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html
next prev parent reply other threads:[~2009-01-27 0:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 17:59 [PATCH 1/1] x86: syscalls: sys_setrlimit64/sys_getrlimit64 calls to provide FSIZE limits > 2^32-1 narendramind
2009-01-26 19:04 ` Arnd Bergmann
2009-01-27 0:46 ` Michael Kerrisk [this message]
[not found] ` <497E595F.2010708-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-01-30 17:57 ` Narendra Prasad Madanapalli
[not found] ` <85e5430e0901300957x64951d6at2a79c5cb1ee88e97-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-30 18:04 ` Arnd Bergmann
2009-01-26 19:23 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2009-01-23 17:53 narendramind
2009-01-23 17:49 narendramind
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=497E595F.2010708@gmail.com \
--to=mtk.manpages@googlemail.com \
--cc=arnd@arndb.de \
--cc=linux-abi@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narendramind@spikesource.com \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).