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, 4 Aug 2009 09:45:10 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	David Miller <davem@...emloft.net>
Cc:	joerg.roedel@....com, fujita.tomonori@....ntt.co.jp,
	reif@...thlink.net, sparclinux@...r.kernel.org,
	linux-kernel@...r.kernel.org, x86@...nel.org, tony.luck@...el.com,
	akpm@...ux-foundation.org
Subject: Re: [PATCH v2 0/8] sparc: use asm-generic/dma-mapping-common.h and
	pci-dma-compat.h


* David Miller <davem@...emloft.net> wrote:

> From: Ingo Molnar <mingo@...e.hu>
> Date: Mon, 3 Aug 2009 07:56:08 +0200
> 
> > I'm wondering how sparc32 handles core_kernel_text() & friends? 
> > 
> > Those functions already assume that the bits between _stext and 
> > _etext are all core kernel text and not generic pages freed back 
> > to the buddy.
> 
> They won't work for such pages obviously.  Shows how many sparc32 
> users who trigger this case of actually freeing those pages and 
> using such facilities there actually are :-)

:)

I suspect the other bit is probably that core_kernel_text() really 
didnt use to have any critical use at all - just debugging/lockdep 
mostly. So no functionality broke for people to report.

Such bugs often have years of latency on x86 too - we recently fixed 
one that was there for over a year and nobody noticed:

 4a44bac: symbols, stacktrace: look up init symbols after module symbols

	Ingo
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ