From: Kalev Lember <kalev@smartlink.ee>
To: skorinkod@mosk.ru
Cc: linux-mtd@lists.infradead.org
Subject: Re: mkfs.ext3 - segmentation fault
Date: Mon, 22 Nov 2004 15:21:34 +0200 [thread overview]
Message-ID: <41A1E7DE.6010005@smartlink.ee> (raw)
In-Reply-To: <200411221339.15109.skorinkod@mosk.ru>
[-- Attachment #1: Type: text/plain, Size: 125 bytes --]
Dmitry Skorinko wrote:
>try current cvs and have same :(( :
>
>
Try the attached patch.
--
Best regards,
Kalev Lember
[-- Attachment #2: inftlmount.c.diff --]
[-- Type: text/plain, Size: 775 bytes --]
Index: inftlmount.c
===================================================================
RCS file: /home/cvs/mtd/drivers/mtd/inftlmount.c,v
retrieving revision 1.15
diff -u -r1.15 inftlmount.c
--- inftlmount.c 5 Nov 2004 21:55:55 -0000 1.15
+++ inftlmount.c 22 Nov 2004 13:17:53 -0000
@@ -389,8 +389,6 @@
struct erase_info *instr = &inftl->instr;
int physblock;
- instr->mtd = inftl->mbd.mtd;
-
DEBUG(MTD_DEBUG_LEVEL3, "INFTL: INFTL_formatblock(inftl=%p,"
"block=%d)\n", inftl, block);
@@ -400,6 +398,7 @@
_first_? */
/* Use async erase interface, test return code */
+ instr->mtd = inftl->mbd.mtd;
instr->addr = block * inftl->EraseSize;
instr->len = inftl->mbd.mtd->erasesize;
/* Erase one physical eraseblock at a time, even though the NAND api
next prev parent reply other threads:[~2004-11-22 13:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 9:11 mkfs.ext3 - segmentation fault Dmitry Skorinko
2004-11-22 9:40 ` Sean Young
2004-11-22 10:24 ` Kalev Lember
2004-11-22 10:39 ` Dmitry Skorinko
2004-11-22 13:21 ` Kalev Lember [this message]
2004-11-22 15:44 ` Dmitry Skorinko
2004-11-22 18:50 ` Dmitry Skorinko
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=41A1E7DE.6010005@smartlink.ee \
--to=kalev@smartlink.ee \
--cc=linux-mtd@lists.infradead.org \
--cc=skorinkod@mosk.ru \
/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.