public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "jdow" <jdow@earthlink.net>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>, "Neil Brown" <neilb@suse.de>
Cc: <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: Fri, 13 Oct 2006 11:16:08 -0700	[thread overview]
Message-ID: <105201c6eef3$ab64c750$0225a8c0@Wednesday> (raw)
In-Reply-To: 1160752047.25218.50.camel@localhost.localdomain

From: "Alan Cox" <alan@lxorguk.ukuu.org.uk>

> Ar Gwe, 2006-10-13 am 09:50 +1000, ysgrifennodd Neil Brown:
>> So:  Is there any good reason to not clip the partitions to fit
>> within the device - and discard those that are completely beyond
>> the end of the device??
> 
> Its close but not quite the right approach
> 
>> The patch at the end of the mail does that.  Is it OK to submit this
>> to mainline?
> 
> 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.

This is also a risk for users who have a partition that was poorly
setup with an earlier version that allowed it to almost work. If there
is data on that partition refusing to mount it can lead to massive
data loss akin to a broken disk drive.

<<jdow>> I'd propose allowing it to mount read-only and forcing
read-only mode when attempts to mount read-write are made. That way
the user never perceives a data loss situation and can take the
appropriate steps to repair the partitioning error.

{^_^}   Joanne Dow

  reply	other threads:[~2006-10-13 18:16 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 [this message]
2006-10-16  0:08   ` Neil Brown
2006-10-16  1:22     ` Wakko Warner
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='105201c6eef3$ab64c750$0225a8c0@Wednesday' \
    --to=jdow@earthlink.net \
    --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