Description of problem: After I did 'telinit 1' and 'telinit 3' I got during level 3 startup the following (on a screen but this is quoted from dmesg): Removing netfilter NETLINK layer. Slab corruption: (Not tainted) start=ffff81001d9a8000, len=4096 Call Trace:<ffffffff8016fa72>{check_poison_obj+141} <ffffffff801aea6b>{seq_read+125} <ffffffff8016fc46>{cache_alloc_debugcheck_after+55} <ffffffff8016ffa1>{kmem_cache_alloc+149} <ffffffff801aea6b>{seq_read+125} <ffffffff80165f6f>{audit_syscall_entry+305} <ffffffff8018dcbe>{vfs_read+199} <ffffffff8018e757>{sys_read+69} <ffffffff8010ec3c>{tracesys+209} 120: 6b 6b 6b 6b 6b 6b 6b 6b ff ff ff ff 00 00 00 00 ip_tables: (C) 2000-2002 Netfilter core team Netfilter messages via NETLINK v0.30. It does not happen every time but on the second or third try of 'telinit 1/telinit 3' I got the same "Slab corruption" again. Both messages look exactly the same with an exception of "start=ffff8100128bf000" this time. The above was on x86_64 and so far I did not try that on something else. Version-Release number of selected component (if applicable): kernel-2.6.14-1.1674_FC5 How reproducible: with a small effort - see above.
Is this still occuring in current builds ?
> Is this still occuring in current builds ? I tried to reproduce and failed. It is the case that originally this was not happening every time but it was rather easy to trigger. Do you have reasons to believe that the real underlying bug was fixed?
not in a 'point to specific change that fixed it' sense, but a lot of code has changed, and we've had slab debug on the whole time.. I'll close this for now, but feel free to reopen/file a new bug if something appears again.