linux-kernel - Re: Linux 2.6.28-rc8

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:	Fri, 12 Dec 2008 08:11:35 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Arjan van de Ven <arjan@...radead.org>
cc:	Ingo Molnar <mingo@...e.hu>, Pekka Enberg <penberg@...helsinki.fi>,
	Frans Pop <elendil@...net.nl>, Eric Anholt <eric@...olt.net>,
	nix.or.die@...glemail.com, linux-kernel@...r.kernel.org,
	rjw@...k.pl, Yinghai Lu <yinghai@...nel.org>
Subject: Re: Linux 2.6.28-rc8

On Fri, 12 Dec 2008, Arjan van de Ven wrote:
> 
> another thing we could do is try to only warn if you cross bar
> boundaries but not if you cross other user-of-the-resource boundaries.

Hmm. We could use the res->flags for this. But I'm not sure non-PCI 
resources fill those in correctly.

A pure "busy" allocation (ie a driver marker) would generally have just 
the IORESOURCE_BUSY bit set, while a real PCI hardware resource will have 
other bits set (ie the IORESOURCE_IO/MEM bits) and not be marked BUSY.

Maybe just ignoring resources with BUSY set, as they are driver markers 
rather than actual HW resources.

			Linus
--
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/