From: JiSheng Zhang <jszhang3@gmail.com>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, stable@kernel.org
Subject: Re: [BUG]2.6.27.y some contents lost after writing to mmaped file
Date: Tue, 17 Nov 2009 19:07:33 +0800 [thread overview]
Message-ID: <2df346410911170307y1eb1f209se01d0cf456bb0bc6@mail.gmail.com> (raw)
In-Reply-To: <20091117015655.GA8683@suse.de>
Hi Greg,
2009/11/17 Greg KH <gregkh@suse.de>:
>>
>> 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?
I have tested on both 2.6.27.12 and 2.6.27.39, fsx-linux all failed.
>
>> 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
> Are you sure that the LTP is correct? It wouldn't be the first time it
> wasn't...
hmmm, I read the source again, IMHO it is correct.
>
> thanks,
>
> greg k-h
>
One more findings: If I add "return" at the beginning of domapwrite,
no fail found yet.
Regards,
Jisheng
--
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 11:07 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 [this message]
2009-11-17 12:36 ` Chris Mason
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=2df346410911170307y1eb1f209se01d0cf456bb0bc6@mail.gmail.com \
--to=jszhang3@gmail.com \
--cc=gregkh@suse.de \
--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