From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Hugh Dickins <hugh@veritas.com>
Cc: Andrew Morton <akpm@digeo.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: wonderffffffffull ac filemap patch
Date: 27 Mar 2003 19:07:03 +0000 [thread overview]
Message-ID: <1048792021.3228.26.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0303271750220.2542-100000@localhost.localdomain>
On Thu, 2003-03-27 at 17:59, Hugh Dickins wrote:
> > For 2.4 I just wanted to handle what we had and fix up the spec violations.
> > For 2.5.x rlimit64 is calling 8)
>
> Fixing up a silly in what's there, that I understand; and adding rlimit64,
> that too. But on 64-bit arches, isn't rlimit already rlimit64?
>
> If the answer to that is Yes, then doesn't the 0xFFFFFFFFULL test cripple
> them? If the answer to that is No, then how come we're trying to handle
> a case in which limit has more than 32 bits?
Infallibility is only available by special request. I'd have to read the
code and specs again but what you say sounds quite reasonable since off_t
would be 64bit, and rlimit types likewise
prev parent reply other threads:[~2003-03-27 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 17:33 Hugh Dickins
2003-03-27 17:45 ` Alan Cox
2003-03-27 17:59 ` Hugh Dickins
2003-03-27 19:07 ` Alan Cox [this message]
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=1048792021.3228.26.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@digeo.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®