From: Juergen Gross <jgross@suse.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
xen-devel@lists.xenproject.org, akpm@linux-foundation.org,
stable@vger.kernel.org,
Pavel Tatashin <pasha.tatashin@oracle.com>
Subject: Re: [PATCH] mm: don't defer struct page initialization for Xen pv guests
Date: Fri, 16 Feb 2018 15:02:17 +0100 [thread overview]
Message-ID: <1424bb25-7d6a-ee21-83b4-0e90369d6132@suse.com> (raw)
In-Reply-To: <20180216135940.GQ7275@dhcp22.suse.cz>
On 16/02/18 14:59, Michal Hocko wrote:
> [CC Pavel]
>
> On Fri 16-02-18 14:37:26, Juergen Gross wrote:
>> Commit f7f99100d8d95dbcf09e0216a143211e79418b9f ("mm: stop zeroing
>> memory during allocation in vmemmap") broke Xen pv domains in some
>> configurations, as the "Pinned" information in struct page of early
>> page tables could get lost.
>
> Could you be more specific please?
In which way? Do you want to see the resulting crash in the commit
message or some more background information?
>
>> Avoid this problem by not deferring struct page initialization when
>> running as Xen pv guest.
>>
>> Cc: <stable@vger.kernel.org> #4.15
> Fixes: f7f99100d8d9 ("mm: stop zeroing memory during allocation in vmemmap")
>
> please
Okay.
Juergen
--
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 prev parent reply other threads:[~2018-02-16 14:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 13:37 Juergen Gross
2018-02-16 13:59 ` Michal Hocko
2018-02-16 14:02 ` Juergen Gross [this message]
2018-02-16 14:21 ` Pavel Tatashin
2018-02-16 14:28 ` Michal Hocko
2018-02-18 16:25 ` kbuild test robot
2018-02-18 18:45 ` kbuild test robot
2018-02-20 23:21 ` 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=1424bb25-7d6a-ee21-83b4-0e90369d6132@suse.com \
--to=jgross@suse.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=pasha.tatashin@oracle.com \
--cc=stable@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox