On Thu, 1 Jun 2017, Hugh Dickins wrote: > CONFIG_SLUB_DEBUG_ON=y. My SLAB|SLUB config options are > > CONFIG_SLUB_DEBUG=y > # CONFIG_SLUB_MEMCG_SYSFS_ON is not set > # CONFIG_SLAB is not set > CONFIG_SLUB=y > # CONFIG_SLAB_FREELIST_RANDOM is not set > CONFIG_SLUB_CPU_PARTIAL=y > CONFIG_SLABINFO=y > # CONFIG_SLUB_DEBUG_ON is not set > CONFIG_SLUB_STATS=y Thats fine. > But I think you are now surprised, when I say no slub_debug options > were on. Here's the output from /sys/kernel/slab/pgtable-2^12/* > (before I tried the new kernel with Aneesh's fix patch) > in case they tell you anything... > > pgtable-2^12/poison:0 > pgtable-2^12/red_zone:0 > pgtable-2^12/reserved:0 > pgtable-2^12/sanity_checks:0 > pgtable-2^12/store_user:0 Ok so debugging was off but the slab cache has a ctor callback which mandates that the free pointer cannot use the free object space when the object is not in use. Thus the size of the object must be increased to accomodate the freepointer. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
