linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Zdenek Sojka" <zsojka@seznam.cz>
To: "Nikolay Borisov" <nborisov@suse.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: possible circular locking dependency detected (sb_internal/fs_reclaim)
Date: Wed, 11 Sep 2019 10:35:38 +0200 (CEST)	[thread overview]
Message-ID: <Hue.2yoN.5452lXisyg7.1TUB7Q@seznam.cz> (raw)
In-Reply-To: ec419309-2903-aeed-8776-065920e65e7b@suse.com

Hello,

---------- Původní e-mail ----------

Od: Nikolay Borisov <nborisov@suse.com>

Komu: Zdenek Sojka <zsojka@seznam.cz>, linux-btrfs@vger.kernel.org

Datum: 11. 9. 2019 10:16:49

Předmět: Re: possible circular locking dependency detected
 (sb_internal/fs_reclaim)





On 11.09.19 г. 10:54 ч.,  Zdenek Sojka  wrote:

> Hello,

>

> this is my fourth attempt to post this message to the mailing list; this time, without any attached kernel config (because it has over 100KiB). I also tried contacting the kernel btrfs maintainers directly by email, but they probably also didn't receive the message...

>

> I am running kernel with lock debugging enabled since I am quite often encountering various lockups and hung tasks. Several of the problems have been fixed recently, but not all; I don't know if the following backtrace is related to the hangups, or if it is just a false positive.

>

> $ uname -a

> Linux zso 5.2.11-gentoo #2 SMP Fri Aug 30 07:18:03 CEST 2019 x86_64 Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz GenuineIntel GNU/Linux

>

> The kernel has a distro patchset applied (which should not affect this, but you can never say that for sure) and I am compiling at -O3 -fipa-pta -march=native instead of default -O2 (gcc-8.3.0).

>

> Please let me know if I can provide any more information.

>

> Best regards,

> Zdenek Sojka

>

> The dmesg warning I recently triggered:



> This already received a patch in [PATCH] btrfs: nofs inode allocations

> It's just not reviewed/merged yet. Care to test that patch if you can

> reliably reproduce this?


Thank you for the reply, I missed that thread.
Applied, and I will start testing.

Best regards,
Zdenek Sojka

      reply	other threads:[~2019-09-11  8:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-11  7:54 possible circular locking dependency detected (sb_internal/fs_reclaim) Zdenek Sojka
2019-09-11  8:16 ` Nikolay Borisov
2019-09-11  8:35   ` Zdenek Sojka [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=Hue.2yoN.5452lXisyg7.1TUB7Q@seznam.cz \
    --to=zsojka@seznam.cz \
    --cc=linux-btrfs@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).