Re: kernel/resource.c breakage

Jeff Garzik (jgarzik@pobox.com)
Sat, 03 Jul 1999 21:33:52 -0400

Mikael Pettersson wrote:
>
> Summary: kernel/resource.c, in kernel 2.3.7 and later,
> is semantically incompatible with previous versions,
> and may break existing working code.
>
> The main problem is release_region(). Previously it would
> discard all information about the region. Now it _keeps_
> the region description (base+extent), but gives it a magic
> marker (name==NULL). The new check_region() and request_region()
> will allow an existing "magic" region to be reallocated in its
> entirety. Other allocations that partially interfere with a
> "magic" region will not succeed.

There was disagreement from several people about this... Several people
thought that the resource allocation code should not leave info around
after it has been released, resulting in the behavior you describe.

Jeff


-- 
He's pretty fly for a rabbi


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/