| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 15 Dec 2009 20:10:48 +0900 From: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp> To: mingo@...e.hu Cc: fujita.tomonori@....ntt.co.jp, yinghai@...nel.org, rdreier@...co.com, linux-kernel@...r.kernel.org Subject: Re: bisected crash due to "x86: Move swiotlb initialization before dma32_free_bootmem" On Tue, 15 Dec 2009 11:56:50 +0100 Ingo Molnar <mingo@...e.hu> wrote: > > * FUJITA Tomonori <fujita.tomonori@....ntt.co.jp> wrote: > > > There are a few people who hit this. How many people use a box with over > > 256GB memory? > > > > And you can work around this with "dma32_size" kernel boot option. > > Well, since the kernel has not crashed before this change there's really just > two options as per upstream kernel regression policy: either we fix it or we > revert it. As I wrote, here is a patch that can be applied to cleanly to the git head: http://www.kernel.org/pub/linux/kernel/people/tomo/misc/0001-x86-two-stage-swiotlb-initialization.patch It fixes the problem. Yinghai, can you test it? It should work but it's good to confirm it. I simply wanted to say that it's not a bug that breaks lots of boxes or leads to something serious like data corruption (no need to say something like "revert it now!"). It's also worth investigating why it breaks, I think. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists