linux-kernel - Re: [solved] Yenta Cardbus allocation failure

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: <20061220194003.b0db1844.akpm@osdl.org>
Date:	Wed, 20 Dec 2006 19:40:03 -0800
From:	Andrew Morton <akpm@...l.org>
To:	"Markus Rechberger" <mrechberger@...il.com>
Cc:	linux-kernel@...r.kernel.org, Linus Torvalds <torvalds@...l.org>,
	Daniel Ritz <daniel.ritz@....ch>,
	Dominik Brodowski <linux@...inikbrodowski.net>
Subject: Re: [solved] Yenta Cardbus allocation failure

On Tue, 19 Dec 2006 01:12:07 +0100
"Markus Rechberger" <mrechberger@...il.com> wrote:

> I went on with investigating that problem and found the problem,
> though I'm not sure if that solution is acceptable..
> 
> seems like the memory range gets preallocated in setup-bus.c, and
> CARDBUS_MEM_SIZE defines that size.
> 
> I changed
> #define CARDBUS_MEM_SIZE        (32*1024*1024)
> to
> #define CARDBUS_MEM_SIZE        (48*1024*1024)
> 
> and now the system is able to allocate the resources for the 3rd
> pci/pcmcia function.
> 
> Can anyone please have a closer look at it too? I think the whole
> implementation isn't really good there..
> 
> so this is the new output of iomem:
> $ cat /proc/iomem
> ...
> 30000000-35ffffff : PCI Bus #02
>   30000000-32ffffff : PCI CardBus #03
> 36000000-360003ff : 0000:00:1f.1
> 39000000-3bffffff : PCI CardBus #03
>   39000000-39ffffff : 0000:03:00.0
>   3a000000-3affffff : 0000:03:00.1
>   3b000000-3bffffff : 0000:03:00.2 <- this one failed to allocate previously
> 3c000000-3effffff : PCI CardBus #07
> 41000000-43ffffff : PCI CardBus #07
> ...

This keeps happening.  Is there no way in which we can put this to bed
permanently, or does it require prior knowledge about what cardbus cards
the user owns?

Does the cardbus spec set an upper limit on these resource sizes?

Linus has wondered "how much does Windows use"?  How might we determine
that?
-
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/