linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: JiSheng Zhang <jszhang3@gmail.com>
Cc: Jan Kara <jack@suse.cz>, Greg KH <gregkh@suse.de>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	stable@kernel.org, Chris Mason <chris.mason@oracle.com>,
	linux-arm@lists.infradead.org
Subject: Re: [BUG]2.6.27.y some contents lost after writing to mmaped file
Date: Thu, 19 Nov 2009 15:25:48 +0000	[thread overview]
Message-ID: <20091119152548.GA22232@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20091118221756.367c005e@ustc>

On Wed, Nov 18, 2009 at 10:17:56PM +0800, JiSheng Zhang wrote:
> I forget to mention that the test were done on an arm board with 64M ram. 
> I have tested fsx-linux again on pc, it seems that failure go away.

Could provide a full bug report please, as in:

- CPU type
- is it a SMP CPU
- are you running a SMP kernel
- board type

All the above can be provided by supplying the kernel boot messages
(preferred)

- the storage peripheral being used for this test
- is DMA being used for this periperal
- any additional block layers (eg, lvm, dm, md)
- filesystem type

Plus, please cc suspected ARM problems to the ARM _kernel_ mailing list.

Thanks.

--
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>

  parent reply	other threads:[~2009-11-19 15:26 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
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 [this message]
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=20091119152548.GA22232@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=chris.mason@oracle.com \
    --cc=gregkh@suse.de \
    --cc=jack@suse.cz \
    --cc=jszhang3@gmail.com \
    --cc=linux-arm@lists.infradead.org \
    --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