linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maciej Rutecki <maciej.rutecki@gmail.com>
To: liubo <liubo2009@cn.fujitsu.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-btrfs@vger.kernel.org
Subject: Re: [BUG] btrfs: report a direct-IO bug
Date: Fri, 7 May 2010 16:00:35 +0200	[thread overview]
Message-ID: <201005071600.36060.maciej.rutecki@gmail.com> (raw)
In-Reply-To: <4BE21FC1.1010901@cn.fujitsu.com>

On czwartek, 6 maja 2010 o 03:47:45 liubo wrote:
> When we tested the series of jim owens' direct-IO patch, a bug occured.
> 
> It could be reproduced on a 2.6.34-rc6 kernel with
> direct-IO patch by the following steps...
> 

I created a Bugzilla entry at 
https://bugzilla.kernel.org/show_bug.cgi?id=15935
for your bug report, please add your address to the CC list in there, thanks!
 

-- 
Maciej Rutecki
http://www.maciek.unixy.pl

      parent reply	other threads:[~2010-05-07 14:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06  1:47 [BUG] btrfs: report a direct-IO bug liubo
2010-05-06  1:56 ` Josef Bacik
2010-05-07 14:00 ` Maciej Rutecki [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=201005071600.36060.maciej.rutecki@gmail.com \
    --to=maciej.rutecki@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liubo2009@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).