* Nathan Chancellor <nathan@xxxxxxxxxx> [220225 18:00]: > On Fri, Feb 25, 2022 at 03:46:52PM -0500, Qian Cai wrote: > > On Fri, Feb 25, 2022 at 08:23:41PM +0000, Liam Howlett wrote: > > > I just booted an arm64 VM with my build and kasan enabled with no issue. > > > Could you please send me your config file for the build? > > > > On linux-next, I just do: > > > > $ make arch=arm64 defconfig debug.config [1] > > > > Then, I just generate some memory pressume into swapping/OOM Killer to > > trigger it. > > > > [1] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/kernel/configs/debug.config > > Is the stacktrace [1] related to the conflict that Mark encountered [2] > while merging the maple and folio trees? Booting a next-20220223 kernel > on my Raspberry Pi 3 and 4 shows constant NULL pointer dereferences > (just ARCH=arm and ARCH=arm64 defconfigs) and reverting the folio and > maple tree merges makes everything work properly again. > > [1]: https://lore.kernel.org/r/YhhRrBpXTFolUAKi@qian/ > [2]: https://lore.kernel.org/r/20220224011653.1380557-1-broonie@xxxxxxxxxx/ Maybe? I'm trying to figure out why it's having issues.. I've not been able to reproduce it with just my maple tree branch. Steven Rostedt found a bad commit that has been fixed in either 20220224, I believe [1]. It might be best to try next-20220225 and see if you have better luck if that's an option. [1]: https://lore.kernel.org/linux-fsdevel/f6fb6fd4-dcf2-4326-d25e-9a4a9dad5020@xxxxxx/T/#t Thanks, Liam
