On Mon, Oct 5, 2015 at 8:24 PM, Casey Schaufler <casey@xxxxxxxxxxxxxxxx> wrote: > On 10/4/2015 12:19 PM, Andreas Gruenbacher wrote: >> Add a hook to invalidate an inode's security label when the cached >> information becomes invalid. > > Where is this used? See the next patch in this patch queue, gfs2. > If I need to do the same for Smack or any other module, how would I know that > it works right? I haven't looked at Smack but if it does the same thing as SELinux, then label updates on one gfs2 nod ein a cluster won't become visible on other nodes without this fix, and with this fix they will. Andreas -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html