From: Wakko Warner <wakko@animx.eu.org>
To: Neil Brown <neilb@suse.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, aeb@cwi.nl,
Jens Axboe <jens.axboe@oracle.com>
Subject: Re: Why aren't partitions limited to fit within the device?
Date: Sun, 15 Oct 2006 21:22:49 -0400 [thread overview]
Message-ID: <20061016012249.GA2029@animx.eu.org> (raw)
In-Reply-To: <17714.52626.667835.228747@cse.unsw.edu.au>
Neil Brown wrote:
> On Friday October 13, alan@lxorguk.ukuu.org.uk wrote:
> > No I think not. Any partition which is partly outside the disk should be
> > ignored entirely, that ensures it doesn't accidentally get mounted and
> > trashed by an HPA or similar mixup.
>
> Hmmm.. So Alan things a partially-outside-this-disk partition
> shouldn't show up at all, and Andries thinks it should.
> And both give reasonably believable justifications.
>
> Maybe we need a kernel parameter? How about this?
How about something in /proc or /sys to force the partition to show or not?
Maybe something like
echo 1 > /sys/block/hda/hda4/visible
?
Just an idea, my view would be not to introduce a new kernel parameter since
you have to reboot just to see it. It's quite possible this would effect
USB/Firewire storage devices. I have never been bitten by this problem
however it would be nice not to have to reboot to solve one like this say on
a slightly corrupted usb memory stick.
A possibility of using words instead of numbers, in the above example could
be one of: yes r/o no indicating full r/w, r/o, or not visible.
I'm not so sure if the size of the partition that is visible should be the
size according to the partition table or the size according to the start of
the partition to the end of the device. I would probably choose to have the
size to be the smaller number.
I was bitten by a 2.4 to 2.6 conversion where the size of the disk was 1
sector larger than what I saw in 2.4, but it was a minor problem which was
solved by masking off bit 0 of the size.
--
Lab tests show that use of micro$oft causes cancer in lab animals
Got Gas???
next prev parent reply other threads:[~2006-10-16 1:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 23:50 Why aren't partitions limited to fit within the device? Neil Brown
2006-10-13 1:02 ` Andries Brouwer
2006-10-13 1:31 ` Neil Brown
2006-10-13 15:07 ` Alan Cox
2006-10-13 18:16 ` jdow
2006-10-16 0:08 ` Neil Brown
2006-10-16 1:22 ` Wakko Warner [this message]
2006-10-16 1:31 ` Randy Dunlap
2006-10-16 4:09 ` Kyle Moffett
2006-10-16 6:40 ` Andries Brouwer
2006-10-16 6:43 ` dean gaudet
2006-10-16 7:28 ` Xavier Bestel
2006-10-16 10:54 ` Alan Cox
2006-10-17 6:05 ` Chris Wedgwood
2006-10-15 8:29 ` Ville Herva
2006-10-15 23:50 ` Neil Brown
2006-10-16 5:27 ` Ville Herva
2006-10-16 6:02 ` Andries Brouwer
2006-10-16 6:20 ` Ville Herva
2006-10-16 6:27 ` dean gaudet
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=20061016012249.GA2029@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=aeb@cwi.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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