From: "Henrik Nordström" <henrik@henriknordstrom.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] sandbox: block driver using host file/device as backing store, crash in ext4
Date: Sat, 18 May 2013 16:24:15 +0200 [thread overview]
Message-ID: <1368887055.15404.7.camel@localhost> (raw)
In-Reply-To: <CAPnjgZ1AHFVafFttrbfunskrA4qGwS-4oC6ehvWJ1BU=+x2xxg@mail.gmail.com>
tor 2013-05-16 klockan 21:53 -0700 skrev Simon Glass:
> Sorry I meant:
>
> =>ext4ls host 0:3
> Segmentation fault (core dumped)
>
> It may not be your code, but I think the segfault is there.
It's crashing in ext4 for me.
#0 ext4fs_set_blk_dev (rbdd=0x6434a0 <host_devices>,
info=info at entry=0x643980 <fs_partition>) at dev.c:56
#0 ext4fs_set_blk_dev (rbdd=0x6434a0 <host_devices>,
info=info at entry=0x643980 <fs_partition>) at dev.c:56
56 get_fs()->total_sect = (info->size * info->blksz) >>
57 get_fs()->dev_desc->log2blksz;
58 get_fs()->dev_desc = rbdd;
p(gdb) p get_fs()
$2 = (struct ext_filesystem *) 0x644410 <ext_fs>
(gdb) p $2->dev_desc
$5 = (block_dev_desc_t *) 0x0
Looks like a generic ext4 bug in the new block size handling code.
I think it just needs to be shuffled around a bit so the dev_desc is
assigned before, not after.
Regards
Henrik
next prev parent reply other threads:[~2013-05-18 14:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 23:36 [U-Boot] [PATCH] sandbox: block driver using host file/device as backing store Henrik Nordström
2013-05-15 17:42 ` Simon Glass
2013-05-15 21:29 ` Henrik Nordström
2013-05-15 21:54 ` [U-Boot] [PATCH v2] " Henrik Nordström
2013-05-15 22:20 ` Simon Glass
2013-05-16 1:09 ` Henrik Nordström
2013-05-17 4:53 ` Simon Glass
2013-05-18 14:24 ` Henrik Nordström [this message]
2013-05-18 17:46 ` [U-Boot] sandbox: block driver using host file/device as backing store, crash in ext4 Simon Glass
2013-06-16 14:50 ` [U-Boot] [PATCH v2] sandbox: block driver using host file/device as backing store Simon Glass
2013-06-17 1:39 ` Henrik Nordström
2013-07-31 11:29 ` Simon Glass
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=1368887055.15404.7.camel@localhost \
--to=henrik@henriknordstrom.net \
--cc=u-boot@lists.denx.de \
/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