From: Dave Chinner <david@fromorbit.com>
To: Dave Jones <davej@redhat.com>,
xfs@oss.sgi.com, Linux Kernel <linux-kernel@vger.kernel.org>
Cc: linux-mm@kvack.org
Subject: Re: XFS WARN_ON in xfs_vm_writepage
Date: Fri, 13 Jun 2014 16:26:45 +1000 [thread overview]
Message-ID: <20140613062645.GZ9508@dastard> (raw)
In-Reply-To: <20140613051631.GA9394@redhat.com>
[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
> 0000000000000009 000000004f70ab82 ffff8801d5ebf578 ffffffff8373215c
> 0000000000000000 ffff8801d5ebf5b0 ffffffff8306f7cd ffff88023dd543e0
> ffffea000254a3c0 ffff8801d5ebf820 ffffea000254a3e0 ffff8801d5ebf728
> Call Trace:
> [<ffffffff8373215c>] dump_stack+0x4e/0x7a
> [<ffffffff8306f7cd>] warn_slowpath_common+0x7d/0xa0
> [<ffffffff8306f8fa>] warn_slowpath_null+0x1a/0x20
> [<ffffffffc023068e>] xfs_vm_writepage+0x5ce/0x630 [xfs]
> [<ffffffff8373f1ab>] ? preempt_count_sub+0xab/0x100
> [<ffffffff83347315>] ? __percpu_counter_add+0x85/0xc0
> [<ffffffff8316f759>] shrink_page_list+0x8f9/0xb90
> [<ffffffff83170123>] shrink_inactive_list+0x253/0x510
> [<ffffffff83170c93>] shrink_lruvec+0x563/0x6c0
> [<ffffffff83170e2b>] shrink_zone+0x3b/0x100
> [<ffffffff831710e1>] shrink_zones+0x1f1/0x3c0
> [<ffffffff83171414>] try_to_free_pages+0x164/0x380
> [<ffffffff83163e52>] __alloc_pages_nodemask+0x822/0xc90
> [<ffffffff83169eb2>] ? pagevec_lru_move_fn+0x122/0x140
> [<ffffffff831abeff>] alloc_pages_vma+0xaf/0x1c0
> [<ffffffff8318a931>] handle_mm_fault+0xa31/0xc50
> [<ffffffff831845c0>] ? follow_page_mask+0x1f0/0x320
> [<ffffffff8318491b>] __get_user_pages+0x22b/0x660
> [<ffffffff831b5093>] ? kmem_cache_alloc+0x183/0x210
> [<ffffffff8318ce7e>] __mlock_vma_pages_range+0x9e/0xd0
> [<ffffffff8318d6ba>] __mm_populate+0xca/0x180
> [<ffffffff83179033>] vm_mmap_pgoff+0xd3/0xe0
> [<ffffffff8318fbd6>] SyS_mmap_pgoff+0x116/0x2c0
> [<ffffffff83011ced>] ? syscall_trace_enter+0x14d/0x2a0
> [<ffffffff830084c2>] SyS_mmap+0x22/0x30
> [<ffffffff837436ef>] tracesys+0xdd/0xe2
>
>
> 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...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2014-06-13 6:27 UTC|newest]
Thread overview: 6+ 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 6:26 ` Dave Chinner [this message]
2014-06-13 14:19 ` Dave Jones
2014-06-19 2:03 ` Dave Chinner
2014-06-23 20:27 ` Dave Jones
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=20140613062645.GZ9508@dastard \
--to=david@fromorbit.com \
--cc=davej@redhat.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 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).