From: "Jörn Engel" <joern@logfs.org>
To: srimugunthan dhandapani <srimugunthan.dhandapani@gmail.com>
Cc: linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org
Subject: Re: logfs unmount bug
Date: Mon, 8 Aug 2011 10:31:07 +0200 [thread overview]
Message-ID: <20110808083107.GN26160@logfs.org> (raw)
In-Reply-To: <CAMjNe_c0qZ+opwHtO3AhD60v1p8-gpDLVykJoKo8oD4zNGk9kA@mail.gmail.com>
On Sat, 6 August 2011 19:39:42 +0530, srimugunthan dhandapani wrote:
>
> Thanks. I tested your patch with nandsim and i was able to unmount
> without any problems.
Good.
> I did some more tests on logfs with nandsim. I ran into some crashes
> when i used bonnie and tiobench.
> Following are the steps i followed with bonnie. Also kernel messages
> are below that.
>
> 1. sudo modprobe mtdblock
> 2. sudo modprobe nandsim
> 3. sudo modprobe zlib_deflate
> 4. sudo insmod logfs/logfs.ko
> 5. sudo flash_eraseall /dev/mtd0
> 6. sudo logfsprogs/mklogfs /dev/mtdblock0
> 7. sudo mount -t logfs /dev/mtdblock0 /mnt/flash_drive/
> 8. sudo chown srimugunthan /mnt/flash_drive/
> 9. bonnie -d /mnt/flash_drive/ -s 100 -r 50
>
> kernel oops with bonnie
> ( A different kind of crash happened with tiobench command
> ./tiobench.pl --dir /mnt/flash_drive/ --size 25 --threads 4)
Not good. So far I managed to see a (the?) tiobench bug once, but
couldn't make it reproduceable. Nor could I reproduce the bonnie bug.
Once the bugs are reproduceable, even my feeble eyes can usually spot
the cause sooner or later. With a backtrace alone and no idea what
internal state it depends on, life is much harder.
Just in case this depends on device size or erase size, can you send
me the mklogfs output?
> do_invalidatepage+0x28/0x30
> truncate_inode_page+0x92/0xb0
> truncate_inode_pages_range+0x177/0x4f0
> truncate_inode_pages+0x15/0x20
> truncate_pagecache+0x4f/0x70
> truncate_setsize+0x1f/0x30
> vmtruncate+0x3e/0x60
> logfs_truncate+0x263/0x2a0 [logfs]
> logfs_evict_inode+0xdc/0x1d0 [logfs]
> ? do_raw_spin_unlock+0x5e/0xb0
> evict+0xa9/0x1a0
> iput+0xfd/0x200
> dentry_iput+0x98/0xe0
> dput+0x19e/0x2a0
> fput+0x182/0x230
> filp_close+0x66/0xa0
> sys_close+0xb9/0x120
> system_call_fastpath+0x16/0x1b
We still had a struct logfs_block with some reserved bytes attached to
the page when logfs called into vmtruncate. I'll see whether that
makes any sense at all. At the very least, some more documentation
would be in order.
Jörn
--
"[One] doesn't need to know [...] how to cause a headache in order
to take an aspirin."
-- Scott Culp, Manager of the Microsoft Security Response Center, 2001
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-08-08 8:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 19:35 logfs unmount bug srimugunthan dhandapani
2011-08-05 16:03 ` Jörn Engel
2011-08-06 14:09 ` srimugunthan dhandapani
2011-08-08 8:31 ` Jörn Engel [this message]
2011-08-08 14:44 ` srimugunthan dhandapani
2011-08-09 14:58 ` Jörn Engel
2011-08-10 11:06 ` srimugunthan dhandapani
2011-08-12 9:34 ` Jörn Engel
2011-08-12 17:26 ` srimugunthan dhandapani
2011-08-16 17:17 ` Jörn Engel
2011-08-21 21:19 ` srimugunthan dhandapani
2011-08-26 19:49 ` Jörn Engel
2011-08-29 10:07 ` srimugunthan dhandapani
2011-08-31 5:58 ` Jörn Engel
2011-08-31 7:22 ` srimugunthan dhandapani
2011-08-31 7:49 ` Jörn Engel
2011-08-31 12:49 ` srimugunthan dhandapani
2011-08-31 14:17 ` Jörn Engel
2011-09-01 6:08 ` srimugunthan dhandapani
2011-09-01 9:46 ` srimugunthan dhandapani
2011-09-01 21:34 ` Jörn Engel
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=20110808083107.GN26160@logfs.org \
--to=joern@logfs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=srimugunthan.dhandapani@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).