From: Andrew Morton <akpm@osdl.org>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: sct@redhat.com, torvalds@osdl.org, aia21@cam.ac.uk,
ext2-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sector_t overflow in block layer
Date: Fri, 19 May 2006 14:15:22 -0700 [thread overview]
Message-ID: <20060519141522.76c2938e.akpm@osdl.org> (raw)
In-Reply-To: <20060519205550.GI5964@schatzie.adilger.int>
Andreas Dilger <adilger@clusterfs.com> wrote:
>
> One extra suggestion that might be safe and acceptible all around is if
> a device is larger than 2TB w/o a 64-bit sector_t that the block device
> size itself be truncated in the kernel to 2TB-512. This at least prevents
> userspace tools from trying to e.g. format a 3TB filesystem on a device
> that will just corrupt the filesystem.
'twould be good if we could do something like that - doing it on every
single IO submission in submit_bh() Just Feels Wrong.
Also, there's always the option (or enhancement) of emitting lots of scary
warnings and then just proceeding.
next prev parent reply other threads:[~2006-05-19 21:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1147849273.16827.27.camel@localhost.localdomain>
[not found] ` <m3odxxukcp.fsf@bzzz.home.net>
[not found] ` <1147884610.16827.44.camel@localhost.localdomain>
[not found] ` <m34pzo36d4.fsf@bzzz.home.net>
[not found] ` <1147888715.12067.38.camel@dyn9047017100.beaverton.ibm.com>
[not found] ` <m364k4zfor.fsf@bzzz.home.net>
[not found] ` <20060517235804.GA5731@schatzie.adilger.int>
[not found] ` <1147947803.5464.19.camel@sisko.sctweedie.blueyonder.co.uk>
2006-05-18 18:59 ` Andreas Dilger
2006-05-18 20:58 ` Alexey Dobriyan
2006-05-18 21:06 ` Linus Torvalds
2006-05-18 22:12 ` Anton Altaparmakov
2006-05-18 22:41 ` Linus Torvalds
2006-05-18 23:23 ` Andreas Dilger
2006-05-19 19:36 ` Stephen C. Tweedie
2006-05-19 20:11 ` Andrew Morton
2006-05-19 20:55 ` Andreas Dilger
2006-05-19 21:15 ` Andrew Morton [this message]
2006-05-19 21:05 ` Stephen C. Tweedie
2006-05-18 22:43 ` Andreas Dilger
2006-05-22 0:14 ` Pavel Machek
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=20060519141522.76c2938e.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=adilger@clusterfs.com \
--cc=aia21@cam.ac.uk \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.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
all inboxes | Powered by JetHome®