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, vbabka@suse.cz,
Will Deacon <will.deacon@arm.com>
Subject: [PATCH v2 0/3] mm: huge pages: Misc fixes for issues found during fuzzing
Date: Tue, 13 Jun 2017 11:28:39 +0100 [thread overview]
Message-ID: <1497349722-6731-1-git-send-email-will.deacon@arm.com> (raw)
Hi all,
This is v2 of the patches previously posted here:
http://www.spinics.net/lists/linux-mm/msg128577.html
Changes since v1 include:
* Use smp_mb() instead of smp_mb__before_atomic() before atomic_set()
* Added acks and fixes tag
Feedback welcome,
Will
--->8
Mark Rutland (1):
mm: numa: avoid waiting on freed migrated pages
Will Deacon (2):
mm/page_ref: Ensure page_ref_unfreeze is ordered against prior
accesses
mm: migrate: Stabilise page count when migrating transparent hugepages
include/linux/page_ref.h | 1 +
mm/huge_memory.c | 8 +++++++-
mm/migrate.c | 15 ++-------------
3 files changed, 10 insertions(+), 14 deletions(-)
--
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>
next reply other threads:[~2017-06-13 10:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 10:28 Will Deacon [this message]
2017-06-13 10:28 ` [PATCH v2 1/3] mm: numa: avoid waiting on freed migrated pages Will Deacon
2017-06-13 10:28 ` [PATCH v2 2/3] mm/page_ref: Ensure page_ref_unfreeze is ordered against prior accesses Will Deacon
2017-06-13 14:06 ` Kirill A. Shutemov
2017-06-13 10:28 ` [PATCH v2 3/3] mm: migrate: Stabilise page count when migrating transparent hugepages Will Deacon
2017-06-15 20:32 ` [PATCH v2 0/3] mm: huge pages: Misc fixes for issues found during fuzzing Andrew Morton
2017-06-19 9:35 ` Will Deacon
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=1497349722-6731-1-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 \
--cc=vbabka@suse.cz \
/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).