From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: avoid direct write if we fall back to buffered v3
Date: Fri, 30 Apr 2010 13:52:43 -0700 [thread overview]
Message-ID: <20100430205243.GD1938@mail.oracle.com> (raw)
In-Reply-To: <20100430204705.GC1938@mail.oracle.com>
On Fri, Apr 30, 2010 at 01:47:05PM -0700, Joel Becker wrote:
> Have you tested this version? I got a compile error:
I want to be clear - has this patch (v3) been run against the
fsstress that caused the bug report in the first place? Does the
fsstress now pass? Let me know so I can send it upstream.
Joel
--
Life's Little Instruction Book #314
"Never underestimate the power of forgiveness."
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2010-04-30 20:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-17 9:49 [Ocfs2-devel] [PATCH] ocfs2: avoid direct write if we fall back to buffered v3 Li Dongyang
2010-04-26 9:56 ` Li Dongyang
2010-04-26 22:24 ` Joel Becker
2010-04-30 20:37 ` Mark Fasheh
2010-04-30 20:47 ` Joel Becker
2010-04-30 20:52 ` Joel Becker [this message]
2010-05-04 1:37 ` Li Dongyang
2010-05-04 1:47 ` Joel Becker
2010-05-04 2:10 ` Li Dongyang
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=20100430205243.GD1938@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=ocfs2-devel@oss.oracle.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.