public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Artem B. Bityuckiy" <abityuckiy@yandex.ru>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: BUG in JFFS2
Date: Mon, 15 Nov 2004 12:41:31 +0300	[thread overview]
Message-ID: <419879CB.3010209@yandex.ru> (raw)
In-Reply-To: <1100508326.8015.57.camel@localhost.localdomain>



David Woodhouse wrote:
> On Mon, 2004-11-15 at 11:27 +0300, Artem B. Bityuckiy wrote:
> 
>>Hello,
>>
>>I've hit on bug in JFFS2, but I can not reproduce it easilly yet. I have 
>>  stess test which in general creates files, deletes them, creates 
>>directories and deletes them, and so on so on. When I run this test 
>>nightly, I see the following error when I come at work in the morning:
>>
>>kernel BUG at 
>>/tester/linux/linux-2.6.8-1.521up-custom-nopreempt/fs/jffs2/gc.c:1164!
> 
> 
> In my copy of v1.137 there's three instances of BUG_ON() around there,
> but none at line 1164. They're at lines 116[123]. 
I have the lastest MTD snapshot, v1.140. This is BUG_ON(end > 
JFFS2_F_I_SIZE(f));

> 
> Start by changing it from a simple BUG_ON() to a printk saying precisely
> what went wrong and giving all the other information which might be
> relevant. If you can just trap into a debugger when it happens, that's
> even better.
I'll do this as soos as I have done other pending JFFS2 tasks :-) I 
think I'll insert useful printkeyss there since now I have no configured 
environment to use debugger.

-- 
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.

      reply	other threads:[~2004-11-15  9:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-15  8:27 BUG in JFFS2 Artem B. Bityuckiy
2004-11-15  8:45 ` David Woodhouse
2004-11-15  9:41   ` Artem B. Bityuckiy [this message]

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=419879CB.3010209@yandex.ru \
    --to=abityuckiy@yandex.ru \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox