From: Chris Murphy <lists@colorremedies.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: 5.2.0 rc5, circular lock warning systemd-journal and btrfs_page_mkwrite
Date: Tue, 18 Jun 2019 12:53:26 -0600 [thread overview]
Message-ID: <CAJCQCtT6NgAmZkiWuTLD1Js-bvDHL-LeVo+wgbhdSNW4cmsD1A@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtQT+PJR14Z6iMmiw63LaPqrn0cWjdU6daNhF=D_67eALg@mail.gmail.com>
On Tue, Jun 18, 2019 at 11:45 AM Chris Murphy <lists@colorremedies.com> wrote:
>
> This still happens on RC5, attaching full dmesg to this email.
>
> [ 8.432777] BTRFS info (device sda6): use zstd compression, level 3
> [ 8.432791] BTRFS info (device sda6): using free space tree
> [ 8.581762] systemd-journald[649]: Received request to flush
> runtime journal from PID 1
>
> [ 8.639535] ======================================================
> [ 8.641452] WARNING: possible circular locking dependency detected
> [ 8.643283] 5.2.0-0.rc5.git0.1.fc31.x86_64+debug #1 Not tainted
> [ 8.645060] ------------------------------------------------------
> [ 8.646765] systemd-journal/649 is trying to acquire lock:
> [ 8.648393] (____ptrval____) (&fs_info->reloc_mutex){+.+.}, at:
> btrfs_record_root_in_trans+0x44/0x70 [btrfs]
> [ 8.650111]
> but task is already holding lock:
> [ 8.653475] (____ptrval____) (sb_pagefaults){.+.+}, at:
> btrfs_page_mkwrite+0x69/0x570 [btrfs]
> [ 8.655238]
> which lock already depends on the new lock.
It would not attach so here it is:
https://drive.google.com/open?id=1KahsVcP88CpJprMe6aCFilpj22uGo0Nn
--
Chris Murphy
prev parent reply other threads:[~2019-06-18 18:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 18:24 5.2rc2, circular lock warning systemd-journal and btrfs_page_mkwrite Chris Murphy
2019-06-17 10:45 ` [systemd-devel] " Lennart Poettering
[not found] ` <CAJCQCtQT+PJR14Z6iMmiw63LaPqrn0cWjdU6daNhF=D_67eALg@mail.gmail.com>
2019-06-18 18:53 ` Chris Murphy [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=CAJCQCtT6NgAmZkiWuTLD1Js-bvDHL-LeVo+wgbhdSNW4cmsD1A@mail.gmail.com \
--to=lists@colorremedies.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 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).