From: Matthew Wilcox <willy@infradead.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-nvdimm <linux-nvdimm@lists.01.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Balcer, Piotr" <piotr.balcer@intel.com>
Subject: Re: find_get_entries_tag regression bisected
Date: Sat, 16 Feb 2019 13:11:05 -0800 [thread overview]
Message-ID: <20190216211105.GO12668@bombadil.infradead.org> (raw)
In-Reply-To: <20190216172948.GN12668@bombadil.infradead.org>
On Sat, Feb 16, 2019 at 09:29:48AM -0800, Matthew Wilcox wrote:
> On Sat, Feb 16, 2019 at 07:35:11AM -0800, Matthew Wilcox wrote:
> > Another way to fix this would be to mask the address in dax_entry_mkclean(),
> > but I think this is cleaner.
>
> That's clearly rubbish, dax_entry_mkclean() can't possibly mask the
> address. It might be mis-aligned in another process. But ... if it's
> misaligned in another process, dax_entry_mkclean() will only clean the first
> PTE associated with the PMD; it won't clean the whole thing. I think we need
> something like this:
Nope, this isn't enough. It's _necessary_ to find the processes that
have part of this PMD page mapped, but not the start of it. But it's
not _sufficient_ because it'll still only mkclean the first PTE. So we
need a loop. I'm feeling a bit over my head here. I may have a go at
a fuller fix, but if someone else wants to have a go at it, be my guest!
(feeling massively unqualified for the task at hand ;-)
next prev parent reply other threads:[~2019-02-16 21:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-16 2:08 find_get_entries_tag regression bisected Dan Williams
2019-02-16 15:35 ` Matthew Wilcox
2019-02-16 17:29 ` Matthew Wilcox
2019-02-16 21:11 ` Matthew Wilcox [this message]
2019-02-26 5:03 ` Dan Williams
2019-02-26 12:08 ` Matthew Wilcox
2019-02-26 13:16 ` Matthew Wilcox
2019-02-27 18:16 ` Dan Williams
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=20190216211105.GO12668@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=dan.j.williams@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=piotr.balcer@intel.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).