[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Mon, 10 Oct 2016 13:17:04 -0400
From: Dave Jones <davej@...emonkey.org.uk>
To: Al Viro <viro@...IV.linux.org.uk>
Cc: Chris Mason <clm@...com>, Josef Bacik <jbacik@...com>,
David Sterba <dsterba@...e.com>, linux-btrfs@...r.kernel.org,
Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: btrfs_direct_IO oops
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
Powered by blists - more mailing lists