[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Speeding up the mounting of JFFS Device



In article <E6871E7D02CA4D115AB40005B8CCE22D@xxxxxxx.com>,
Dan <dmcdon@xxxxxxx.com> wrote:
>Hello folks:
>
>This week's change to intrep.c by (sjhill) has noticably
>improved the mount time for JFFS - at least for my application.
>Those considering using the Node Cache should try this out
>before going through the hassle of getting the node cache
>going.
>
>It looks like Mr Hill added read-buffering to the scan_flash().
>

We have a bit of an issue. The node cache generates an oops when writing
the filesystem to the node cache. After enabling some debugging and
adding a few other messages, this is what I get:

...
jffs_nc_write_name(): name_offset: 44480
jffs_nc_write_name(): filename: fail [c0321e20], off: 44480, size: 4
jffs_nc_write_name(): name_offset: 44488
jffs_nc_write_name(): filename: <NULL> [00000000], off: 44488, size: 0
Unable to handle kernel NULL pointer dereference at virtual address
00000000
current->tss.cr3 = 01cc3000, %cr3 = 01cc3000
*pde = 00000000
Oops: 0000
CPU:    0
EIP:    0010:[<c01a7f96>]
EFLAGS: 00010202
(etc)

We're trying to call
err = flash_safe_write(mtd, name_offset, (u_char*) f->name, f->nsize+1 );

when f->name is null which corresponds to "/"
(from dumping out the system's hash table)
*** c->hash[1]: "" (ino: 1, pino: 0)

Amy

To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to majordomo@xxxxxxx.com