From: Dan Williams <dan.j.williams@intel.com>
To: Huang Adrian <adrianhuang0701@gmail.com>
Cc: Jan Kara <jack@suse.cz>, linux-nvdimm <linux-nvdimm@lists.01.org>,
Coly Li <colyli@suse.de>, Mikulas Patocka <mpatocka@redhat.com>,
Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@redhat.com>,
Adrian Huang12 <ahuang12@lenovo.com>
Subject: Re: [PATCH] dm: Call proper helper to determine dax support
Date: Fri, 18 Sep 2020 13:12:00 -0700 [thread overview]
Message-ID: <CAPcyv4hMndViSQegczOhCAZ2effuGWF0PDX7XMufspxSawPVUg@mail.gmail.com> (raw)
In-Reply-To: <CAHKZfL2pQ=wqVNPrf2q2GKGWz=S4NSKzPqJMsyd-yHKZu+EDGQ@mail.gmail.com>
On Fri, Sep 18, 2020 at 5:41 AM Huang Adrian <adrianhuang0701@gmail.com> wrote:
[..]
> Interestingly, the command `lvm2-testsuite --only pvmove-abort-all.sh`
> passed on vanilla 5.9-rc5 (on my two boxes).
> Is it the same symptom (call trace) with my reported one?
>
> Could you please run the above-mentioned command on your box (w/wo
> Jan's patch plus my fixup)?
Thanks for the exact reproduction details. I was hitting a different
hang, but I was able to reproduce this regression / latent bug. Fix is
here:
https://lore.kernel.org/linux-nvdimm/160045867590.25663.7548541079217827340.stgit@dwillia2-desk3.amr.corp.intel.com/T/#u
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
next prev parent reply other threads:[~2020-09-18 20:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 15:14 [PATCH] dm: Call proper helper to determine dax support Jan Kara
2020-09-16 15:22 ` Mike Snitzer
2020-09-17 8:08 ` Jan Kara
2020-09-17 9:28 ` [PATCH] " Dan Williams
2020-09-17 10:42 ` Jan Kara
2020-09-17 14:57 ` Huang Adrian
2020-09-17 15:03 ` Huang Adrian
2020-09-17 17:49 ` Dan Williams
2020-09-18 5:41 ` Dan Williams
2020-09-18 12:41 ` Huang Adrian
2020-09-18 12:48 ` Huang Adrian
2020-09-18 20:12 ` Dan Williams [this message]
2020-09-18 12:34 ` Huang Adrian
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=CAPcyv4hMndViSQegczOhCAZ2effuGWF0PDX7XMufspxSawPVUg@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=adrianhuang0701@gmail.com \
--cc=agk@redhat.com \
--cc=ahuang12@lenovo.com \
--cc=colyli@suse.de \
--cc=jack@suse.cz \
--cc=linux-nvdimm@lists.01.org \
--cc=mpatocka@redhat.com \
--cc=snitzer@redhat.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).