On Fri, Nov 25, 2016 at 11:38 AM, Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx> wrote: > I'm not sure we're talking about the same thing. > The patch doesn't touch to anything related to address space > which have to be inherited by the '&/adressof' operator. > The patch only concern what must be done with MOD_STATIC, > MOD_EXTERN & MOD_TOPLEVEL when we're taking the address of an object. > This is certainly one point where taking the address of an object > and then later dereferencing the pointer is *not* the same as using > directly the object, it deosn't matter anymore if the object was > static. Sorry I jump the conclusion. If it is only concern with MOD_STATIC, MOD_EXTERN & MOD_TOPLEVEL, that is not a bug issue at all. I thought you are going to extend that logic to other modifier bits as well. Chris -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
