David Teigland writes:
> but why can't you return NULL here on failure like you do for
> find_lock_page()?
because create is set
Yes, but looking at (some of the) top-level callers, there's no real reason
why create must not fail. Am I missing something here?
> gfs2-02.patch:+ RETRY_MALLOC(bd = kmem_cache_alloc(gfs2_bufdata_cachep,
> GFP_KERNEL),
> -> GFP_NOFAIL
It looks to me like NOFAIL does nothing for kmem_cache_alloc().
Am I seeing that wrong?
It is passed to the page allocator just like with kmalloc() which uses
__cache_alloc() too.
Pekka
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |