user/sven/linux.git/kernel/resource.c, branch v2.6.12.2

[PATCH] pci enumeration on ixp2000: overflow in kernel/resource.c

2005-04-16T22:25:58Z

IXP2000 (ARM-based) platforms use a separate 'struct resource' for PCI MEM space. Resource allocation for PCI BARs always fails because the 'root' resource (the IXP2000 PCI MEM resource) always has the entire address space (00000000-ffffffff) free, and find_resource() calculates the size of that range as ffffffff-00000000+1=0, so all allocations fail because it thinks there is no space. (akpm: pls. double-check) Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

[PATCH] Make lots of things static

2005-03-12T00:40:56Z

This is a megarollup of ~60 patches which give various things static scope. Signed-off-by: Adrian Bunk Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

[PATCH] Lock initializer cleanup (Core)

2005-01-08T06:09:06Z

Kernel core files converted to use the new lock initializers. Signed-off-by: Thomas Gleixner Acked-by: Ingo Molnar Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

Lock-annotate some kernel functions as an example of how it works.

2004-10-31T00:51:14Z

In particular, a function that is called with a lock held, and releases it only to re-acquire it needs to be annotated as such, since otherwise sparse will complain about an unexpected unlock, even though "globally" the lock is constant over the call.

Fix "insert_resource()" nesting bug

2004-08-27T12:29:11Z

It used to create totally impossible resource trees in some circumstances where it was asked to insert a conflicting resource. We never noticed, because it wasn't used that much. Make it return the proper error instead.

[PATCH] insert_resource fix

2004-06-15T13:19:55Z

I noticed that insert_resource() incorrectly handles the case of an existing parent resource with the same ending address as a newly added child. This results in incorrect nesting, like the following: # cat /proc/ioports 002f0000-002fffff : PCI Bus #48 00200000-002fffff : /pci@800000020000003 Signed-off-by: John Rose Signed-off-by: Linus Torvalds

[PATCH] PCI: insert_resource can succeed and return an error

2004-03-19T06:07:09Z

If we start again, we can return an error even if we were successful. Reset the result to 0 before beginning again. Why don't we use a tailcall here?

[PATCH] Make insert_resource work for alder IOAPIC resources

2004-02-24T12:03:10Z

From: James Bottomley This is a necessary precursor patch for getting the Intel Alder motherboard working (it has a PCI device corresponding to the IO-APIC which has to be forcibly inserted into the machine's reserved memory region). Eric Biederman was going to come up with a more comprehensive fix, but in the meantime, this is the minimum necessary to get insert_resource to work when the covering region is larger than the resource being inserted.

[PATCH] Fix __release_region() race

2004-02-18T12:56:48Z

From: MAEDA Naoaki I am testing PCI hot-plug in 2.6.2 kernel, but sometimes a struct resource tree in kernel/resource.c was broken if multiple hot-plug requests are issued at the same time. The reason is lots of drivers call release_region() on hot removal, and __release_region(), which is invoked by release_region() macro, changes the tree without holding a writer lock for resource_lock. I think __release_region() must hold a writer lock as well as __request_region() does. A following patch fixes the issue in my environment.

[PATCH] adjust_resource()

2004-02-06T07:07:04Z

I need this to cope with some devices on PA-RISC and Russell also needs something like it for PCMCIA.