From: Roman Gushchin <guro@fb.com>
To: Murphy Zhou <jencce.kernel@gmail.com>
Cc: Linux-Fsdevel <linux-fsdevel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>
Subject: Re: [fsdax xfs] Regression panic at inode_switch_wbs_work_fn
Date: Thu, 15 Jul 2021 09:06:51 -0700 [thread overview]
Message-ID: <YPBdG2pe94hRdCMC@carbon.dhcp.thefacebook.com> (raw)
In-Reply-To: <CADJHv_uitWbPquubkFJGwiFi8Vx7V0ZxhYUSiEOd1_vMhHOonA@mail.gmail.com>
On Thu, Jul 15, 2021 at 06:10:22PM +0800, Murphy Zhou wrote:
> Hi,
>
> #Looping generic/270 of xfstests[1] on pmem ramdisk with
> mount option: -o dax=always
> mkfs.xfs option: -f -b size=4096 -m reflink=0
> can hit this panic now.
>
> #It's not reproducible on ext4.
> #It's not reproducible without dax=always.
Hi Murphy!
Thank you for the report!
Can you, please, check if the following patch fixes the problem?
Thank you!
--
diff --git a/mm/backing-dev.c b/mm/backing-dev.c
index 271f2ca862c8..f5561ea7d90a 100644
--- a/mm/backing-dev.c
+++ b/mm/backing-dev.c
@@ -398,12 +398,12 @@ static void cgwb_release_workfn(struct work_struct *work)
blkcg_unpin_online(blkcg);
fprop_local_destroy_percpu(&wb->memcg_completions);
- percpu_ref_exit(&wb->refcnt);
spin_lock_irq(&cgwb_lock);
list_del(&wb->offline_node);
spin_unlock_irq(&cgwb_lock);
+ percpu_ref_exit(&wb->refcnt);
wb_exit(wb);
WARN_ON_ONCE(!list_empty(&wb->b_attached));
kfree_rcu(wb, rcu);
next prev parent reply other threads:[~2021-07-15 16:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 10:10 [fsdax xfs] Regression panic at inode_switch_wbs_work_fn Murphy Zhou
2021-07-15 16:06 ` Roman Gushchin [this message]
2021-07-16 5:57 ` Murphy Zhou
2021-07-16 20:13 ` Roman Gushchin
2021-07-17 17:17 ` Darrick J. Wong
2021-07-17 17:40 ` Matthew Wilcox
2021-07-17 22:08 ` Roman Gushchin
2021-07-17 23:26 ` Matthew Wilcox
2021-07-18 16:07 ` Roman Gushchin
2021-07-19 5:56 ` Murphy Zhou
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=YPBdG2pe94hRdCMC@carbon.dhcp.thefacebook.com \
--to=guro@fb.com \
--cc=jencce.kernel@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.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.