[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHk-=wi4+sVr6MUsybh8v-fPYoruZK9AmtasqMYi7z09UKHf6Q@mail.gmail.com>
Date: Mon, 28 Oct 2024 08:50:52 -1000
From: Linus Torvalds <torvalds@...uxfoundation.org>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Hugh Dickins <hughd@...gle.com>, Alexander Viro <viro@...iv.linux.org.uk>,
Andrew Morton <akpm@...ux-foundation.org>, Christian Brauner <brauner@...nel.org>,
Matthew Wilcox <willy@...radead.org>, Christoph Hellwig <hch@....de>,
Kent Overstreet <kent.overstreet@...ux.dev>, "Darrick J. Wong" <djwong@...nel.org>,
Peter Zijlstra <peterz@...radead.org>, linux-fsdevel@...r.kernel.org,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH] iov_iter: fix copy_page_from_iter_atomic() if KMAP_LOCAL_FORCE_MAP
On Sun, 27 Oct 2024 at 22:41, Thomas Gleixner <tglx@...utronix.de> wrote:
>
> It has caught real problems and as long as we have highmem support, it
> should stay IMO to provide test coverage.
Yeah. I'd love to get rid of highmem support entirely, and that day
*will* come. Old 32-bit architectures that do stupid things can just
deal with old kernels, we need to leave that braindamage behind some
day.
But as long as we support it, we should at least also have the debug
support for it on sane hardware.
Of course, maybe we should just make PageHighMem() always return true
for CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP, but I suspect that would cause
more pain than is worth it.
But yeah, I do think we should seriously start thinking about just
getting rid of HIGHMEM.
Linus
Powered by blists - more mailing lists