From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Ralph Campbell <rcampbell@nvidia.com>
To: <linux-mm@kvack.org>
Cc: <linux-kernel@vger.kernel.org>, Ralph Campbell <rcampbell@nvidia.com>,
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Mike Kravetz <mike.kravetz@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Jason Gunthorpe <jgg@mellanox.com>
Cc: John Hubbard <jhubbard@nvidia.com>
Cc: <stable@vger.kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH v3 3/3] mm/hmm: Fix bad subpage pointer in try_to_unmap_one
Date: Thu, 25 Jul 2019 02:03:39 +0000 [thread overview]
Message-ID: <20190725020340.D2EA021951@mail.kernel.org> (raw)
In-Reply-To: <20190724232700.23327-4-rcampbell@nvidia.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: a5430dda8a3a mm/migrate: support un-addressable ZONE_DEVICE page in migration.
The bot has tested the following trees: v5.2.2, v5.1.19, v4.19.60, v4.14.134.
v5.2.2: Build OK!
v5.1.19: Build OK!
v4.19.60: Build OK!
v4.14.134: Failed to apply! Possible dependencies:
0f10851ea475 ("mm/mmu_notifier: avoid double notification when it is useless")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks,
Sasha
prev parent reply other threads:[~2019-07-25 2:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 23:26 [PATCH v3 0/3] mm/hmm: fixes for device private page migration Ralph Campbell
2019-07-24 23:26 ` [PATCH v3 1/3] mm: document zone device struct page field usage Ralph Campbell
2019-07-25 1:22 ` Jason Gunthorpe
2019-07-25 17:49 ` Ralph Campbell
2019-07-25 5:38 ` Christoph Hellwig
2019-07-25 18:19 ` Ralph Campbell
2019-07-24 23:26 ` [PATCH v3 2/3] mm/hmm: fix ZONE_DEVICE anon page mapping reuse Ralph Campbell
2019-08-02 8:31 ` Christoph Hellwig
2019-08-02 19:11 ` Andrew Morton
2019-07-24 23:27 ` [PATCH v3 3/3] mm/hmm: Fix bad subpage pointer in try_to_unmap_one Ralph Campbell
2019-07-25 2:03 ` Sasha Levin [this message]
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=20190725020340.D2EA021951@mail.kernel.org \
--to=sashal@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rcampbell@nvidia.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).