[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ec7d3fdb-445b-7f4e-d6e6-77c6ae9a5732@web.de>
Date: Mon, 30 Sep 2019 08:02:53 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Navid Emamdoost <navid.emamdoost@...il.com>,
linux-fsdevel@...r.kernel.org
Cc: LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org,
Navid Emamdoost <emamd001@....edu>, Kangjie Lu <kjlu@....edu>,
Stephen McCamant <smccaman@....edu>,
Al Viro <viro@...iv.linux.org.uk>,
David Sterba <dsterba@...e.com>,
Deepa Dinamani <deepa.kernel@...il.com>,
"Gustavo A. R. Silva" <gustavo@...eddedor.com>,
Kees Cook <keescook@...omium.org>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] fs: affs: fix a memory leak in affs_remount
* Please avoid typos in the commit message.
* I would prefer an other wording for the change description.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id=97f9a3c4eee55b0178b518ae7114a6a53372913d#n151
> But this is not actually used later!
Can this information trigger the deletion of questionable source code
instead of adding a missing function call “kfree(new_opts)”?
How do you think about to add the tag “Fixes”?
Regards,
Markus
Powered by blists - more mailing lists