All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <josef@toxicpanda.com>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH 0/2] A couple of lockdep fixes
Date: Tue,  1 Sep 2020 08:09:00 -0400	[thread overview]
Message-ID: <cover.1598961912.git.josef@toxicpanda.com> (raw)

Hello,

These are the last two lockdep splats I'm able to see in my testing.  We have
like 4 variations of the same lockdep splat that's addressed by 

btrfs: do not create raid sysfs entries under chunk_mutex

Basically this particular dependency pulls in the kernfs_mutex under the
chunk_mutex, and so we have like 4 issues in github with slightly different
splats, but are all fixed by that fix.  With these two patches (and the one I
sent the other day for add_missing_dev) I haven't hit any lockdep splats in 6
runs of xfstests on 3 different VMs in the last 12 hours.  That means it should
take Dave at least 2 runs before he hits a new one.  Thanks,

Josef Bacik (2):
  btrfs: init sysfs for devices outside of the chunk_mutex
  btrfs: do not create raid sysfs entries under chunk_mutex

 fs/btrfs/block-group.c | 23 +++++++++++++++++++----
 fs/btrfs/sysfs.c       | 25 +++++++++++++++++++++++--
 fs/btrfs/volumes.c     |  7 ++++---
 3 files changed, 46 insertions(+), 9 deletions(-)

-- 
2.26.2


             reply	other threads:[~2020-09-01 12:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-01 12:09 Josef Bacik [this message]
2020-09-01 12:09 ` [PATCH 1/2] btrfs: init sysfs for devices outside of the chunk_mutex Josef Bacik
2020-09-01 15:28   ` David Sterba
2020-09-01 12:09 ` [PATCH 2/2] btrfs: do not create raid sysfs entries under chunk_mutex Josef Bacik
2020-09-01 15:35   ` David Sterba
2020-09-01 17:31     ` Josef Bacik

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=cover.1598961912.git.josef@toxicpanda.com \
    --to=josef@toxicpanda.com \
    --cc=kernel-team@fb.com \
    --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 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.