From: Dave Chinner <david@fromorbit.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: xfs@oss.sgi.com
Subject: Re: real-time device warning
Date: Thu, 4 Feb 2016 10:40:21 +1100 [thread overview]
Message-ID: <20160203234021.GI459@dastard> (raw)
In-Reply-To: <20160203231259.GA5137@linux.intel.com>
On Wed, Feb 03, 2016 at 04:12:59PM -0700, Ross Zwisler wrote:
> On Thu, Feb 04, 2016 at 08:55:55AM +1100, Dave Chinner wrote:
> > On Wed, Feb 03, 2016 at 09:50:31AM -0700, Ross Zwisler wrote:
> > > I've been doing some more real-time device testing with XFS, and I was able to
> > > get past the BUG I reported here:
> > >
> > > http://www.spinics.net/lists/xfs/msg37445.html
> > >
> > > by setting CONFIG_XFS_DEBUG=n as Dave suggested.
> > >
> > > After that I/O seems to work, although it doesn't look like the DAX mount
> > > option is applied to I/Os that go to the real-time device.
> > >
> > > After the first I/O, though, the following warning is hit:
> > >
> > > [ 413.086897] XFS (ram1): _xfs_buf_ioapply: no ops on block 0xa0/0x8
> >
> > This series:
> >
> > http://oss.sgi.com/archives/xfs/2016-02/msg00017.html
>
> Ah, I wasn't aware of that work. Can you please CC me next time so I can give
> you a Tested-by?
Sure, easy to forget cc's when posting a patchbomb(*), especially when
I've got my own test cases that trigger the problem...
Cheers,
Dave.
(*) I do not allow git-send-email to add cc's from commit message
details because that's a silent information leak just waiting to
happen.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2016-02-03 23:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 16:50 real-time device warning Ross Zwisler
2016-02-03 21:55 ` Dave Chinner
2016-02-03 23:12 ` Ross Zwisler
2016-02-03 23:40 ` Dave Chinner [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=20160203234021.GI459@dastard \
--to=david@fromorbit.com \
--cc=ross.zwisler@linux.intel.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 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.