From: Alan Cox <alan@linux.intel.com>
To: linux-fsdevel@vger.kernel.org, akpm@linux-foundation.org,
aeb@cwi.nl, linux-kernel@vger.kernel.org
Subject: Cannot partition 32GB disk on a 32bit machine
Date: Thu, 19 Jun 2014 10:30:01 +0100 [thread overview]
Message-ID: <1403170201.10778.36.camel@acox1-desk.ger.corp.intel.com> (raw)
The block code has 32bit cleanness problems with the iterator. This
prevents things like partitioning a 32GB volume on a 32bit system.
I hit this with a volume of exactly 32GB in size (easy to duplicate with
virtual machines). Tracing at step by step through the kernel I found
the problem lines in blkdev_read_iter which truncates the size value
into a 32bit value when setting up the iterator.
The hack below if applied "fixes" this and I think demonstrates that
this is the problem spot.
What I'm less clear on is what the correct fix for this should be.
diff --git a/fs/block_dev.c b/fs/block_dev.c
index 6d72746..3792406 100644
--- a/fs/block_dev.c
+++ b/fs/block_dev.c
@@ -1603,6 +1603,9 @@ static ssize_t blkdev_read_iter(struct kiocb
*iocb, struct iov_iter *to)
size -= pos;
iov_iter_truncate(to, size);
+ /* Fix up for 32bit boxes for now */
+ if (to->count < size)
+ to->count = size;
return generic_file_read_iter(iocb, to);
}
next reply other threads:[~2014-06-19 9:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 9:30 Alan Cox [this message]
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
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=1403170201.10778.36.camel@acox1-desk.ger.corp.intel.com \
--to=alan@linux.intel.com \
--cc=aeb@cwi.nl \
--cc=akpm@linux-foundation.org \
--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
all inboxes | Powered by JetHome®