linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Nikolay Borisov <nborisov@suse.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: lockdep splat in today's master in generic/070
Date: Wed, 1 Mar 2017 09:46:45 +1100	[thread overview]
Message-ID: <20170228224645.GG17542@dastard> (raw)
In-Reply-To: <0e8e52ac-36e4-c8f9-99c7-88e2c9bcb782@suse.com>

On Tue, Feb 28, 2017 at 04:56:01PM +0200, Nikolay Borisov wrote:
> Hello, 
> 
> I've been running xfstest and I can reliably reproduce the following lockdep splat: 

vm_map_ram() has hard coded GFP_KERNEL allocations, it's being
called in GFP_NOFS context, and lockdep doesn't know about
memalloc_noio_save() used by _xfs_buf_map_pages() to work around
the problems in vm_map_ram(). See the comment in
_xfs_buf_map_pages().

-Dave.
-- 
Dave Chinner
david@fromorbit.com

      parent reply	other threads:[~2017-02-28 23:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-28 14:56 lockdep splat in today's master in generic/070 Nikolay Borisov
2017-02-28 15:15 ` Nikolay Borisov
2017-02-28 22:46 ` Dave Chinner [this message]

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=20170228224645.GG17542@dastard \
    --to=david@fromorbit.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=nborisov@suse.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).