On Wed, 4 Jun 2014, Jan Kara wrote: > On Wed 04-06-14 10:33:00, Sasha Levin wrote: > > Hi all, > > > > While fuzzing with trinity inside a KVM tools guest running the latest -next > > kernel I've stumbled on the following spew: > Hum, I'd really suspect more a SLUB bug - the area has poisoning 0x6b > (POISON_FREE) instead of expected poisoning 0x5a (POISON_INUSE). Or maybe > I'm just mistaken - could some SLUB guy comment? Well yes that is really weird. The last byte is 0xa5 (end of object) which indicates that the padding space has been treated as an object. Could be metadata corruption. The slab is empty but there is an object allocated in there??? -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
