linux-kernel - Re: [PATCH] mm/shmem.c: Fix the missing unaccount on the failed path

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LSU.2.11.2009201141510.4318@eggly.anvils>
Date:   Sun, 20 Sep 2020 11:49:20 -0700 (PDT)
From:   Hugh Dickins <hughd@...gle.com>
To:     Tianjia Zhang <tianjia.zhang@...ux.alibaba.com>
cc:     Hugh Dickins <hughd@...gle.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Al Viro <viro@...iv.linux.org.uk>, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm/shmem.c: Fix the missing unaccount on the failed
 path

On Mon, 21 Sep 2020, Tianjia Zhang wrote:

> In function __shmem_file_setup(), shmem_unacct_size() is forgotten
> on the failed path, so add it.
> 
> Fixes: 93dec2da7b234 ("... and switch shmem_file_setup() to alloc_file_pseudo()")
> Cc: Al Viro <viro@...iv.linux.org.uk>
> Signed-off-by: Tianjia Zhang <tianjia.zhang@...ux.alibaba.com>
> ---
>  mm/shmem.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/mm/shmem.c b/mm/shmem.c
> index 8e2b35ba93ad..591410dc3541 100644
> --- a/mm/shmem.c
> +++ b/mm/shmem.c
> @@ -4200,8 +4200,10 @@ static struct file *__shmem_file_setup(struct vfsmount *mnt, const char *name, l
>  	if (!IS_ERR(res))
>  		res = alloc_file_pseudo(inode, mnt, name, O_RDWR,
>  				&shmem_file_operations);
> -	if (IS_ERR(res))
> +	if (IS_ERR(res)) {
>  		iput(inode);
> +		shmem_unacct_size(flags, size);
> +	}
>  	return res;
>  }
>  
> -- 
> 2.19.1.3.ge56e4f7

Looks mistaken to me.

Is this something you noticed by source inspection,
or something you have observed in practice?

I haven't tried exercising this path while injecting errors into
alloc_file_pseudo(); but what I'd expect to happen is that the
iput(inode), which you see already on that error path, will get
to evict the inode, which will entail calling shmem_evict_inode(),
which does that shmem_unacct_size() itself.

Hugh