From: Rasmus Villemoes <linux@rasmusvillemoes.dk>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: David Woodhouse <David.Woodhouse@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Arjun Sreedharan <arjun024@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: krealloc in kernel/params.c
Date: Thu, 16 Oct 2014 11:49:28 +0200 [thread overview]
Message-ID: <87fveo1h07.fsf@rasmusvillemoes.dk> (raw)
In-Reply-To: <87r3yaapyf.fsf@rustcorp.com.au> (Rusty Russell's message of "Wed, 15 Oct 2014 15:29:04 +1030")
On Wed, Oct 15 2014, Rusty Russell <rusty@rustcorp.com.au> wrote:
> Rasmus Villemoes <linux@rasmusvillemoes.dk> writes:
>> It is likely that I'm just missing something trivial, but I have
>> a hard time understanding 63662139e ("params: Fix potential
>> memory leak in add_sysfs_param()").
>
> Yes, it was a bad commit, and we've been discussing it, see:
>
> [PATCH] params: fix potential memory leak in add_sysfs_param()
>
> The only error case we are about is when add_sysfs_param()
> is called from module_param_sysfs_setup(): the in-kernel cases
> at boot time are assumed not to fail.
>
> That call should invoke free_module_param_attrs() when it fails,
> rather than relying on add_sysfs_param() to clean up.
>
> Don't patch bad code - rewrite it. (Kernigan and Plauger)
>
> How's this?
>
> params: cleanup sysfs allocation
>
> commit 63662139e519ce06090b2759cf4a1d291b9cc0e2 attempted to patch a
> leak (which would only happen on OOM, ie. never), but it didn't quite
> work.
>
> This rewrites the code to be as simple as possible. add_sysfs_param()
> adds a parameter. If it fails, it's the caller's responsibility to
> clean up the parameters which already exist.
>
> The kzalloc-then-always-krealloc pattern is perhaps overly simplistic,
> but this code has clearly confused people. It worked on me...
>
I think kzalloc immediately followed by kreallocing the returned value
is rather ugly. Other than that:
> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
>
> diff --git a/kernel/params.c b/kernel/params.c
> index db97b791390f..5b8005d01dfc 100644
> --- a/kernel/params.c
> +++ b/kernel/params.c
> @@ -603,68 +603,58 @@ static __modinit int add_sysfs_param(struct module_kobject *mk,
> const struct kernel_param *kp,
> const char *name)
> {
> - struct module_param_attrs *new;
> - struct attribute **attrs;
> - int err, num;
> + struct module_param_attrs *new_mp;
> + struct attribute **new_attrs;
> + unsigned int i;
>
> /* We don't bother calling this with invisible parameters. */
> BUG_ON(!kp->perm);
>
> if (!mk->mp) {
> - num = 0;
> - attrs = NULL;
> - } else {
> - num = mk->mp->num;
> - attrs = mk->mp->grp.attrs;
> + /* First allocation. */
> + mk->mp = kzalloc(sizeof(*mk->mp), GFP_KERNEL);
> + if (!mk->mp)
> + return -ENOMEM;
free_module_param_attrs does not check mk->mp for being NULL before
kfree'ing mk->mp->grp.attrs, so this will oops.
Rasmus
next prev parent reply other threads:[~2014-10-16 9:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 20:44 Rasmus Villemoes
2014-10-15 4:59 ` Rusty Russell
2014-10-16 9:49 ` Rasmus Villemoes [this message]
2014-10-16 22:59 ` Rusty Russell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fveo1h07.fsf@rasmusvillemoes.dk \
--to=linux@rasmusvillemoes.dk \
--cc=David.Woodhouse@intel.com \
--cc=akpm@linux-foundation.org \
--cc=arjun024@gmail.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome