On Thu, Nov 07, 2013 at 05:58:03PM -0800, Olav Haugan wrote: > zsmalloc encodes a handle using the pfn and an object > index. On hardware platforms with physical memory starting > at 0x0 the pfn can be 0. This causes the encoded handle to be > 0 and is incorrectly interpreted as an allocation failure. Please list the known hardware platforms that have this issue, so that people have a chance to know if this patch is relevant for them or not. For example, should I include this in the stable releases because it affects systems that are shipping? Or is it just in "future" chips and it doesn't need to go there or not? Please make it easy for me to do this type of determination, I already asked you this question before, why didn't you include the information here as well (hint, that is why I asked you...) greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
