From: Christoph Hellwig <hch@infradead.org>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Jens Axboe <axboe@kernel.dk>,
"Alasdair G. Kergon" <agk@redhat.com>,
Mike Snitzer <msnitzer@redhat.com>,
dm-devel@redhat.com, "David S. Miller" <davem@davemloft.net>,
linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, Neil Brown <neilb@suse.de>,
linux-raid@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] block devices: validate block device capacity
Date: Mon, 3 Feb 2014 00:15:06 -0800 [thread overview]
Message-ID: <20140203081506.GA10961@infradead.org> (raw)
In-Reply-To: <alpine.LRH.2.02.1401310316560.21451@file01.intranet.prod.int.rdu2.redhat.com>
On Fri, Jan 31, 2014 at 03:20:17AM -0500, Mikulas Patocka wrote:
> So if you think you can support 16TiB devices and leave pgoff_t 32-bit,
> send a patch that does it.
>
> Until you make it, you should apply the patch that I sent, that prevents
> kernel lockups or data corruption when the user uses 16TiB device on
> 32-bit kernel.
Exactly. I had actually looked into support for > 16TiB devices for
a NAS use case a while ago, but when explaining the effort involves
the idea was dropped quickly. The Linux block device is too deeply
tied to the pagecache to make it easily feasible.
next prev parent reply other threads:[~2014-02-03 8:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 20:40 Mikulas Patocka
2014-01-30 22:49 ` James Bottomley
2014-01-30 23:10 ` Mikulas Patocka
2014-01-30 23:37 ` James Bottomley
2014-01-31 0:20 ` Mikulas Patocka
2014-01-31 1:43 ` James Bottomley
2014-01-31 2:43 ` Mikulas Patocka
2014-01-31 5:45 ` James Bottomley
2014-01-31 8:20 ` Mikulas Patocka
2014-02-03 8:15 ` Christoph Hellwig [this message]
2014-02-03 20:22 ` Mikulas Patocka
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=20140203081506.GA10961@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=dm-devel@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=msnitzer@redhat.com \
--cc=neilb@suse.de \
/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®