linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
To: linux-btrfs@vger.kernel.org
Subject: repeatable btrfs deadlock in unlink, kernel versions v3.15..v3.18.3
Date: Sat, 17 Jan 2015 22:14:23 -0500	[thread overview]
Message-ID: <20150118031423.GA12780@hungrycats.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 783 bytes --]

Processes keep getting stuck in btrfs_evict_inode during unlink.

I've seen this dozens of times, usually when two subvols on a btrfs
filesystem are active at the same time (i.e. it never happens on
single-subvol filesystems).  It happens on kernel versions v3.15..v3.18.3.

This used to happen with SyS_renameat2 on the stack, but I haven't seen
a stack trace including that function since late November (v3.18-rc6).

	[<ffffffff81387dc0>] lock_extent_bits+0x1b0/0x200
	[<ffffffff81375e99>] btrfs_evict_inode+0x139/0x550
	[<ffffffff8120d708>] evict+0xb8/0x190
	[<ffffffff8120dec5>] iput+0x105/0x1a0
	[<ffffffff812001d9>] do_unlinkat+0x189/0x2d0
	[<ffffffff81202e26>] SyS_unlink+0x16/0x20
	[<ffffffff8185e96d>] system_call_fastpath+0x1a/0x1f
	[<ffffffffffffffff>] 0xffffffffffffffff

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

                 reply	other threads:[~2015-01-18  3:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20150118031423.GA12780@hungrycats.org \
    --to=ce3g8jdj@umail.furryterror.org \
    --cc=linux-btrfs@vger.kernel.org \
    /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).