From: Steven Rostedt <rostedt@goodmis.org>
To: Dave Jones <davej@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ftrace 'failed to modify' bug when loading reiserfs.ko
Date: Fri, 6 Sep 2013 10:24:13 -0400 [thread overview]
Message-ID: <20130906102413.2e52d337@gandalf.local.home> (raw)
In-Reply-To: <20130906141852.GA18708@redhat.com>
On Fri, 6 Sep 2013 10:18:52 -0400
Dave Jones <davej@redhat.com> wrote:
> > > 00000000000028b0 <reiserfs_init_bitmap_cache>:
> > >
> > > return bh;
> > > }
> > >
> > > int reiserfs_init_bitmap_cache(struct super_block *sb)
> > > {
> > > 28b0: e8 00 00 00 00 callq 28b5 <reiserfs_init_bitmap_cache+0x5>
> >
> > That looks to be the call to fentry, but without being resolved. What
> > we saw in the previous report wasn't 0xe8 but 0x14, and it was
> > unresolved after loading!
> >
> > I'm surprised that the module built with a different
> > DEBUG_KOBJECT_RELEASE config would load. Does it not affect module
> > versions?
>
> # CONFIG_MODVERSIONS is not set
>
Is it really safe to load modules that were compiled with different
options? Sounds like a failure in the install scripts to me.
Anyway, if you can send me the binary file, I can take a deeper look at
it.
-- Steve
next prev parent reply other threads:[~2013-09-06 14:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 1:19 Dave Jones
2013-09-06 1:28 ` Steven Rostedt
2013-09-06 1:34 ` Dave Jones
2013-09-06 1:44 ` Steven Rostedt
2013-09-06 1:48 ` Dave Jones
2013-09-06 1:51 ` Steven Rostedt
2013-09-06 3:58 ` Dave Jones
2013-09-06 13:32 ` Steven Rostedt
2013-09-06 14:18 ` Dave Jones
2013-09-06 14:24 ` Steven Rostedt [this message]
2013-09-06 14:41 ` Kyle McMartin
2013-09-06 15:22 ` Dave Jones
2013-09-06 15:34 ` Steven Rostedt
2013-09-06 15:46 ` Josh Boyer
2013-09-06 16:07 ` Steven Rostedt
2013-09-06 16:12 ` Josh Boyer
2013-09-06 16:40 ` richard -rw- weinberger
2013-09-06 17:50 ` Josh Boyer
2013-09-06 16:44 ` 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=20130906102413.2e52d337@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®