[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEkB2ERMqs=xbt4H-1ro0zAQryoQUH=N5iJop-CKbSOo_mTk3w@mail.gmail.com>
Date: Tue, 1 Oct 2019 12:34:59 -0500
From: Navid Emamdoost <navid.emamdoost@...il.com>
To: Markus Elfring <Markus.Elfring@....de>
Cc: linux-fsdevel@...r.kernel.org, Navid Emamdoost <emamd001@....edu>,
Stephen McCamant <smccaman@....edu>, Kangjie Lu <kjlu@....edu>,
David Sterba <dsterba@...e.com>,
Thomas Gleixner <tglx@...utronix.de>,
Al Viro <viro@...iv.linux.org.uk>,
Jeff Layton <jlayton@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Deepa Dinamani <deepa.kernel@...il.com>,
"Gustavo A. R. Silva" <gustavo@...eddedor.com>,
LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH v2] fs: affs: fix a memory leak in affs_remount
Hi Markus, thanks for your suggestions for improving the quality of
the patch. At the moment I prefer first get a confirmation from
contributors about the leak and then work on any possible improvements
for the patch.
Thanks,
Navid.
On Tue, Oct 1, 2019 at 3:31 AM Markus Elfring <Markus.Elfring@....de> wrote:
>
> > The allocated memory for new_opts is only released if pare_options fail.
>
> Can the following wording be nicer?
>
> The allocated memory for the buffer “new_opts” will be released
> only if a call of the function “parse_options” failed.
>
>
> > The release for new_opts is added.
>
> * How do you think about the change possibility to delete questionable
> source code here?
>
> * Would you like to complete the data processing for corresponding options
> any more?
>
>
> > -- fix a type in title, …
>
> Please avoid typos also in your version comments.
>
>
> > ---
>
> I suggest to replace this second delimiter by a blank line.
>
> Regards,
> Markus
--
Navid.
Powered by blists - more mailing lists