From: Dave Chinner <david@fromorbit.com>
To: "Michael L. Semon" <mlsemon35@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Lockdep for 3.10.0+ for rm of kernel git...
Date: Mon, 15 Jul 2013 11:24:41 +1000 [thread overview]
Message-ID: <20130715012441.GG5228@dastard> (raw)
In-Reply-To: <51E1F1F4.40500@gmail.com>
On Sat, Jul 13, 2013 at 08:33:56PM -0400, Michael L. Semon wrote:
> Hi! Here's a lockdep that happened while executing an `rm -r linux` to
> remove an old kernel git directory. This is for a git 3.10.0+ kernel
> on a non-CRC XFS filesystem that's less than a week old.
>
> I'm not getting lockdep reports like this unless I'm minding my own
> business. xfstests could be running until there's a faint burning
> electrical smell in the room, and this won't show up. But if all I'm
> doing is removing things to prepare for the next xfstests session or
> git activity, then this lockdep will show up. I'm not sure if I get
> the same lockdep every time, but it's related to deletes somehow, and
> it's newer than the production 3.10 kernel, AFAIK.
>
> For the lockdeps, this pattern is prominent...
>
> CPU0
> ----
> lock(&(&ip->i_lock)->mr_lock);
> <Interrupt>
> lock(&(&ip->i_lock)->mr_lock);
>
> ...and lockdep hasn't suggested the SMP scenario on XFS in some time.
>
> There does seem to be some new lockdep work in the kernel, so maybe
> it's not a regression but something else.
.....
> [<c10a3d44>] __get_free_pages+0x1c/0x37
> [<c1025dc4>] pte_alloc_one_kernel+0x14/0x16
> [<c10b7716>] __pte_alloc_kernel+0x16/0x71
> [<c10c0f27>] vmap_page_range_noflush+0x12c/0x13a
> [<c10c1fdb>] vm_map_ram+0x32c/0x3d7
> [<c10c1d21>] ? vm_map_ram+0x72/0x3d7
> [<c1171d3b>] _xfs_buf_map_pages+0x5b/0xe1
It's vmap related. Again. Ignore it.
On the bright side, I think I've found precedence in the kernel for
getting this fixed, so stay tuned....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-07-15 1:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-14 0:33 Lockdep for 3.10.0+ for rm of kernel git Michael L. Semon
2013-07-15 1:24 ` 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=20130715012441.GG5228@dastard \
--to=david@fromorbit.com \
--cc=mlsemon35@gmail.com \
--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