From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] fix an infinite loop with a corrupted pc partition table
Date: Sun, 26 Jul 2009 08:49:43 +0200 [thread overview]
Message-ID: <1248590983.3661.2.camel@fz.local> (raw)
In-Reply-To: <d7ead6de0907251620r485d4ecbj7e9208651a1ab7e1@mail.gmail.com>
Am Sonntag, den 26.07.2009, 01:20 +0200 schrieb Vladimir 'phcoder'
Serbinenko:
> On Sun, Jul 26, 2009 at 12:58 AM, Vladimir 'phcoder'
> Serbinenko<phcoder@gmail.com> wrote:
> > On Sun, Jul 26, 2009 at 12:35 AM, Vladimir 'phcoder'
> > Serbinenko<phcoder@gmail.com> wrote:
> >>> Links backwards between extended partition entries are more likely
> to be
> >>> due to data corruption than due to buggy partitoning tools. OK,
> if you
> >>> want, let's support up to 10 backward links. That's more than
> enough.
> >> I remembered a compact algorithm for detecting loops of such kind I
> >> will implement it and submit a patch and we'll see how really
> compact
> >> it is
> > Here it is. Strange that I haven't remembered this algorithm before.
> > Can someone test this patch?
> Small optimisation
This works with the partition table of the initial bug report:
/home/fz/grub/grub2-1.96+20090725/kern/partition.c:106: Detecting pc_partition_map...
/home/fz/grub/grub2-1.96+20090725/kern/disk.c:389: Reading `hd1'...
/home/fz/grub/grub2-1.96+20090725/partmap/pc.c:153: partition 0: flag 0x0, type 0x5, start 0x0, len 0x11177330
/home/fz/grub/grub2-1.96+20090725/partmap/pc.c:153: partition 1: flag 0x0, type 0x0, start 0x0, len 0x0
/home/fz/grub/grub2-1.96+20090725/partmap/pc.c:153: partition 2: flag 0x0, type 0x0, start 0x0, len 0x0
/home/fz/grub/grub2-1.96+20090725/partmap/pc.c:153: partition 3: flag 0x0, type 0x0, start 0x0, len 0x0
/home/fz/grub/grub2-1.96+20090725/kern/disk.c:389: Reading `hd1'...
/home/fz/grub/grub2-1.96+20090725/kern/partition.c:112: pc_partition_map detection failed.
/home/fz/grub/grub2-1.96+20090725/kern/disk.c:333: Closing `hd1'.
--
Felix Zielcke
Proud Debian Maintainer
next prev parent reply other threads:[~2009-07-26 6:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 16:58 [PATCH] fix an infinite loop with a corrupted pc partition table Felix Zielcke
2009-07-24 19:24 ` Felix Zielcke
2009-07-24 20:28 ` Pavel Roskin
2009-07-24 20:46 ` Vladimir 'phcoder' Serbinenko
2009-07-25 16:36 ` Robert Millan
2009-07-25 16:56 ` Vladimir 'phcoder' Serbinenko
2009-07-25 22:06 ` Pavel Roskin
2009-07-25 22:35 ` Vladimir 'phcoder' Serbinenko
2009-07-25 22:58 ` Vladimir 'phcoder' Serbinenko
2009-07-25 23:20 ` Vladimir 'phcoder' Serbinenko
2009-07-26 6:49 ` Felix Zielcke [this message]
2009-07-28 17:55 ` Robert Millan
2009-08-23 15:40 ` Vladimir 'phcoder' Serbinenko
2009-08-28 17:30 ` Vladimir 'phcoder' Serbinenko
2009-09-11 21:50 ` Pavel Roskin
2009-07-24 19:56 ` Pavel Roskin
2009-07-24 20:35 ` Vladimir 'phcoder' Serbinenko
2009-07-24 21:03 ` Pavel Roskin
2009-07-25 10:48 ` Vladimir 'phcoder' Serbinenko
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=1248590983.3661.2.camel@fz.local \
--to=fzielcke@z-51.de \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.