> What is the underlying filesystem? > Do you if your system also tries to set security.capability xattr > or just tries to read them? The underlying filesystem is ext4. I'll find out about security.capability xattr is set or not (guess I have to add log in vfs). > > I would check the change (from v4.14): > 8db6c34f1dbc Introduce v3 namespaced file capabilities > > I suggest that you continue down the rabbit hole to see > which check returns -EINVAL, whether inside ovl_xattr_get() > or deeper inside nested vfs_getxattr(). > > Other than that, you can try this overlayfs backport branch: > https://github.com/amir73il/linux/commits/overlayfs-4.9.y-17 > It contains backported overlayfs patches up to v4.17 based > off of v4.9.102. > > If problem is not reproduced on the backported branch then > chances are the problem has to do with interaction between > overlayfs and a change to another subsystem (e.g. v3 > namespaced file capabilities). > > Thanks, > Amir. Thanks those suggestions, I'll test them and go back to you then. Thanks, Eddie -- To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
