On Tue, Apr 17, 2001 at 03:29:20PM -0600, Jeff V. Merkey wrote:
Added kmem_cache_destroy() to get around the problem. I'm still
curious as to why we need to panic at this point rather than return
an error.
Thanks
Jeff
>
>
> I noticed that subsequent calls to kmem_cache_create with the same name
> does not return an -EEXIST return code, but instead barfs and crashes
> with a bug at slab.c line 804. This occurs in 2.4.3.
>
> Is this the expected behavior for kmem_cache_create? I am using
> the slab allocator to create and maintain buffer head chains for
> asynch I/O.
>
> I would assume that if a valid tag existed, an error would be returned
> rather than the system crashing. I see the problem unloading then
> reloading the module on 2.4.3.
>
> Thanks,
>
> Jeff
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
