From: jim owens <jowens@hp.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [RFC] Early look at btrfs directIO read code
Date: Mon, 24 Aug 2009 13:57:39 -0400 [thread overview]
Message-ID: <4A92D493.3070804@hp.com> (raw)
In-Reply-To: <4A92853E.8010800@hp.com>
Arrrgh...
If I did not already scare you enough to stay away from trying
this code, I already hit another bug. Proving the axiom that
you will find a bad bug as soon as you send your code to anyone.
* non-inline file size must be a multiple of device sector size.
jim
next prev parent reply other threads:[~2009-08-24 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 12:19 [RFC] Early look at btrfs directIO read code jim owens
2009-08-24 17:57 ` jim owens [this message]
2009-09-02 21:48 ` jim owens
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=4A92D493.3070804@hp.com \
--to=jowens@hp.com \
--cc=linux-btrfs@vger.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 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.