From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Alan Cox <alan@linux.intel.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"aeb@cwi.nl" <aeb@cwi.nl>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Cannot partition 32GB disk on a 32bit machine (correct version of the patch this time)
Date: Thu, 19 Jun 2014 16:44:07 -0700 [thread overview]
Message-ID: <1403221447.1962.24.camel@jarvis.lan> (raw)
In-Reply-To: <1403219058.10778.72.camel@acox1-desk.ger.corp.intel.com>
On Fri, 2014-06-20 at 00:04 +0100, Alan Cox wrote:
> > Wow that's junk issued by an Exchange server ... Alan, really ...
>
> Blame evolution. It apparently thinks that if you follow up to your own
> email from one address it should randomly switch to another.
so you @linux.intel.com is sane and you @intel.com is exchange ...
> > Do you have CONFIG_LBD turned on? That's supposed to let us go up to
> > about 16TB before we run out of page index bits. If you do, we might
> > have a variable that's int but should be sector_t somewhere.
>
> LBDAF is set
OK, so as Andrew said, it looks like Viro's conversion from aio to
iterators has a length and offset problem on 32 bits.
my suspicion is that iov_offset and count in struct iov_iter have to
become loff_t quantities ... plus a lot of other size_t to loff_t
conversions. Hopefully Viro will fix it as a matter of urgency.
James
next prev parent reply other threads:[~2014-06-19 23:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 9:30 Cannot partition 32GB disk on a 32bit machine Alan Cox
2014-06-19 9:33 ` Cannot partition 32GB disk on a 32bit machine (correct version of the patch this time) Cox, Alan
2014-06-19 18:43 ` James Bottomley
2014-06-19 20:51 ` Andrew Morton
2014-06-19 21:12 ` Paul Bolle
2014-06-19 23:04 ` Alan Cox
2014-06-19 23:44 ` James Bottomley [this message]
2014-06-19 21:12 ` Andries E. Brouwer
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=1403221447.1962.24.camel@jarvis.lan \
--to=james.bottomley@hansenpartnership.com \
--cc=aeb@cwi.nl \
--cc=akpm@linux-foundation.org \
--cc=alan@linux.intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).