linux-kernel - Re: New conflict message in latest GIT

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]

Message-ID: <4886E540.2070106@keyaccess.nl>
Date:	Wed, 23 Jul 2008 10:01:04 +0200
From:	Rene Herman <rene.herman@...access.nl>
To:	Fabio Comolli <fabio.comolli@...il.com>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...l.org>,
	Bjorn Helgaas <bjorn.helgaas@...com>
Subject: Re: New conflict message in latest GIT

On 23-07-08 09:17, Fabio Comolli wrote:

>> http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.26-rc8/2.6.26-rc8-mm1/broken-out/pnp-have-quirk_system_pci_resources-include-io-resources.patch
> 
> I did not add it manually for sure. By the way, I don't see any ACPI
> related problems with this kernel.

You can just look at drivers/pnp/quirks.c:quirk_system_pci_resources() 
and see if it's still IORESOURCE_MEM only (current linus) or includes 
IORESOURCE_IO resources as per that patch.

Had a momentary notion that if we specifically exclude ACPI in favour of 
PCI as that patch does this could _cause_ the message -- before, the PCI 
smbus driver just would've failed but perhaps you don't even have such a 
driver or something.

Probably way of base. Just had a deja vu to my own soundcard trouble.

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