From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Mike Kravetz <mike.kravetz@oracle.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: Michal Hocko <mhocko@kernel.org>, Hugh Dickins <hughd@google.com>,
Cc: <stable@vger.kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 2/3] hugetlbfs: Use i_mmap_rwsem to fix page fault/truncate race
Date: Fri, 14 Jun 2019 21:56:31 +0000 [thread overview]
Message-ID: <20190614215632.BF5F721473@mail.kernel.org> (raw)
In-Reply-To: <20181203200850.6460-3-mike.kravetz@oracle.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: ebed4bfc8da8 [PATCH] hugetlb: fix absurd HugePages_Rsvd.
The bot has tested the following trees: v5.1.9, v4.19.50, v4.14.125, v4.9.181, v4.4.181.
v4.19.50: Build OK!
v4.14.125: Build OK!
v4.9.181: Build OK!
v4.4.181: Failed to apply! Possible dependencies:
0070e28d97e7 ("radix_tree: loop based on shift count, not height")
00f47b581105 ("radix-tree: rewrite radix_tree_tag_clear")
0e749e54244e ("dax: increase granularity of dax_clear_blocks() operations")
1366c37ed84b ("radix tree test harness")
29f3ad7d8380 ("fs: Provide function to unmap metadata for a range of blocks")
334fd34d76f2 ("vfs: Add page_cache_seek_hole_data helper")
339e6353046d ("radix_tree: tag all internal tree nodes as indirect pointers")
4aae8d1c051e ("mm/hugetlbfs: unmap pages if page fault raced with hole punch")
52db400fcd50 ("pmem, dax: clean up clear_pmem()")
72e2936c04f7 ("mm: remove unnecessary condition in remove_inode_hugepages")
7fc9e4722435 ("fs: Introduce filemap_range_has_page()")
83929372f629 ("filemap: prepare find and delete operations for huge pages")
ac401cc78242 ("dax: New fault locking")
b2e0d1625e19 ("dax: fix lifetime of in-kernel dax mappings with dax_map_atomic()")
d604c324524b ("radix-tree: introduce radix_tree_replace_clear_tags()")
d72dc8a25afc ("mm: make pagevec_lookup() update index")
e4b274915863 ("DAX: move RADIX_DAX_ definitions to dax.c")
e61452365372 ("radix_tree: add support for multi-order entries")
f9fe48bece3a ("dax: support dirty DAX entries in radix tree")
How should we proceed with this patch?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-06-14 21:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 20:08 [PATCH 0/3] hugetlbfs: use i_mmap_rwsem for better synchronization Mike Kravetz
2018-12-03 20:08 ` [PATCH 1/3] hugetlbfs: use i_mmap_rwsem for more pmd sharing synchronization Mike Kravetz
2018-12-04 13:54 ` Sasha Levin
2018-12-03 20:08 ` [PATCH 2/3] hugetlbfs: Use i_mmap_rwsem to fix page fault/truncate race Mike Kravetz
2018-12-04 13:54 ` Sasha Levin
2018-12-17 10:25 ` Aneesh Kumar K.V
2018-12-17 18:42 ` Mike Kravetz
2018-12-18 0:17 ` Mike Kravetz
2018-12-18 22:10 ` Andrew Morton
2018-12-18 22:34 ` Mike Kravetz
2019-06-14 21:56 ` Sasha Levin [this message]
2019-06-14 23:33 ` Mike Kravetz
2019-06-15 22:38 ` Sasha Levin
2018-12-03 20:08 ` [PATCH 3/3] hugetlbfs: remove unnecessary code after i_mmap_rwsem synchronization Mike Kravetz
2018-12-04 13:54 ` Sasha Levin
2018-12-17 10:34 ` Aneesh Kumar K.V
2018-12-14 21:22 ` [PATCH 0/3] hugetlbfs: use i_mmap_rwsem for better synchronization Andrew Morton
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=20190614215632.BF5F721473@mail.kernel.org \
--to=sashal@kernel.org \
--cc=hughd@google.com \
--cc=mhocko@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.