From: Jiri Olsa <jolsa@redhat.com>
To: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
Cc: Ingo Molnar <mingo@elte.hu>, Jason Baron <jbaron@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] jump_label: fix jump_label update
Date: Mon, 20 Jun 2011 14:53:45 +0200 [thread overview]
Message-ID: <20110620125345.GC2056@jolsa.brq.redhat.com> (raw)
In-Reply-To: <4DFBB2D5.2060003@cn.fujitsu.com>
On Sat, Jun 18, 2011 at 04:02:29AM +0800, Xiao Guangrong wrote:
> The key of module is out of __stop___jump_table, it causes the events
> of modules does not work
right, I missed the case when the key is defined in the module itself
>
> This bug is introduced by commit: 7cbc5b8d4a775a43875a09e29c49a2a8195b5b2d
>
> Signed-off-by: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
> ---
> kernel/jump_label.c | 8 ++++++--
> 1 files changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/jump_label.c b/kernel/jump_label.c
> index fa27e75..dcad2fb 100644
> --- a/kernel/jump_label.c
> +++ b/kernel/jump_label.c
> @@ -375,11 +375,15 @@ int jump_label_text_reserved(void *start, void *end)
>
> static void jump_label_update(struct jump_label_key *key, int enable)
> {
> - struct jump_entry *entry = key->entries;
> + struct jump_entry *entry = key->entries, *stop = __stop___jump_table;
> + struct module *mod = __module_address((jump_label_t)key);
> +
> + if (mod)
> + stop = mod->jump_entries + mod->num_jump_entries;
this breaks !CONFIG_MODULES compilation
thanks,
jirka
>
> /* if there are no users, entry can be NULL */
> if (entry)
> - __jump_label_update(key, entry, __stop___jump_table, enable);
> + __jump_label_update(key, entry, stop, enable);
>
> #ifdef CONFIG_MODULES
> __jump_label_mod_update(key, enable);
> --
> 1.7.5.4
next prev parent reply other threads:[~2011-06-20 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 20:02 Xiao Guangrong
2011-06-20 12:53 ` Jiri Olsa [this message]
2011-06-20 18:58 ` Xiao Guangrong
2011-06-21 0:39 ` Steven Rostedt
2011-06-21 1:30 ` Steven Rostedt
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=20110620125345.GC2056@jolsa.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=xiaoguangrong@cn.fujitsu.com \
/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