linux-kernel - Re: bisected crash due to "x86: Move swiotlb initialization before dma32_free

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 15 Dec 2009 20:50:53 +0900
From:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
To:	yinghai@...nel.org
Cc:	fujita.tomonori@....ntt.co.jp, mingo@...e.hu, rdreier@...co.com,
	linux-kernel@...r.kernel.org, cl@...ux-foundation.org
Subject: Re: bisected crash due to "x86: Move swiotlb initialization before
 dma32_free_bootmem"

On Tue, 15 Dec 2009 03:25:41 -0800
Yinghai Lu <yinghai@...nel.org> wrote:

> FUJITA Tomonori wrote:
> > 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 tested already, it works.

Great, thanks a lot!

I've just sent the patch.


> > 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.
> 
> will look at it later

Thanks. If it's due to huge memory, I try to work on it.
--
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/