From: Dave Chinner <david@fromorbit.com>
To: Gavin Guo <gavin.guo@canonical.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, xfs@oss.sgi.com
Subject: Re: Possible memory allocation deadlock in kmem_alloc and hung task in xfs_log_commit_cil and xlog_cil_push
Date: Wed, 8 Jul 2015 09:37:43 +1000 [thread overview]
Message-ID: <20150707233743.GZ7943@dastard> (raw)
In-Reply-To: <CA+eFSM30A1V7j4CYJOyLSN7V7REHt0hrxteU1dVRw4HQZLmuxw@mail.gmail.com>
On Tue, Jul 07, 2015 at 05:29:43PM +0800, Gavin Guo wrote:
> Hi all,
>
> Recently, we observed that there is the error message in
> Ubuntu-3.13.0-48.80:
>
> "XFS: possible memory allocation deadlock in kmem_alloc (mode:0x8250)"
>
> repeatedly shows in the dmesg. Temporarily, our workaround is to tune the
> parameters, such as, vfs_cache_pressure, min_free_kbytes, and dirty_ratio.
>
> And we also found that there are different error messages regarding the
> hung tasks which happened in xfs_log_commit_cil and xlog_cil_push.
>
> The log is available at: http://paste.ubuntu.com/11835007/
>
> The following link seems the same problem we suffered:
>
> XFS hangs with XFS: possible memory allocation deadlock in kmem_alloc
> http://oss.sgi.com/archives/xfs/2015-03/msg00172.html
>
> I read the mail and found that there might be some modification regarding
> to move the memory allocation outside the ctx lock. And I also read the
> latest patch from February of 2015 to see if there is any new change
> about that. Unfortunately, I didn't find anything regarding the change (may
> be I'm not familiar with the XFS, so didn't find the commit). If it's
> possible for someone who is familiar with the code to point out the commits
> related to the bug if already exist or any status about the plan.
No commits - the approach I thought we might be able to take to
avoid the problem didn't work out. I have another idea of how we
might solve the problem, but I haven't ad a chance to prototype it
yet.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Dave Chinner <david@fromorbit.com>
To: Gavin Guo <gavin.guo@canonical.com>
Cc: xfs@oss.sgi.com, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Possible memory allocation deadlock in kmem_alloc and hung task in xfs_log_commit_cil and xlog_cil_push
Date: Wed, 8 Jul 2015 09:37:43 +1000 [thread overview]
Message-ID: <20150707233743.GZ7943@dastard> (raw)
In-Reply-To: <CA+eFSM30A1V7j4CYJOyLSN7V7REHt0hrxteU1dVRw4HQZLmuxw@mail.gmail.com>
On Tue, Jul 07, 2015 at 05:29:43PM +0800, Gavin Guo wrote:
> Hi all,
>
> Recently, we observed that there is the error message in
> Ubuntu-3.13.0-48.80:
>
> "XFS: possible memory allocation deadlock in kmem_alloc (mode:0x8250)"
>
> repeatedly shows in the dmesg. Temporarily, our workaround is to tune the
> parameters, such as, vfs_cache_pressure, min_free_kbytes, and dirty_ratio.
>
> And we also found that there are different error messages regarding the
> hung tasks which happened in xfs_log_commit_cil and xlog_cil_push.
>
> The log is available at: http://paste.ubuntu.com/11835007/
>
> The following link seems the same problem we suffered:
>
> XFS hangs with XFS: possible memory allocation deadlock in kmem_alloc
> http://oss.sgi.com/archives/xfs/2015-03/msg00172.html
>
> I read the mail and found that there might be some modification regarding
> to move the memory allocation outside the ctx lock. And I also read the
> latest patch from February of 2015 to see if there is any new change
> about that. Unfortunately, I didn't find anything regarding the change (may
> be I'm not familiar with the XFS, so didn't find the commit). If it's
> possible for someone who is familiar with the code to point out the commits
> related to the bug if already exist or any status about the plan.
No commits - the approach I thought we might be able to take to
avoid the problem didn't work out. I have another idea of how we
might solve the problem, but I haven't ad a chance to prototype it
yet.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2015-07-07 23:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 9:29 Possible memory allocation deadlock in kmem_alloc and hung task in xfs_log_commit_cil and xlog_cil_push Gavin Guo
2015-07-07 9:29 ` Gavin Guo
2015-07-07 23:37 ` Dave Chinner [this message]
2015-07-07 23:37 ` Dave Chinner
2015-07-08 12:34 ` Gavin Guo
2015-07-08 12:34 ` Gavin Guo
2015-07-08 14:06 ` juncheng bai
2015-07-08 14:06 ` juncheng bai
2015-07-09 1:58 ` Dave Chinner
2015-07-09 1:58 ` Dave Chinner
2015-08-28 12:54 ` Gavin Guo
2015-08-28 12:54 ` Gavin Guo
2015-08-29 22:31 ` Dave Chinner
2015-08-29 22:31 ` Dave Chinner
2015-08-31 7:33 ` Gavin Guo
2015-08-31 7:33 ` Gavin Guo
2015-12-07 16:46 ` Gavin Guo
2015-12-07 16:46 ` Gavin Guo
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=20150707233743.GZ7943@dastard \
--to=david@fromorbit.com \
--cc=gavin.guo@canonical.com \
--cc=linux-kernel@vger.kernel.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.