All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: mark.rutland@arm.com, akpm@linux-foundation.org,
	kirill.shutemov@linux.intel.com, Punit.Agrawal@arm.com,
	mgorman@suse.de, steve.capper@arm.com,
	Will Deacon <will.deacon@arm.com>
Subject: [PATCH 2/3] mm/page_ref: Ensure page_ref_unfreeze is ordered against prior accesses
Date: Tue,  6 Jun 2017 18:58:35 +0100	[thread overview]
Message-ID: <1496771916-28203-3-git-send-email-will.deacon@arm.com> (raw)
In-Reply-To: <1496771916-28203-1-git-send-email-will.deacon@arm.com>

page_ref_freeze and page_ref_unfreeze are designed to be used as a pair,
wrapping a critical section where struct pages can be modified without
having to worry about consistency for a concurrent fast-GUP.

Whilst page_ref_freeze has full barrier semantics due to its use of
atomic_cmpxchg, page_ref_unfreeze is implemented using atomic_set, which
doesn't provide any barrier semantics and allows the operation to be
reordered with respect to page modifications in the critical section.

This patch ensures that page_ref_unfreeze is ordered after any critical
section updates, by invoking smp_mb__before_atomic() prior to the
atomic_set.

Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Acked-by: Steve Capper <steve.capper@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
---
 include/linux/page_ref.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/include/linux/page_ref.h b/include/linux/page_ref.h
index 610e13271918..74d32d7905cb 100644
--- a/include/linux/page_ref.h
+++ b/include/linux/page_ref.h
@@ -174,6 +174,7 @@ static inline void page_ref_unfreeze(struct page *page, int count)
 	VM_BUG_ON_PAGE(page_count(page) != 0, page);
 	VM_BUG_ON(count == 0);
 
+	smp_mb__before_atomic();
 	atomic_set(&page->_refcount, count);
 	if (page_ref_tracepoint_active(__tracepoint_page_ref_unfreeze))
 		__page_ref_unfreeze(page, count);
-- 
2.1.4

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: mark.rutland@arm.com, akpm@linux-foundation.org,
	kirill.shutemov@linux.intel.com, Punit.Agrawal@arm.com,
	mgorman@suse.de, steve.capper@arm.com,
	Will Deacon <will.deacon@arm.com>
Subject: [PATCH 2/3] mm/page_ref: Ensure page_ref_unfreeze is ordered against prior accesses
Date: Tue,  6 Jun 2017 18:58:35 +0100	[thread overview]
Message-ID: <1496771916-28203-3-git-send-email-will.deacon@arm.com> (raw)
In-Reply-To: <1496771916-28203-1-git-send-email-will.deacon@arm.com>

page_ref_freeze and page_ref_unfreeze are designed to be used as a pair,
wrapping a critical section where struct pages can be modified without
having to worry about consistency for a concurrent fast-GUP.

Whilst page_ref_freeze has full barrier semantics due to its use of
atomic_cmpxchg, page_ref_unfreeze is implemented using atomic_set, which
doesn't provide any barrier semantics and allows the operation to be
reordered with respect to page modifications in the critical section.

This patch ensures that page_ref_unfreeze is ordered after any critical
section updates, by invoking smp_mb__before_atomic() prior to the
atomic_set.

Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Acked-by: Steve Capper <steve.capper@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
---
 include/linux/page_ref.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/include/linux/page_ref.h b/include/linux/page_ref.h
index 610e13271918..74d32d7905cb 100644
--- a/include/linux/page_ref.h
+++ b/include/linux/page_ref.h
@@ -174,6 +174,7 @@ static inline void page_ref_unfreeze(struct page *page, int count)
 	VM_BUG_ON_PAGE(page_count(page) != 0, page);
 	VM_BUG_ON(count == 0);
 
+	smp_mb__before_atomic();
 	atomic_set(&page->_refcount, count);
 	if (page_ref_tracepoint_active(__tracepoint_page_ref_unfreeze))
 		__page_ref_unfreeze(page, count);
-- 
2.1.4

  parent reply	other threads:[~2017-06-06 17:58 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-06 17:58 [PATCH 0/3] mm: huge pages: Misc fixes for issues found during fuzzing Will Deacon
2017-06-06 17:58 ` Will Deacon
2017-06-06 17:58 ` [PATCH 1/3] mm: numa: avoid waiting on freed migrated pages Will Deacon
2017-06-06 17:58   ` Will Deacon
2017-06-08  9:04   ` Vlastimil Babka
2017-06-08  9:04     ` Vlastimil Babka
2017-06-08 10:31     ` Mark Rutland
2017-06-08 10:31       ` Mark Rutland
2017-06-08 10:27   ` Kirill A. Shutemov
2017-06-08 10:27     ` Kirill A. Shutemov
2017-06-06 17:58 ` Will Deacon [this message]
2017-06-06 17:58   ` [PATCH 2/3] mm/page_ref: Ensure page_ref_unfreeze is ordered against prior accesses Will Deacon
2017-06-08  9:38   ` Vlastimil Babka
2017-06-08  9:38     ` Vlastimil Babka
2017-06-08 10:34     ` Will Deacon
2017-06-08 10:34       ` Will Deacon
2017-06-08 11:02       ` Vlastimil Babka
2017-06-08 11:02         ` Vlastimil Babka
2017-06-08 10:40     ` Kirill A. Shutemov
2017-06-08 10:40       ` Kirill A. Shutemov
2017-06-08 11:07       ` Vlastimil Babka
2017-06-08 11:07         ` Vlastimil Babka
2017-06-08 11:24         ` Will Deacon
2017-06-08 11:24           ` Will Deacon
2017-06-08 12:16           ` Peter Zijlstra
2017-06-08 12:16             ` Peter Zijlstra
2017-06-08 12:19             ` Peter Zijlstra
2017-06-08 12:19               ` Peter Zijlstra
2017-06-08 12:50           ` Peter Zijlstra
2017-06-08 12:50             ` Peter Zijlstra
2017-06-09 10:05             ` Will Deacon
2017-06-09 10:05               ` Will Deacon
2017-06-06 17:58 ` [PATCH 3/3] mm: migrate: Stabilise page count when migrating transparent hugepages Will Deacon
2017-06-06 17:58   ` Will Deacon
2017-06-08 10:47   ` Kirill A. Shutemov
2017-06-08 10:47     ` Kirill A. Shutemov
2017-06-08 10:52   ` Vlastimil Babka
2017-06-08 10:52     ` Vlastimil Babka
2017-06-08 12:07     ` Will Deacon
2017-06-08 12:07       ` Will Deacon
2017-06-09  8:25       ` zhong jiang
2017-06-09  8:25         ` zhong jiang
2017-06-09  9:16       ` zhong jiang
2017-06-09  9:16         ` zhong 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=1496771916-28203-3-git-send-email-will.deacon@arm.com \
    --to=will.deacon@arm.com \
    --cc=Punit.Agrawal@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mark.rutland@arm.com \
    --cc=mgorman@suse.de \
    --cc=steve.capper@arm.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 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.