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: Fri, 06 Jun 2008 18:53:52 -0400	[thread overview]
Message-ID: <1212792832.1893.17.camel@dv> (raw)
In-Reply-To: <20080606155649.GA13255@thorin>

On Fri, 2008-06-06 at 17:56 +0200, Robert Millan wrote:
> Committed.

I believe it's wrong.  util/biosdisk.c is a low level disk driver.  It's
supposed to read data relative to the disk, like other drivers do.

Besides, is_partition becomes write-only.  It means that the result of
linux_find_partition() is ignored.  Please note that
linux_find_partition() modifies its first argument on success.  It
rewrites the disk device (e.g. /dev/sda) with the partition device
(e.g. /dev/sda1).

If the result of linux_find_partition() is not checked, nobody knows
whether fd is a handle to the partition or to the whole disk.  Yet the
sector variable is used to seek on that device.  Needless to say that
different values would be obtained.

Also, grub-emu is not the only user of util/biosdisk.c.  It is also used
by grub-setup, which is working correctly,  as far as I can tell.

By the way, the current GRUB just failed to install on my test system.
After I rebooted it, GRUB hung on startup after showing "GRUB".

It may be something else.  It was an unclean reboot after a panic for
unrelated reasons, so the hanging problem may be an issue with ext3.
Anyway, extreme caution is required with the current code!

-- 
Regards,
Pavel Roskin



  reply	other threads:[~2008-06-06 22:54 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
2008-06-05 21:12   ` Robert Millan
2008-06-06 15:56 ` Robert Millan
2008-06-06 22:53   ` Pavel Roskin [this message]
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=1212792832.1893.17.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.