linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Elliott, Robert (Persistent Memory)" <elliott@hpe.com>
To: "Kani, Toshi" <toshi.kani@hpe.com>, "jack@suse.cz" <jack@suse.cz>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: RE: open sets ext4_da_aops for DAX existing files
Date: Mon, 10 Sep 2018 17:58:10 +0000	[thread overview]
Message-ID: <AT5PR8401MB1169A490CF0565CAD12ACC3DAB050@AT5PR8401MB1169.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <0768c59f2d5391ff7678370fbc72cb664fca25fd.camel@hpe.com>



> -----Original Message-----
> From: Linux-nvdimm [mailto:linux-nvdimm-bounces@lists.01.org] On Behalf Of Kani, Toshi
> Sent: Monday, September 10, 2018 9:52 AM
> To: jack@suse.cz
> Cc: linux-fsdevel@vger.kernel.org; linux-nvdimm@lists.01.org
> Subject: Re: open sets ext4_da_aops for DAX existing files
...
> > Good catch. Will you send a fix? I.e., call ext4_set_inode_flags() earlier
> > in the ext4_iget()? Did this bug have any user visible manifestations?
> 
> Yes, sync did not flush processor cache.
> 
> > Please also add:
> >
> > Fixes: 5f0663bb4a64f588f0a2dd6d1be68d40f9af0086
> >
> > so that stable automation picks this up. Thanks!
> >
> 
> Will do.
> 

Also check if the same problem exists with ext2.

---
Robert Elliott, HPE Persistent Memory

  reply	other threads:[~2018-09-10 22:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-07 21:23 open sets ext4_da_aops for DAX existing files Kani, Toshi
2018-09-10 12:54 ` Jeff Moyer
2018-09-10 14:21   ` Kani, Toshi
2018-09-10 14:26     ` Dan Williams
2018-09-10 14:29 ` Jan Kara
2018-09-10 14:51   ` Kani, Toshi
2018-09-10 17:58     ` Elliott, Robert (Persistent Memory) [this message]
2018-09-11 15:27       ` Jan Kara
2018-09-11 16:34         ` Kani, Toshi

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=AT5PR8401MB1169A490CF0565CAD12ACC3DAB050@AT5PR8401MB1169.NAMPRD84.PROD.OUTLOOK.COM \
    --to=elliott@hpe.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=toshi.kani@hpe.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).