From: "Jörn Engel" <joern@logfs.org>
To: srimugunthan dhandapani <srimugunthan.dhandapani@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: logfs unmount bug
Date: Tue, 16 Aug 2011 19:17:07 +0200 [thread overview]
Message-ID: <20110816171707.GU26160@logfs.org> (raw)
In-Reply-To: <CAMjNe_eCqe1kVH-GLb6uo1gVCkH2r49w2Xdws6=jFMOaQRU=mw@mail.gmail.com>
On Fri, 12 August 2011 22:56:02 +0530, srimugunthan dhandapani wrote:
>
> > I wouldn't suspect any code changes to cause the different behaviour.
> > Kernel config and test machine (memsize, etc.) would be more likely
> > candidates. So if you could try the patch and send me the output,
> > that would be useful.
>
> I tried your patches and I also tried on official kernel release 3.0.1.
> I have shared the bonnie output and logs in the below link:
>
> https://docs.google.com/leaf?id=0BycgLWCW61phNjY0ZDg4ZjUtYzAyMy00YTgwLWFlMmItNjlmZWIzMWFlNGUy&hl=en_US
Are you sure you tried the first patch? When I grep for
"logfs_invalidatepage", I only find the oopses, not my debug output.
> I did all my tests with nandsim. Are there any problems using logfs
> with nandsim?
Shouldn't be, unless nandsim is corrupting memory in a peculiar and
reproduceable way on your system.
Jörn
--
Unless something dramatically changes, by 2015 we'll be largely
wondering what all the fuss surrounding Linux was really about.
-- Rob Enderle
WARNING: multiple messages have this Message-ID (diff)
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: Tue, 16 Aug 2011 19:17:07 +0200 [thread overview]
Message-ID: <20110816171707.GU26160@logfs.org> (raw)
In-Reply-To: <CAMjNe_eCqe1kVH-GLb6uo1gVCkH2r49w2Xdws6=jFMOaQRU=mw@mail.gmail.com>
On Fri, 12 August 2011 22:56:02 +0530, srimugunthan dhandapani wrote:
>
> > I wouldn't suspect any code changes to cause the different behaviour.
> > Kernel config and test machine (memsize, etc.) would be more likely
> > candidates. So if you could try the patch and send me the output,
> > that would be useful.
>
> I tried your patches and I also tried on official kernel release 3.0.1.
> I have shared the bonnie output and logs in the below link:
>
> https://docs.google.com/leaf?id=0BycgLWCW61phNjY0ZDg4ZjUtYzAyMy00YTgwLWFlMmItNjlmZWIzMWFlNGUy&hl=en_US
Are you sure you tried the first patch? When I grep for
"logfs_invalidatepage", I only find the oopses, not my debug output.
> I did all my tests with nandsim. Are there any problems using logfs
> with nandsim?
Shouldn't be, unless nandsim is corrupting memory in a peculiar and
reproduceable way on your system.
Jörn
--
Unless something dramatically changes, by 2015 we'll be largely
wondering what all the fuss surrounding Linux was really about.
-- Rob Enderle
--
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-16 17:16 UTC|newest]
Thread overview: 41+ 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-05 16:03 ` Jörn Engel
2011-08-06 14:09 ` srimugunthan dhandapani
2011-08-06 14:09 ` srimugunthan dhandapani
2011-08-08 8:31 ` Jörn Engel
2011-08-08 8:31 ` Jörn Engel
2011-08-08 14:44 ` srimugunthan dhandapani
2011-08-08 14:44 ` srimugunthan dhandapani
2011-08-09 14:58 ` Jörn Engel
2011-08-09 14:58 ` Jörn Engel
2011-08-10 11:06 ` srimugunthan dhandapani
2011-08-10 11:06 ` srimugunthan dhandapani
2011-08-12 9:34 ` Jörn Engel
2011-08-12 9:34 ` Jörn Engel
2011-08-12 17:26 ` srimugunthan dhandapani
2011-08-12 17:26 ` srimugunthan dhandapani
2011-08-16 17:17 ` Jörn Engel [this message]
2011-08-16 17:17 ` Jörn Engel
2011-08-21 21:19 ` srimugunthan dhandapani
2011-08-21 21:19 ` srimugunthan dhandapani
2011-08-26 19:49 ` Jörn Engel
2011-08-26 19:49 ` Jörn Engel
2011-08-29 10:07 ` srimugunthan dhandapani
2011-08-29 10:07 ` srimugunthan dhandapani
2011-08-31 5:58 ` Jörn Engel
2011-08-31 5:58 ` Jörn Engel
2011-08-31 7:22 ` srimugunthan dhandapani
2011-08-31 7:22 ` srimugunthan dhandapani
2011-08-31 7:49 ` Jörn Engel
2011-08-31 7:49 ` Jörn Engel
2011-08-31 12:49 ` srimugunthan dhandapani
2011-08-31 12:49 ` srimugunthan dhandapani
2011-08-31 14:17 ` Jörn Engel
2011-08-31 14:17 ` Jörn Engel
2011-09-01 6:08 ` srimugunthan dhandapani
2011-09-01 6:08 ` srimugunthan dhandapani
2011-09-01 9:46 ` srimugunthan dhandapani
2011-09-01 9:46 ` srimugunthan dhandapani
2011-09-01 21:34 ` Jörn Engel
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=20110816171707.GU26160@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 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.