From: Jerome Glisse <jglisse@redhat.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: Jan Kara <jack@suse.cz>,
linux-nvdimm@lists.01.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, hch@lst.de, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v6 06/13] mm, dev_pagemap: Do not clear ->mapping on final put
Date: Mon, 23 Jul 2018 12:23:08 -0400 [thread overview]
Message-ID: <20180723162308.GA4704@redhat.com> (raw)
In-Reply-To: <3fcb3c8a-2a41-7c78-edde-066c10110d34@intel.com>
On Mon, Jul 23, 2018 at 09:12:06AM -0700, Dave Jiang wrote:
> Jerome,
> Is it possible to get an ack for this? Thanks!
>
> On 07/13/2018 09:50 PM, Dan Williams wrote:
> > MEMORY_DEVICE_FS_DAX relies on typical page semantics whereby ->mapping
> > is only ever cleared by truncation, not final put.
> >
> > Without this fix dax pages may forget their mapping association at the
> > end of every page pin event.
> >
> > Move this atypical behavior that HMM wants into the HMM ->page_free()
> > callback.
> >
> > Cc: <stable@vger.kernel.org>
> > Cc: Jan Kara <jack@suse.cz>
> > Cc: Andrew Morton <akpm@linux-foundation.org>
> > Cc: Ross Zwisler <ross.zwisler@linux.intel.com>
> > Fixes: d2c997c0f145 ("fs, dax: use page->mapping...")
> > Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Acked-by: Jérôme Glisse <jglisse@redhat.com>
> > ---
> > kernel/memremap.c | 1 -
> > mm/hmm.c | 2 ++
> > 2 files changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/kernel/memremap.c b/kernel/memremap.c
> > index 5857267a4af5..62603634a1d2 100644
> > --- a/kernel/memremap.c
> > +++ b/kernel/memremap.c
> > @@ -339,7 +339,6 @@ void __put_devmap_managed_page(struct page *page)
> > __ClearPageActive(page);
> > __ClearPageWaiters(page);
> >
> > - page->mapping = NULL;
> > mem_cgroup_uncharge(page);
> >
> > page->pgmap->page_free(page, page->pgmap->data);
> > diff --git a/mm/hmm.c b/mm/hmm.c
> > index de7b6bf77201..f9d1d89dec4d 100644
> > --- a/mm/hmm.c
> > +++ b/mm/hmm.c
> > @@ -963,6 +963,8 @@ static void hmm_devmem_free(struct page *page, void *data)
> > {
> > struct hmm_devmem *devmem = data;
> >
> > + page->mapping = NULL;
> > +
> > devmem->ops->free(devmem, page);
> > }
> >
> >
> > _______________________________________________
> > Linux-nvdimm mailing list
> > Linux-nvdimm@lists.01.org
> > https://lists.01.org/mailman/listinfo/linux-nvdimm
> >
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: Jerome Glisse <jglisse@redhat.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
linux-nvdimm@lists.01.org, Jan Kara <jack@suse.cz>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
hch@lst.de
Subject: Re: [PATCH v6 06/13] mm, dev_pagemap: Do not clear ->mapping on final put
Date: Mon, 23 Jul 2018 12:23:08 -0400 [thread overview]
Message-ID: <20180723162308.GA4704@redhat.com> (raw)
In-Reply-To: <3fcb3c8a-2a41-7c78-edde-066c10110d34@intel.com>
On Mon, Jul 23, 2018 at 09:12:06AM -0700, Dave Jiang wrote:
> Jerome,
> Is it possible to get an ack for this? Thanks!
>
> On 07/13/2018 09:50 PM, Dan Williams wrote:
> > MEMORY_DEVICE_FS_DAX relies on typical page semantics whereby ->mapping
> > is only ever cleared by truncation, not final put.
> >
> > Without this fix dax pages may forget their mapping association at the
> > end of every page pin event.
> >
> > Move this atypical behavior that HMM wants into the HMM ->page_free()
> > callback.
> >
> > Cc: <stable@vger.kernel.org>
> > Cc: Jan Kara <jack@suse.cz>
> > Cc: Andrew Morton <akpm@linux-foundation.org>
> > Cc: Ross Zwisler <ross.zwisler@linux.intel.com>
> > Fixes: d2c997c0f145 ("fs, dax: use page->mapping...")
> > Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Acked-by: J�r�me Glisse <jglisse@redhat.com>
> > ---
> > kernel/memremap.c | 1 -
> > mm/hmm.c | 2 ++
> > 2 files changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/kernel/memremap.c b/kernel/memremap.c
> > index 5857267a4af5..62603634a1d2 100644
> > --- a/kernel/memremap.c
> > +++ b/kernel/memremap.c
> > @@ -339,7 +339,6 @@ void __put_devmap_managed_page(struct page *page)
> > __ClearPageActive(page);
> > __ClearPageWaiters(page);
> >
> > - page->mapping = NULL;
> > mem_cgroup_uncharge(page);
> >
> > page->pgmap->page_free(page, page->pgmap->data);
> > diff --git a/mm/hmm.c b/mm/hmm.c
> > index de7b6bf77201..f9d1d89dec4d 100644
> > --- a/mm/hmm.c
> > +++ b/mm/hmm.c
> > @@ -963,6 +963,8 @@ static void hmm_devmem_free(struct page *page, void *data)
> > {
> > struct hmm_devmem *devmem = data;
> >
> > + page->mapping = NULL;
> > +
> > devmem->ops->free(devmem, page);
> > }
> >
> >
> > _______________________________________________
> > Linux-nvdimm mailing list
> > Linux-nvdimm@lists.01.org
> > https://lists.01.org/mailman/listinfo/linux-nvdimm
> >
WARNING: multiple messages have this Message-ID (diff)
From: Jerome Glisse <jglisse@redhat.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
linux-nvdimm@lists.01.org, Jan Kara <jack@suse.cz>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
hch@lst.de
Subject: Re: [PATCH v6 06/13] mm, dev_pagemap: Do not clear ->mapping on final put
Date: Mon, 23 Jul 2018 12:23:08 -0400 [thread overview]
Message-ID: <20180723162308.GA4704@redhat.com> (raw)
In-Reply-To: <3fcb3c8a-2a41-7c78-edde-066c10110d34@intel.com>
On Mon, Jul 23, 2018 at 09:12:06AM -0700, Dave Jiang wrote:
> Jerome,
> Is it possible to get an ack for this? Thanks!
>
> On 07/13/2018 09:50 PM, Dan Williams wrote:
> > MEMORY_DEVICE_FS_DAX relies on typical page semantics whereby ->mapping
> > is only ever cleared by truncation, not final put.
> >
> > Without this fix dax pages may forget their mapping association at the
> > end of every page pin event.
> >
> > Move this atypical behavior that HMM wants into the HMM ->page_free()
> > callback.
> >
> > Cc: <stable@vger.kernel.org>
> > Cc: Jan Kara <jack@suse.cz>
> > Cc: Andrew Morton <akpm@linux-foundation.org>
> > Cc: Ross Zwisler <ross.zwisler@linux.intel.com>
> > Fixes: d2c997c0f145 ("fs, dax: use page->mapping...")
> > Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Acked-by: Jerome Glisse <jglisse@redhat.com>
> > ---
> > kernel/memremap.c | 1 -
> > mm/hmm.c | 2 ++
> > 2 files changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/kernel/memremap.c b/kernel/memremap.c
> > index 5857267a4af5..62603634a1d2 100644
> > --- a/kernel/memremap.c
> > +++ b/kernel/memremap.c
> > @@ -339,7 +339,6 @@ void __put_devmap_managed_page(struct page *page)
> > __ClearPageActive(page);
> > __ClearPageWaiters(page);
> >
> > - page->mapping = NULL;
> > mem_cgroup_uncharge(page);
> >
> > page->pgmap->page_free(page, page->pgmap->data);
> > diff --git a/mm/hmm.c b/mm/hmm.c
> > index de7b6bf77201..f9d1d89dec4d 100644
> > --- a/mm/hmm.c
> > +++ b/mm/hmm.c
> > @@ -963,6 +963,8 @@ static void hmm_devmem_free(struct page *page, void *data)
> > {
> > struct hmm_devmem *devmem = data;
> >
> > + page->mapping = NULL;
> > +
> > devmem->ops->free(devmem, page);
> > }
> >
> >
> > _______________________________________________
> > Linux-nvdimm mailing list
> > Linux-nvdimm@lists.01.org
> > https://lists.01.org/mailman/listinfo/linux-nvdimm
> >
WARNING: multiple messages have this Message-ID (diff)
From: Jerome Glisse <jglisse@redhat.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
linux-nvdimm@lists.01.org, Jan Kara <jack@suse.cz>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
hch@lst.de
Subject: Re: [PATCH v6 06/13] mm, dev_pagemap: Do not clear ->mapping on final put
Date: Mon, 23 Jul 2018 12:23:08 -0400 [thread overview]
Message-ID: <20180723162308.GA4704@redhat.com> (raw)
In-Reply-To: <3fcb3c8a-2a41-7c78-edde-066c10110d34@intel.com>
On Mon, Jul 23, 2018 at 09:12:06AM -0700, Dave Jiang wrote:
> Jerome,
> Is it possible to get an ack for this? Thanks!
>
> On 07/13/2018 09:50 PM, Dan Williams wrote:
> > MEMORY_DEVICE_FS_DAX relies on typical page semantics whereby ->mapping
> > is only ever cleared by truncation, not final put.
> >
> > Without this fix dax pages may forget their mapping association at the
> > end of every page pin event.
> >
> > Move this atypical behavior that HMM wants into the HMM ->page_free()
> > callback.
> >
> > Cc: <stable@vger.kernel.org>
> > Cc: Jan Kara <jack@suse.cz>
> > Cc: Andrew Morton <akpm@linux-foundation.org>
> > Cc: Ross Zwisler <ross.zwisler@linux.intel.com>
> > Fixes: d2c997c0f145 ("fs, dax: use page->mapping...")
> > Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Acked-by: Jérôme Glisse <jglisse@redhat.com>
> > ---
> > kernel/memremap.c | 1 -
> > mm/hmm.c | 2 ++
> > 2 files changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/kernel/memremap.c b/kernel/memremap.c
> > index 5857267a4af5..62603634a1d2 100644
> > --- a/kernel/memremap.c
> > +++ b/kernel/memremap.c
> > @@ -339,7 +339,6 @@ void __put_devmap_managed_page(struct page *page)
> > __ClearPageActive(page);
> > __ClearPageWaiters(page);
> >
> > - page->mapping = NULL;
> > mem_cgroup_uncharge(page);
> >
> > page->pgmap->page_free(page, page->pgmap->data);
> > diff --git a/mm/hmm.c b/mm/hmm.c
> > index de7b6bf77201..f9d1d89dec4d 100644
> > --- a/mm/hmm.c
> > +++ b/mm/hmm.c
> > @@ -963,6 +963,8 @@ static void hmm_devmem_free(struct page *page, void *data)
> > {
> > struct hmm_devmem *devmem = data;
> >
> > + page->mapping = NULL;
> > +
> > devmem->ops->free(devmem, page);
> > }
> >
> >
> > _______________________________________________
> > Linux-nvdimm mailing list
> > Linux-nvdimm@lists.01.org
> > https://lists.01.org/mailman/listinfo/linux-nvdimm
> >
next prev parent reply other threads:[~2018-07-23 16:23 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-14 4:49 [PATCH v6 00/13] mm: Teach memory_failure() about ZONE_DEVICE pages Dan Williams
2018-07-14 4:49 ` Dan Williams
2018-07-14 4:49 ` [PATCH v6 01/13] device-dax: Convert to vmf_insert_mixed and vm_fault_t Dan Williams
2018-07-14 4:49 ` Dan Williams
2018-07-14 4:49 ` [PATCH v6 02/13] device-dax: Enable page_mapping() Dan Williams
2018-07-14 4:49 ` Dan Williams
2018-07-14 4:49 ` [PATCH v6 03/13] device-dax: Set page->index Dan Williams
2018-07-14 4:49 ` Dan Williams
2018-07-14 4:49 ` [PATCH v6 04/13] filesystem-dax: " Dan Williams
2018-07-14 4:49 ` Dan Williams
2018-07-14 4:49 ` [PATCH v6 05/13] mm, madvise_inject_error: Disable MADV_SOFT_OFFLINE for ZONE_DEVICE pages Dan Williams
2018-07-14 4:49 ` Dan Williams
2018-07-17 6:47 ` Naoya Horiguchi
2018-07-17 6:47 ` Naoya Horiguchi
2018-07-14 4:50 ` [PATCH v6 06/13] mm, dev_pagemap: Do not clear ->mapping on final put Dan Williams
2018-07-14 4:50 ` Dan Williams
2018-07-14 4:50 ` Dan Williams
2018-07-23 16:12 ` Dave Jiang
2018-07-23 16:12 ` Dave Jiang
2018-07-23 16:12 ` Dave Jiang
2018-07-23 16:23 ` Jerome Glisse [this message]
2018-07-23 16:23 ` Jerome Glisse
2018-07-23 16:23 ` Jerome Glisse
2018-07-23 16:23 ` Jerome Glisse
2018-07-14 4:50 ` [PATCH v6 07/13] mm, madvise_inject_error: Let memory_failure() optionally take a page reference Dan Williams
2018-07-14 4:50 ` Dan Williams
2018-07-17 6:52 ` Naoya Horiguchi
2018-07-14 4:50 ` [PATCH v6 08/13] mm, memory_failure: Collect mapping size in collect_procs() Dan Williams
2018-07-14 4:50 ` Dan Williams
2018-07-14 4:50 ` [PATCH v6 09/13] filesystem-dax: Introduce dax_lock_mapping_entry() Dan Williams
2018-07-14 4:50 ` Dan Williams
2018-08-06 9:21 ` Jan Kara
2018-08-06 9:21 ` Jan Kara
2018-07-14 4:50 ` [PATCH v6 10/13] mm, memory_failure: Teach memory_failure() about dev_pagemap pages Dan Williams
2018-07-14 4:50 ` Dan Williams
2018-07-14 4:50 ` Dan Williams
2018-08-06 9:27 ` Jan Kara
2018-08-06 9:27 ` Jan Kara
2018-08-06 9:27 ` Jan Kara
2018-08-06 9:27 ` Jan Kara
2018-07-14 4:50 ` [PATCH v6 13/13] libnvdimm, pmem: Restore page attributes when clearing errors Dan Williams
2018-07-14 4:50 ` Dan Williams
2018-07-19 17:57 ` [PATCH v6 00/13] mm: Teach memory_failure() about ZONE_DEVICE pages Dave Jiang
2018-07-19 17:57 ` Dave Jiang
2018-07-24 7:39 ` Ingo Molnar
2018-07-24 7:39 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2018-07-14 4:50 [v6,11/13] x86/mm/pat: Prepare {reserve, free}_memtype() for "decoy" addresses Dan Williams
2018-07-14 4:50 ` [PATCH v6 11/13] " Dan Williams
2018-07-14 4:50 ` Dan Williams
2018-07-14 4:50 [v6,12/13] x86/memory_failure: Introduce {set, clear}_mce_nospec() Dan Williams
2018-07-14 4:50 ` [PATCH v6 12/13] " Dan Williams
2018-07-14 4:50 ` Dan Williams
2018-07-24 7:36 [v6,11/13] x86/mm/pat: Prepare {reserve, free}_memtype() for "decoy" addresses Ingo Molnar
2018-07-24 7:36 ` [PATCH v6 11/13] " Ingo Molnar
2018-07-24 7:36 ` Ingo Molnar
2018-07-24 15:46 [v6,11/13] " Dave Jiang
2018-07-24 15:46 ` [PATCH v6 11/13] " Dave Jiang
2018-07-24 15:46 ` Dave Jiang
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=20180723162308.GA4704@redhat.com \
--to=jglisse@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dave.jiang@intel.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=stable@vger.kernel.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.