[Pvfs2-users] Segmentation fault on insmod pvfs2.ko (pvfs2.6.3-patched, kernel 2.6.22-rc4)

[Murali Vilayannur]

Ah pete! thanks for the clarification. I was looking at 2.6.21 hoping
that that would be the latest.
It does look like a new ish kernel feature. I am sorta out of the loop
on the newest kernel issues :(
Let me look at the code a little bit and  work on a patch and send it
later today.
Basically, SLAB is deprecated. We need to find out an alternate way/interface.
thanks!
Murali

On 6/27/07, Pete Wyckoff <pw at osc.edu> wrote:
> murali.vilayannur at gmail.com wrote on Wed, 27 Jun 2007 00:50 -0700:
> > Something really bad is going on with these new kernels. This is the
> > 2nd (or perhaps 3rd) time that someone reported this exact same error.
> > Weird. I cannot think of any reason based on a cursory code glance
> > that could explain this error.
> > Am I missing something, Pete, Sam? Can you guys reproduce this error?
> >
> > kmem_cache_create gives this error message on
> > - a NULL name - which is not the case
> > - if called from an interrupt context - I doubt if this is possible at all.
> > - size < 4 bytes: not possible. pvfs2_inode_t is 392 bytes
> > - size > 128K: again not possible
> > - no constructor && a destructor specified - not possible from a code
> > review.
>
> Actually latest kernels don't allow a dtor at all.  Rev
> c59def9f222d44bb7e2f0a559f2906191a0862d7 for those playing
> along at home.
>
> We use dtors for the inode cache and devreq cache.  But it's not
> obivous to me how to move that functionality elsewhere, at a quick
> glance.  Maybe you'll know?
>
>                 -- Pete
>