2008/4/22, Jiri Slaby <jirislaby@xxxxxxxxx>:
> On 04/22/2008 12:54 AM, Paul E. McKenney wrote:
>
> > On Tue, Apr 22, 2008 at 12:26:04AM +0200, Jiri Slaby wrote:
> >
> > >
> > > > Having slub_debug enabled, tomorrow will be results, I guess...
> > > >
> > > Sorry, one more entry:
> > >
> > > 00000000000000f0 dentry.d_op (Zdenek, offset ? around 136)
> > >
> >
>
> Zdenek's is at offset 184.
>
>
> >
> > > 00f0000000000000 dentry.d_hash.next (me, offset 24)
> > > ffff81f02003f16c dentry.d_name.name (me, offset 56)
> > > memory ORed by 000000f000000000
> > > fffff0002004c1b0 file.f_mapping (me, offset 176)
> > > memory hole, it was something like
> > > (ffff81002004c1b0 & ~00000f0000000000) | 0000f00000000000?
> > > ffffffffffffffff dentry.d_hash.next (Rafael, offset ? around 24)
> > > -1, ~0ULL
> > >
> >
> > Are these running with CONFIG_PREEMPT_RCU? Grasping at straws, but
> > there are a couple of patches that need to move from -rt to mainline,
> > but mostly related to SELinux. So if both PREEMPT_RCU and SELinux
> > were in use, we might be missing "rcu-various-fixups.patch" from:
> >
>
> $ grep RCU .config
> CONFIG_CLASSIC_RCU=y
> # CONFIG_RCU_TORTURE_TEST is not set
> $ grep SECU .config
> # CONFIG_EXT4DEV_FS_SECURITY is not set
> # CONFIG_SECURITY is not set
> # CONFIG_SECURITY_FILE_CAPABILITIES is not set
>
> I guess not.
>
> BTW the corruption I mentioned earlier was char 'ð' and it's ('p' | 0xf0)
> in latin2. I think it was set_ðending_irq IIRC. Whatever, it won't help us.
>
I've kernel compiled with preemptible RCU & Security - but usually
using selinux=off as a kernel parameter
Zdenek
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
