From: Dave Jones <davej@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-mm@kvack.org, Linux Kernel <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: XFS WARN_ON in xfs_vm_writepage
Date: Fri, 13 Jun 2014 10:19:25 -0400 [thread overview]
Message-ID: <20140613141925.GA24199@redhat.com> (raw)
In-Reply-To: <20140613062645.GZ9508@dastard>
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 something it shouldn't (i.e.
> dirty page writeback from direct reclaim), so this is one for the mm
> folk to work out...
Trinity had driven the machine deeply into swap, and the oom killer was
kicking in pretty often. Then this happened.
Dave
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Dave Jones <davej@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com, Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: XFS WARN_ON in xfs_vm_writepage
Date: Fri, 13 Jun 2014 10:19:25 -0400 [thread overview]
Message-ID: <20140613141925.GA24199@redhat.com> (raw)
In-Reply-To: <20140613062645.GZ9508@dastard>
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 something it shouldn't (i.e.
> dirty page writeback from direct reclaim), so this is one for the mm
> folk to work out...
Trinity had driven the machine deeply into swap, and the oom killer was
kicking in pretty often. Then this happened.
Dave
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Dave Jones <davej@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com, Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: XFS WARN_ON in xfs_vm_writepage
Date: Fri, 13 Jun 2014 10:19:25 -0400 [thread overview]
Message-ID: <20140613141925.GA24199@redhat.com> (raw)
In-Reply-To: <20140613062645.GZ9508@dastard>
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 something it shouldn't (i.e.
> dirty page writeback from direct reclaim), so this is one for the mm
> folk to work out...
Trinity had driven the machine deeply into swap, and the oom killer was
kicking in pretty often. Then this happened.
Dave
next prev parent reply other threads:[~2014-06-13 14:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 5:16 XFS WARN_ON in xfs_vm_writepage Dave Jones
2014-06-13 5:16 ` Dave Jones
2014-06-13 6:26 ` Dave Chinner
2014-06-13 6:26 ` Dave Chinner
2014-06-13 6:26 ` Dave Chinner
2014-06-13 14:19 ` Dave Jones [this message]
2014-06-13 14:19 ` Dave Jones
2014-06-13 14:19 ` Dave Jones
2014-06-19 2:03 ` Dave Chinner
2014-06-19 2:03 ` Dave Chinner
2014-06-19 2:03 ` Dave Chinner
2014-06-23 20:27 ` Dave Jones
2014-06-23 20:27 ` Dave Jones
2014-06-23 20:27 ` Dave Jones
2014-06-24 1:02 ` Dave Chinner
2014-06-24 1:02 ` Dave Chinner
2014-06-24 1:02 ` Dave Chinner
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=20140613141925.GA24199@redhat.com \
--to=davej@redhat.com \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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.