On 01/21/2015 11:51 AM, Andrey Ryabinin wrote: > With this patch kasan will be able to catch bugs in memory allocated > by slub. > Initially all objects in newly allocated slab page, marked as redzone. > Later, when allocation of slub object happens, requested by caller > number of bytes marked as accessible, and the rest of the object > (including slub's metadata) marked as redzone (inaccessible). > > We also mark object as accessible if ksize was called for this object. > There is some places in kernel where ksize function is called to inquire > size of really allocated area. Such callers could validly access whole > allocated memory, so it should be marked as accessible. > > Code in slub.c and slab_common.c files could validly access to object's > metadata, so instrumentation for this files are disabled.
This one doesn't apply on -next. Is there a missing commit? Applying: mm: slub: add kernel address sanitizer support for slub allocator fatal: sha1 information is lacking or useless (mm/slub.c). Repository lacks necessary blobs to fall back on 3-way merge. Cannot fall back to three-way merge. Patch failed at 0007 mm: slub: add kernel address sanitizer support for slub allocator When you have resolved this problem run "git am --resolved". If you would prefer to skip this patch, instead run "git am --skip". To restore the original branch and stop patching run "git am --abort". Thanks, Sasha -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
