From: Dave Jones <davej@codemonkey.org.uk>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <jbacik@fb.com>,
David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: btrfs_direct_IO oops
Date: Mon, 10 Oct 2016 13:17:04 -0400 [thread overview]
Message-ID: <20161010171704.skyaq2sy6de7ghn6@codemonkey.org.uk> (raw)
In-Reply-To: <20161010155503.GZ19539@ZenIV.linux.org.uk>
On Mon, Oct 10, 2016 at 04:55:03PM +0100, Al Viro wrote:
> > WARNING: CPU: 1 PID: 13581 at lib/iov_iter.c:327 sanity+0x102/0x150
> > CPU: 1 PID: 13581 Comm: trinity-c17 Not tainted 4.8.0-think+ #9
> > ffffc90000963ae8
> > ffffffffb93e22d1
> > 0000000000000000
> > 0000000000000000
> >
> > ffffffffb9c1e1cb
> > ffffffffb93fa5b2
> > ffffc90000963b28
> > ffffffffb908b010
> >
> > 00000147d43c0e7f
> > ffffffffb9c1e1cb
> > 0000000000000147
> > 0000000000000010
>
> What are these from? Confused...
That's the stack I think. I don't know why it started printing all weird..
> [via splice_direct_to_actor()]
>
> Hmmm... I think I see it. Could you try the following (on top of debugging
> in lib/iov_iter.c) and see if anything triggers?
Been running for an hour without incident so far, so this looks promising.
I'll follow-up if anything jumps out, but normally I'd have seen this by now.
Dave
prev parent reply other threads:[~2016-10-10 17:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-08 18:08 btrfs_direct_IO oops Dave Jones
2016-10-08 18:29 ` Al Viro
2016-10-08 23:20 ` Dave Jones
2016-10-09 15:11 ` Dave Jones
2016-10-10 3:43 ` Al Viro
2016-10-10 13:11 ` Dave Jones
2016-10-10 15:55 ` Al Viro
2016-10-10 17:17 ` Dave Jones [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=20161010171704.skyaq2sy6de7ghn6@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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).