[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <159803590250.29194.13619627284206815276@build.alporthouse.com>
Date: Fri, 21 Aug 2020 19:51:42 +0100
From: Chris Wilson <chris@...is-wilson.co.uk>
To: Andrew Morton <akpm@...ux-foundation.org>,
Joerg Roedel <joro@...tes.org>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
intel-gfx@...ts.freedesktop.org, Pavel Machek <pavel@....cz>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Dave Airlie <airlied@...hat.com>,
Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@...el.com>,
David Vrabel <david.vrabel@...rix.com>,
Joerg Roedel <jroedel@...e.de>, stable@...r.kernel.org
Subject: Re: [PATCH v2] mm: Track page table modifications in __apply_to_page_range()
Quoting Joerg Roedel (2020-08-21 13:37:46)
> From: Joerg Roedel <jroedel@...e.de>
>
> The __apply_to_page_range() function is also used to change and/or
> allocate page-table pages in the vmalloc area of the address space.
> Make sure these changes get synchronized to other page-tables in the
> system by calling arch_sync_kernel_mappings() when necessary.
>
> Tested-by: Chris Wilson <chris@...is-wilson.co.uk> #x86-32
> Cc: <stable@...r.kernel.org> # v5.8+
> Signed-off-by: Joerg Roedel <jroedel@...e.de>
I've doubled check that this patch by itself fixes our x86-32 vmapping
issue. Thanks,
-Chris
Powered by blists - more mailing lists