All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] biosdisk / open_device() messing up offsets
Date: Wed, 04 Jun 2008 21:47:17 -0400	[thread overview]
Message-ID: <1212630437.26365.18.camel@dv> (raw)
In-Reply-To: <20080604233536.GA21711@thorin>

On Thu, 2008-06-05 at 01:35 +0200, Robert Millan wrote:
> It seems that open_device() in biosdisk is messing up offsets when
> accessing partitions.  For example if you try:
> 
> grub> hexdump (hd0,1)
> 
> in grub-emu, you'll get a message saying lseek failed.  The problem is that
> it substracts to the sector offset, so all accesses get to wrong data and
> accessing sector 0 results in underflow.
> 
> I would think those lines (see patch) are plainly wrong, but they appear to
> be very old, and it is strange that this wasn't noticed earlier.  Maybe we
> have changed behaviour around partition/disk offsets, causing this breakage
> without noticing?

The question whether sector is relative to the partition or to the whole
disk.  From what I see in disk/memdisk.c or it disk/i386/pc/biosdisk.c,
the sector is relative to the whole disk.  There is no compensation for
partition offsets.  That's low-level code that doesn't know about
partitions, and util/biosdisk.c correctly tries to emulate that.

I guess grub-emu gets it wrong somewhere.

-- 
Regards,
Pavel Roskin



  reply	other threads:[~2008-06-05  1:47 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-04 23:35 [PATCH] biosdisk / open_device() messing up offsets Robert Millan
2008-06-05  1:47 ` Pavel Roskin [this message]
2008-06-05 21:12   ` Robert Millan
2008-06-06 15:56 ` Robert Millan
2008-06-06 22:53   ` Pavel Roskin
2008-06-06 23:38     ` Robert Millan
2008-06-07  2:58       ` Pavel Roskin
2008-06-08 19:29         ` Robert Millan
2008-06-07  6:33       ` Pavel Roskin
2008-06-07  7:48         ` Bean
2008-06-08  6:00           ` Pavel Roskin
2008-06-08  6:44             ` Bean
2008-06-08  6:52               ` Pavel Roskin
2008-06-08  7:11                 ` Bean
2008-06-08  7:29                   ` Pavel Roskin
2008-06-08 11:49                     ` Bean
2008-06-08 18:42                       ` Pavel Roskin
2008-06-08 18:57                         ` Bean
2008-06-09  1:43                           ` Pavel Roskin
2008-06-09 18:30                             ` Bean
2008-06-10  7:16                               ` Bean
2008-06-10 18:26                                 ` Pavel Roskin
2008-06-10 18:51                                   ` Bean
2008-06-10 20:19                                     ` Pavel Roskin
2008-06-10 22:58                                     ` Pavel Roskin
2008-06-10 23:18                                       ` [RFC PATCH] " Pavel Roskin
2008-06-11  5:25                                       ` Bean
2008-06-12  4:01                                         ` Pavel Roskin
2008-06-12  6:22                                         ` Pavel Roskin
2008-06-12  9:51                                           ` Bean
2008-06-12 16:25                                             ` Pavel Roskin
2008-06-13  3:48                                               ` Bean
2008-06-13  4:31                                                 ` Pavel Roskin
2008-06-13  4:39                                                   ` Bean
2008-06-13  5:00                                                     ` Pavel Roskin
2008-06-13  5:18                                                       ` Bean
2008-06-07  8:37     ` Bean
2008-06-08  5:41       ` Pavel Roskin

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=1212630437.26365.18.camel@dv \
    --to=proski@gnu.org \
    --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.