From: Chris Mason <chris.mason@oracle.com>
To: Greg KH <gregkh@suse.de>
Cc: JiSheng Zhang <jszhang3@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
stable@kernel.org, jack@suse.cz
Subject: Re: [BUG]2.6.27.y some contents lost after writing to mmaped file
Date: Tue, 17 Nov 2009 07:36:22 -0500 [thread overview]
Message-ID: <20091117123622.GI27677@think> (raw)
In-Reply-To: <20091117015655.GA8683@suse.de>
On Mon, Nov 16, 2009 at 05:56:55PM -0800, Greg KH wrote:
> On Mon, Nov 16, 2009 at 11:38:57AM +0800, JiSheng Zhang wrote:
> > Hi,
> >
> > I triggered a failure in an fs test with fsx-linux from ltp. It seems that
> > fsx-linux failed at mmap->write sequence.
> >
> > Tested kernel is 2.6.27.12 and 2.6.27.39
>
> Does this work on any kernel you have tested? Or is it a regression?
>
> > Tested file system: ext3, tmpfs.
> > IMHO, it impacts all file systems.
> >
> > Some fsx-linux log is:
> >
> > READ BAD DATA: offset = 0x2771b, size = 0xa28e
> > OFFSET GOOD BAD RANGE
> > 0x287e0 0x35c9 0x15a9 0x80
> > operation# (mod 256) for the bad datamay be 21
> > ...
> > 7828: 1257514978.306753 READ 0x23dba thru 0x25699 (0x18e0 bytes)
> > 7829: 1257514978.306899 MAPWRITE 0x27eeb thru 0x2a516 (0x262c bytes)
> > ******WWWW
> > 7830: 1257514978.307504 READ 0x2771b thru 0x319a8 (0xa28e bytes)
> > ***RRRR***
> > Correct content saved for comparison
> > ...
>
> Are you sure that the LTP is correct? It wouldn't be the first time it
> wasn't...
I'm afraid fsx usually finds bugs. I thought Jan Kara recently fixed
something here in ext3, does 2.6.32-rc work?
-chris
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-11-17 12:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 3:38 JiSheng Zhang
2009-11-17 1:56 ` Greg KH
2009-11-17 11:07 ` JiSheng Zhang
2009-11-17 12:36 ` Chris Mason [this message]
2009-11-17 19:06 ` Jan Kara
2009-11-18 14:17 ` JiSheng Zhang
2009-11-19 14:43 ` Jan Kara
2009-11-19 15:25 ` Russell King - ARM Linux
2009-11-20 3:41 ` JiSheng Zhang
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=20091117123622.GI27677@think \
--to=chris.mason@oracle.com \
--cc=gregkh@suse.de \
--cc=jack@suse.cz \
--cc=jszhang3@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stable@kernel.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