Bugzilla 205592:
    
    One problem we've found is that under heavy system load, memory could
    be in shortage that results in kmalloc() failure. In previous versions,
    upon kmalloc() failure, in certain code paths, sometime it was impossible
    to back out - so GFS either panic or hung. In newer versions of GFS, a fix
    was added to allow memory allocation falling back to vmalloc() if kmalloc()
    failed. Unfortuntely, the linux/vmalloc.h header was not added. Since the
    compiler has not been not able to get the correct vmalloc() prototype, it
    assumes the default that casts vmalloc() return code to "int" which is 4
    byes. This could cause panic with 64 machines (e.g. x86_64) that uses 8
    bytes addressing.