[OpenAFS-devel] [PATCH] fix openafs crashes on linux 2.6.10-2.6.12, and all RHEL4 kernels

[Derrick J Brashear]

On Tue, 8 May 2007, chas williams - CONTRACTOR wrote:

> In message <Pine.GSO.4.61-042.0705081205540.1487@johnstown.andrew.cmu.edu>,Derr
> ick J Brashear writes:
>> allocate an extra amount of memory for each allocation, making it aligned,
>> and put a tag saying how to free it in each allocation, then the
>> alloc/free package and not the caller can decide how to allocate.
>
> this doesnt resolve the issue of 'is it safe for me to perform my
> operation with the memory the allocator gave me?'  for instance,
> it might not be safe to performance certain operations under a
> lock with pageable (from vmalloc) memory.

set a flag when you get the memory to ask for what you need.

of course, if you ask for non-pageable memory and you can't get it, then 
what?

we could do something gross involving a fixed pool of non-pageable memory 
(ick) or have multiple code paths to deal with whether you can lock or not 
(no) but what choices do we really have?

>> you're just saying that because you don't like panics.
>
> i love panic.
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel
>