From: Russell King <rmk@arm.linux.org.uk>
To: Peter Oberparleiter <Peter.Oberparleiter@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Partition check order in fs/partition/check.c?
Date: Tue, 1 Apr 2003 14:27:43 +0100 [thread overview]
Message-ID: <20030401142743.C30470@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200304011316.h31DFwTR039380@d06relay02.portsmouth.uk.ibm.com>; from Peter.Oberparleiter@gmx.de on Tue, Apr 01, 2003 at 03:14:56PM +0200
On Tue, Apr 01, 2003 at 03:14:56PM +0200, Peter Oberparleiter wrote:
> Hm, what do you think of these additional checks:
>
> 1. Check for overlap of partitions
That's something which should be done for any partitioning method imho.
I have heard of some situations where, on x86 machines, the DOS and
ext2 filesystems overlapped, but somehow managed to keep working for
a considerable period of time. Then when it all goes wrong, the user
blamed Linux for screwing their DOS/Windows partition.
This might be an acceptable way out of this problem.
> 2. Check for number of recognized partitions (i.e. size != 0) > 0
If the checksum seems to be correct and you mis-parse an x86 bios
partition table as powertec, chances are that you'll have a non-zero
size word somewhere in that sector.
> 3. Check for struct ptec_partition.unused1, unused2, unused5 == 0
> (assuming they default to zero)
Unfortunately they don't default to zero.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-04-01 13:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 9:33 Partition check order in fs/partition/check.c? Peter Oberparleiter
2003-04-01 10:35 ` Russell King
2003-04-01 13:14 ` Peter Oberparleiter
2003-04-01 13:27 ` Russell King [this message]
2003-04-01 20:24 ` jw schultz
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=20030401142743.C30470@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=Peter.Oberparleiter@gmx.de \
--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