On Fri, 6 Sep 2013 10:18:52 -0400
Dave Jones <da...@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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
