From: Greg KH <gregkh@linuxfoundation.org>
To: Yang Shi <yang@os.amperecomputing.com>
Cc: sashal@kernel.org, yangge1116@126.com, hch@infradead.org,
david@redhat.com, peterx@redhat.com, akpm@linux-foundation.org,
linux-mm@kvack.org, stable@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [v2 v6.6-stable PATCH] mm: gup: stop abusing try_grab_folio
Date: Thu, 15 Aug 2024 10:29:44 +0200 [thread overview]
Message-ID: <2024081538-buckshot-captivity-f0f8@gregkh> (raw)
In-Reply-To: <20240812181238.1882310-1-yang@os.amperecomputing.com>
On Mon, Aug 12, 2024 at 11:12:37AM -0700, Yang Shi wrote:
> commit f442fa6141379a20b48ae3efabee827a3d260787 upstream
>
> A kernel warning was reported when pinning folio in CMA memory when
> launching SEV virtual machine. The splat looks like:
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2024-08-15 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 18:12 Yang Shi
2024-08-12 18:12 ` [v2 v6.9-stable " Yang Shi
2024-08-15 8:28 ` Greg KH
2024-08-15 8:29 ` Greg KH [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=2024081538-buckshot-captivity-f0f8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=yang@os.amperecomputing.com \
--cc=yangge1116@126.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