[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20191030114430.GE3001@suse.cz>
Date: Wed, 30 Oct 2019 12:44:31 +0100
From: David Sterba <dsterba@...e.cz>
To: Navid Emamdoost <navid.emamdoost@...il.com>
Cc: emamd001@....edu, smccaman@....edu, kjlu@....edu,
David Sterba <dsterba@...e.com>,
Jeff Layton <jlayton@...nel.org>,
Kees Cook <keescook@...omium.org>,
Deepa Dinamani <deepa.kernel@...il.com>,
"Gustavo A. R. Silva" <gustavo@...eddedor.com>,
Thomas Gleixner <tglx@...utronix.de>,
Al Viro <viro@...iv.linux.org.uk>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] fs: affs: fix a memory leak in affs_remount
On Wed, Oct 02, 2019 at 04:52:37PM -0500, Navid Emamdoost wrote:
> In affs_remount if data is provided it is duplicated into new_opts.
> The allocated memory for new_opts is only released if pare_options fail.
> But the variable is not used anywhere. So the new_opts should be
> removed.
>
> Fixes: c8f33d0bec99 ("affs: kstrdup() memory handling")
> Signed-off-by: Navid Emamdoost <navid.emamdoost@...il.com>
> ---
> Changes in v2:
> -- fix typo
> Changes in v3:
> -- remove the call to kstrdup, as new_opts is not used anymore.
Added it to affs queue. There are still typos in the changelog and this
was pointed out, and v3 lacks the explanations I replied to v2. I'll
fix it up.
Powered by blists - more mailing lists