From 9411e40603f995f28321103c6a38a40c858812a2 Mon Sep 17 00:00:00 2001 From: Werner Almesberger Date: Fri, 9 Jan 2009 04:32:50 +0000 Subject: [PATCH] phase2: block init buggy x Is it really correct to set last_block_init to the next entry ? It would seem that the current (i.e., bogus) values are then just used without further ado. Untested. Not-Yet-Signed-off-by: Werner Almesberger --- qiboot/src/phase2.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/qiboot/src/phase2.c b/qiboot/src/phase2.c index 34ed4d8..6628bf0 100644 --- a/qiboot/src/phase2.c +++ b/qiboot/src/phase2.c @@ -116,7 +116,7 @@ static int do_block_init(void) puts("block device init failed\n"); if (this_kernel->block_init != last_block_init) indicate(UI_IND_MOUNT_FAIL); - last_block_init = this_kernel[1].block_init; + last_block_init = NULL; return 0; } last_block_init = this_kernel->block_init;