Re: fs: pipe: memory corruption in inode_cache

2014-03-18 Thread Sasha Levin
Ping? this is still showing up in -next. On 03/02/2014 09:13 PM, Sasha Levin wrote: Hi all, While fuzzing with trinity inside a KVM tools guest running latest -next kernel I've stumbled on the following spew: [ 315.799264]

Re: fs: pipe: memory corruption in inode_cache

2014-03-18 Thread Sasha Levin
Ping? this is still showing up in -next. On 03/02/2014 09:13 PM, Sasha Levin wrote: Hi all, While fuzzing with trinity inside a KVM tools guest running latest -next kernel I've stumbled on the following spew: [ 315.799264]

fs: pipe: memory corruption in inode_cache

2014-03-02 Thread Sasha Levin
Hi all, While fuzzing with trinity inside a KVM tools guest running latest -next kernel I've stumbled on the following spew: [ 315.799264] = [ 315.800055] BUG inode_cache (Tainted: GB W ): Object padding

fs: pipe: memory corruption in inode_cache

2014-03-02 Thread Sasha Levin
Hi all, While fuzzing with trinity inside a KVM tools guest running latest -next kernel I've stumbled on the following spew: [ 315.799264] = [ 315.800055] BUG inode_cache (Tainted: GB W ): Object padding