Re: XFS WARN_ON in xfs_vm_writepage

2014-06-23 Thread Dave Chinner
On Mon, Jun 23, 2014 at 04:27:14PM -0400, Dave Jones wrote: > On Thu, Jun 19, 2014 at 12:03:40PM +1000, Dave Chinner wrote: > > On Fri, Jun 13, 2014 at 10:19:25AM -0400, Dave Jones wrote: > > > On Fri, Jun 13, 2014 at 04:26:45PM +1000, Dave Chinner wrote: > > > > > > > > 970 if (WARN_

Re: XFS WARN_ON in xfs_vm_writepage

2014-06-23 Thread Dave Jones
On Thu, Jun 19, 2014 at 12:03:40PM +1000, Dave Chinner wrote: > On Fri, Jun 13, 2014 at 10:19:25AM -0400, Dave Jones wrote: > > On Fri, Jun 13, 2014 at 04:26:45PM +1000, Dave Chinner wrote: > > > > > > 970 if (WARN_ON_ONCE((current->flags & > > > > (PF_MEMALLOC|PF_KSWAPD)) == > > >

Re: XFS WARN_ON in xfs_vm_writepage

2014-06-18 Thread Dave Chinner
On Fri, Jun 13, 2014 at 10:19:25AM -0400, Dave Jones wrote: > On Fri, Jun 13, 2014 at 04:26:45PM +1000, Dave Chinner wrote: > > > > 970 if (WARN_ON_ONCE((current->flags & (PF_MEMALLOC|PF_KSWAPD)) > > > == > > > 971 PF_MEMALLOC)) > > > > What were you running at t

Re: XFS WARN_ON in xfs_vm_writepage

2014-06-13 Thread Dave Jones
On Fri, Jun 13, 2014 at 04:26:45PM +1000, Dave Chinner wrote: > > 970 if (WARN_ON_ONCE((current->flags & (PF_MEMALLOC|PF_KSWAPD)) == > > 971 PF_MEMALLOC)) > > What were you running at the time? The XFS warning is there to > indicate that memory reclaim is doing so

Re: XFS WARN_ON in xfs_vm_writepage

2014-06-12 Thread Dave Chinner
[cc linux-mm] On Fri, Jun 13, 2014 at 01:16:31AM -0400, Dave Jones wrote: > Just hit this on Linus' tree from earlier this afternoon.. > > WARNING: CPU: 3 PID: 19721 at fs/xfs/xfs_aops.c:971 > xfs_vm_writepage+0x5ce/0x630 [xfs]() > CPU: 3 PID: 19721 Comm: trinity-c61 Not tainted 3.15.0+ #3 > 00

XFS WARN_ON in xfs_vm_writepage

2014-06-12 Thread Dave Jones
Just hit this on Linus' tree from earlier this afternoon.. WARNING: CPU: 3 PID: 19721 at fs/xfs/xfs_aops.c:971 xfs_vm_writepage+0x5ce/0x630 [xfs]() CPU: 3 PID: 19721 Comm: trinity-c61 Not tainted 3.15.0+ #3 0009 4f70ab82 8801d5ebf578 8373215c fff