From: Ferenc Wagner <wferi@niif.hu>
To: Christoph Hellwig <hch@infradead.org>
Cc: Peter Staubach <staubach@redhat.com>,
Miklos Szeredi <mszeredi@suse.cz>, Ray Lee <ray-lk@madrabbit.org>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: mmap vs mtime in 2.6.26 and up
Date: Thu, 15 Oct 2009 02:08:22 +0200 [thread overview]
Message-ID: <87oco94iyx.fsf@tac.ki.iif.hu> (raw)
In-Reply-To: <20090926131043.GA25204@infradead.org> (Christoph Hellwig's message of "Sat, 26 Sep 2009 09:10:43 -0400")
Christoph Hellwig <hch@infradead.org> writes:
> On Fri, Sep 25, 2009 at 02:47:42PM +0200, Ferenc Wagner wrote:
>
>> I added some fresh test results to
>> http://bugzilla.kernel.org/show_bug.cgi?id=2645. In short, under
>> 2.6.30-rc8 the test program reports full failure on XFS and RAMFS,
>> full success on EXT3, VFAT and ReiserFS, and mixed results on TMPFS:
>
> There's a patch queued up for inclusion in 2.6.32 to work around this
> issue in XFS. The lack of a proper callout from the VFS still makes
> this a much less than ideal solution.
Great, anyway! Somehow I managed to gloss over this mail until now,
but happened to test 2.6.32-rc4 and found the issue fixed. At least
for XFS, as my latest addition to the bug report details it. Thank
you very much for taking care of this issue!
--
Regards,
Feri.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-10-15 0:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <874ovws94s.fsf@tac.ki.iif.hu>
[not found] ` <87ljp2v6vt.fsf@tac.ki.iif.hu>
2009-05-12 15:37 ` mmap vs mtime in 2.6.26 and up Ray Lee
2009-05-12 15:53 ` Christoph Hellwig
2009-05-15 16:40 ` Ferenc Wagner
2009-05-15 16:50 ` Christoph Hellwig
2009-05-18 11:43 ` Christoph Hellwig
2009-07-22 17:52 ` Ferenc Wagner
2009-09-25 12:47 ` Ferenc Wagner
2009-09-26 13:10 ` Christoph Hellwig
2009-10-15 0:08 ` Ferenc Wagner [this message]
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=87oco94iyx.fsf@tac.ki.iif.hu \
--to=wferi@niif.hu \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@suse.cz \
--cc=ray-lk@madrabbit.org \
--cc=staubach@redhat.com \
--cc=xfs@oss.sgi.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