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: Sun, 08 Jun 2008 14:42:10 -0400 [thread overview]
Message-ID: <1212950530.8619.7.camel@dv> (raw)
In-Reply-To: <ca0f59980806080449q1982d4f6r7d3f89b9abae9ac@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1827 bytes --]
On Sun, 2008-06-08 at 19:49 +0800, Bean wrote:
> Can you use grub-fstest ?
>
> Also, the header is from
>
> + grub_printf ("header: %d %d %d\n", log->first_block,
> log->last_block, log->start_block);
>
> I don't know why the number doesn't show, unless log is invalid
> pointer. Perhaps the size is invalid, try to add a debug line to show
> the allocated size of log:
>
> log = grub_malloc (sizeof (struct grub_fshelp_journal) +
> grub_be_to_cpu32 (jsb->maxlen) * sizeof
> (grub_disk_addr_t));
The debug output must be getting split somewhere. If I replace colons
and spaces with underscores, I get some numbers. Anyway, the
installation with the patch is unnecessary.
I made a short partition and installed grub on it, but there are no
problems with it in qemu.
But I can reproduce the problem with grub-fstest on the root partition.
[root@dv grub2]# grub-fstest /dev/sda1 ls /
lost+found/ bin/ boot/ data/ dev/ etc/ home/ lib/ lib64/ media/ mnt/
opt/ proc/ root/ sbin/ scratchbox/ selinux/ srv/ sys/ tftpboot/ tmp/
usr/ var/ debug/ tftpboot;4834754b
[root@dv grub2]# grub-fstest /dev/sda1 ls /boot
[root@dv grub2]# ls /
bin debug home lost+found opt sbin srv
tftpboot;4834754b var
boot dev lib media proc scratchbox sys tmp
data etc lib64 mnt root selinux tftpboot usr
[root@dv grub2]# ls /boot
System.map grub vmlinuz
System.map-2.6.26-rc4-wl initrd-2.6.26-rc4-wl.img
vmlinuz-2.6.26-rc4-wl
System.map-2.6.26-rc4-wl.old memtest86+-2.01
vmlinuz-2.6.26-rc4-wl.old
[root@dv grub2]#
As you can see, "grub-fstest /dev/sda1 ls /boot" fails to find any
files. Then I patched grub with your patch. The output of the same
command is attached (compressed).
--
Regards,
Pavel Roskin
[-- Attachment #2: Log-boot.bz2 --]
[-- Type: application/x-bzip, Size: 14355 bytes --]
next prev parent reply other threads:[~2008-06-08 18:42 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
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 [this message]
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=1212950530.8619.7.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.