From: Mikulas Patocka <mpatocka@redhat.com>
To: Adrian Huang12 <ahuang12@lenovo.com>
Cc: Coly Li <colyli@suse.de>, Jan Kara <jack@suse.com>,
Mike Snitzer <snitzer@redhat.com>,
Pankaj Gupta <pankaj.gupta.linux@gmail.com>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: RE: [External] regression caused by patch 6180bb446ab624b9ab8bf201ed251ca87f07b413 ("dax: fix detection of dax support for non-persistent memory block devices")
Date: Tue, 15 Sep 2020 07:09:15 -0400 (EDT) [thread overview]
Message-ID: <alpine.LRH.2.02.2009150708460.29996@file01.intranet.prod.int.rdu2.redhat.com> (raw)
In-Reply-To: <HK2PR0302MB259490E9D3F212396ACD0109B3200@HK2PR0302MB2594.apcprd03.prod.outlook.com>
On Tue, 15 Sep 2020, Adrian Huang12 wrote:
> Hi Mikulas,
>
> > -----Original Message-----
> > From: Mikulas Patocka <mpatocka@redhat.com>
> > Sent: Monday, September 14, 2020 11:49 PM
> > To: Coly Li <colyli@suse.de>; Dan Williams <dan.j.williams@intel.com>; Dave
> > Jiang <dave.jiang@intel.com>
> > Cc: Jan Kara <jack@suse.com>; Vishal Verma <vishal.l.verma@intel.com>;
> > Adrian Huang12 <ahuang12@lenovo.com>; Ira Weiny <ira.weiny@intel.com>;
> > Mike Snitzer <snitzer@redhat.com>; Pankaj Gupta
> > <pankaj.gupta.linux@gmail.com>; linux-nvdimm@lists.01.org
> > Subject: [External] regression caused by patch
> > 6180bb446ab624b9ab8bf201ed251ca87f07b413 ("dax: fix detection of dax
> > support for non-persistent memory block devices")
> >
> > Hi
> >
> > The patch 6180bb446ab624b9ab8bf201ed251ca87f07b413 ("dax: fix
> > detection of dax support for non-persistent memory block devices") causes
> > crash when attempting to mount the ext4 filesystem on /dev/pmem0
> > ("mkfs.ext4 /dev/pmem0; mount -t ext4 /dev/pmem0 /mnt/test"). The device
> > /dev/pmem0 is emulated using the "memmap" kernel parameter.
> >
>
> Could you please test the following patch? Thanks.
> https://lists.01.org/hyperkitty/list/linux-nvdimm@lists.01.org/thread/2JDBSE2WK75LSGCFEOY3RXRN3CNLBPB2/
I tested it and it works.
Mikulas
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
prev parent reply other threads:[~2020-09-15 11:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 15:48 regression caused by patch 6180bb446ab624b9ab8bf201ed251ca87f07b413 ("dax: fix detection of dax support for non-persistent memory block devices") Mikulas Patocka
2020-09-15 3:03 ` 回复：regression " colyli
2020-09-15 8:01 ` 回复：regression caused by patch 6180bb446ab624b9ab8bf201ed251ca87f07b413?? ("dax: fix detection of dax support for non-persistent memory block?? devices") Jan Kara
2020-09-15 15:12 ` Verma, Vishal L
2020-09-16 9:17 ` Jan Kara
2020-09-15 19:49 ` Dan Williams
2020-09-15 19:56 ` Mike Snitzer
2020-09-15 20:11 ` Dan Williams
2020-09-16 11:24 ` Jan Kara
2020-09-15 8:03 ` [External] regression caused by patch 6180bb446ab624b9ab8bf201ed251ca87f07b413 ("dax: fix detection of dax support for non-persistent memory block devices") Adrian Huang12
2020-09-15 8:16 ` Adrian Huang12
2020-09-15 11:09 ` Mikulas Patocka [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=alpine.LRH.2.02.2009150708460.29996@file01.intranet.prod.int.rdu2.redhat.com \
--to=mpatocka@redhat.com \
--cc=ahuang12@lenovo.com \
--cc=colyli@suse.de \
--cc=jack@suse.com \
--cc=linux-nvdimm@lists.01.org \
--cc=pankaj.gupta.linux@gmail.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).