From: Jens Axboe <jens.axboe@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] block bits for 2.6.29-rc5
Date: Fri, 20 Feb 2009 08:26:35 +0100 [thread overview]
Message-ID: <20090220072635.GR29783@kernel.dk> (raw)
In-Reply-To: <20090219185539.GI29783@kernel.dk>
On Thu, Feb 19 2009, Jens Axboe wrote:
> On Thu, Feb 19 2009, Christoph Hellwig wrote:
> > On Wed, Feb 18, 2009 at 03:41:06PM +0100, Jens Axboe wrote:
> > > Hi Linus,
> > >
> > > One trivial patch, otherwise it's all bug fixes or regressions. Please
> > > pull.
> >
> > Any chance you could look into the barrier fail warning spew regression
> > introduced early in the 2.6.29 circle?
>
> Yep, will get fixed in the next round. There were just a few important
> fixes queued up that I wanted in -rc6.
It seems to work fine for me, tested with a modified sd that doesn't
have barrier support and loop:
Filesystem "sdc1": Disabling barriers, trial barrier write failed
XFS mounting filesystem sdc1
and
Filesystem "loop0": Disabling barriers, trial barrier write failed
XFS mounting filesystem loop0
No extra failure warnings on the barrier IO itself. What device do you
see this on?
--
Jens Axboe
next prev parent reply other threads:[~2009-02-20 7:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 14:41 [GIT PULL] block bits for 2.6.29-rc5 Jens Axboe
2009-02-19 18:54 ` Christoph Hellwig
2009-02-19 18:55 ` Jens Axboe
2009-02-20 7:26 ` Jens Axboe [this message]
2009-02-24 13:45 ` Christoph Hellwig
2009-02-20 1:07 ` Andrew Morton
2009-02-20 16:40 ` Jens Axboe
2009-02-20 16:50 ` Miller, Mike (OS Dev)
2009-02-20 16:53 ` Jens Axboe
2009-02-20 18:51 ` Miller, Mike (OS Dev)
2009-02-23 11:09 ` Jens Axboe
2009-02-23 15:00 ` Miller, Mike (OS Dev)
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=20090220072635.GR29783@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).