Hi Krisztian,
> If we're writing an extended attribute used by IMA, don't
> try to lock sb_writers (mnt_want_write) or i_mutex. We're
> being called from ima_file_free and the necessary locks
> are already being held. Trying to lock them again will
> deadlock.
But it probably isn't the only function calling ovl_setxattr(). So in
addition to testing S_IMA, only if the security.ima xattr is being set,
would this be safe.
Mimi
> In practice we test if the real inode has the S_IMA flag
> set and if it does we call __vfs_setxattr_noperm instead
> of the usual vfs_setxattr we call for all other cases.
>
> Signed-off-by: Krisztian Litkey <kli@xxxxxx>
> ---
> fs/overlayfs/inode.c | 24 ++++++++++++++++++------
> 1 file changed, 18 insertions(+), 6 deletions(-)
>
> diff --git a/fs/overlayfs/inode.c b/fs/overlayfs/inode.c
> index b29036a..9257e8d 100644
> --- a/fs/overlayfs/inode.c
> +++ b/fs/overlayfs/inode.c
> @@ -222,12 +222,18 @@ static bool ovl_is_private_xattr(const char *name)
> int ovl_setxattr(struct dentry *dentry, const char *name,
> const void *value, size_t size, int flags)
> {
> - int err;
> + int err, ima;
> struct dentry *upperdentry;
> + struct inode *inode;
>
> - err = ovl_want_write(dentry);
> - if (err)
> - goto out;
> + inode = ovl_dentry_real(dentry)->d_inode;
> + ima = IS_IMA(inode);
> +
> + if (!ima) {
> + err = ovl_want_write(dentry);
> + if (err)
> + goto out;
> + }
>
> err = -EPERM;
> if (ovl_is_private_xattr(name))
> @@ -238,10 +244,16 @@ int ovl_setxattr(struct dentry *dentry, const
> char *name,
> goto out_drop_write;
>
> upperdentry = ovl_dentry_upper(dentry);
> - err = vfs_setxattr(upperdentry, name, value, size, flags);
> +
> + if (!ima)
> + err = vfs_setxattr(upperdentry, name, value, size, flags);
> + else
> + err = __vfs_setxattr_noperm(upperdentry, name, value, size,
> + flags);
>
> out_drop_write:
> - ovl_drop_write(dentry);
> + if (!ima)
> + ovl_drop_write(dentry);
> out:
> return err;
> }
> --
> 2.5.5
>
--
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
