I've attached a small snippet of dmesg output (produced by "dmesg > file"). It's from kernel 2.6.5-1.358.
Notice that there are >130 spaces at the start of some lines, and those lines also have their data truncated. It looks as if some memcpy has a bad offset.
Arjan and Steve, is this a known bug that's solved in the latest 2.6.6 kernel?
selinux@lists.fedoraproject.org