From: Rusty Russell <rusty@rustcorp.com.au>
To: Andrey Tsyvarev <tsyvarev@ispras.ru>
Cc: Andrey Tsyvarev <tsyvarev@ispras.ru>, linux-kernel@vger.kernel.org
Cc: Peter Zijlstra <peterz@infradead.org>, Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] kernel/module.c: Free lock-classes if parse_args failed
Date: Tue, 20 Jan 2015 17:07:19 +1030 [thread overview]
Message-ID: <87iog2arfk.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1421216708-1975-1-git-send-email-tsyvarev@ispras.ru>
Andrey Tsyvarev <tsyvarev@ispras.ru> writes:
> parse_args call module parameters' .set handlers, which may use locks defined in the module.
> So, these classes should be freed in case parse_args returns error(e.g. due to incorrect parameter passed).
Thanks, this seems right. Applied.
But this makes me ask: where is lockdep_free_key_range() called on the
module init code? It doesn't seem to be at all...
Confused,
Rusty.
> Signed-off-by: Andrey Tsyvarev <tsyvarev@ispras.ru>
> ---
> kernel/module.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/kernel/module.c b/kernel/module.c
> index 3965511..2b44de4 100644
> --- a/kernel/module.c
> +++ b/kernel/module.c
> @@ -3311,6 +3311,9 @@ static int load_module(struct load_info *info, const char __user *uargs,
> module_bug_cleanup(mod);
> mutex_unlock(&module_mutex);
>
> + /* Free lock-classes: */
> + lockdep_free_key_range(mod->module_core, mod->core_size);
> +
> /* we can't deallocate the module until we clear memory protection */
> unset_module_init_ro_nx(mod);
> unset_module_core_ro_nx(mod);
> --
> 1.8.3.1
next prev parent reply other threads:[~2015-01-20 6:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 6:25 [PATCH] kernel/module.c: Free lock-classes if parse_args failed Andrey Tsyvarev
2015-01-20 6:37 ` Rusty Russell [this message]
2015-01-20 7:47 ` Andrey Tsyvarev
2015-01-21 1:40 ` Rusty Russell
2015-01-21 10:49 ` Andrey Tsyvarev
2015-01-22 0:40 ` Rusty Russell
2015-01-22 9:27 ` Andrey Tsyvarev
2015-01-20 9:48 ` Peter Zijlstra
2015-02-19 0:12 ` Ingo Molnar
2015-02-19 11:57 ` Peter Zijlstra
2015-02-19 12:24 ` Ingo Molnar
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=87iog2arfk.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=tsyvarev@ispras.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.