Hi Christoph, > On Mar 30, 2022, at 10:37 PM, Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote: > > On Wed, Mar 30, 2022 at 03:56:38PM -0700, Song Liu wrote: >> We prematurely enabled HAVE_ARCH_HUGE_VMALLOC for x86_64, which could cause >> issues [1], [2]. >> > > Please fix the underlying issues instead of papering over them and > creating a huge maintainance burden for others. I agree that this set is papering over the issue. And I would like your recommendations here. The biggest problem to me is that we (or at least myself) don't know all the issues HAVE_ARCH_HUGE_VMALLOC will trigger on x86_64. Right now we have a bug report from Paul, and the warning from Rick, but I am afraid there might be some other issues. How about we approach it like this: Since it is still early in the release cycle (pre rc1), we can keep HAVE_ARCH_HUGE_VMALLOC on for x86_64 for now and try to fix all the reported issues and warnings. If things don't go very well, we can turn HAVE_ARCH_HUGE_VMALLOC off after rc4 or rc5. Does this make sense? Thanks, Song
