[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200821133548.be58a3b0881b41a32759fa04@linux-foundation.org>
Date: Fri, 21 Aug 2020 13:35:48 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Joerg Roedel <joro@...tes.org>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
Chris Wilson <chris@...is-wilson.co.uk>,
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()
On Fri, 21 Aug 2020 14:37:46 +0200 Joerg Roedel <joro@...tes.org> wrote:
> 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.
There's no description here of the user-visible effects of the bug.
Please always provide this, especially when proposing a -stable
backport. Take pity upon all the downstream kernel maintainers who are
staring at this wondering whether they should risk adding it to their
kernels.
Powered by blists - more mailing lists