On Thu, Oct 06, 2016 at 08:20:17AM -0400, CAI Qian wrote: > > > ----- Original Message ----- > > From: "Al Viro" <viro@xxxxxxxxxxxxxxxxxx> > > To: "CAI Qian" <caiqian@xxxxxxxxxx> > > Cc: "tj" <tj@xxxxxxxxxx>, "Linus Torvalds" <torvalds@xxxxxxxxxxxxxxxxxxxx>, "Dave Chinner" <david@xxxxxxxxxxxxx>, > > "linux-xfs" <linux-xfs@xxxxxxxxxxxxxxx>, "Jens Axboe" <axboe@xxxxxxxxx>, "Nick Piggin" <npiggin@xxxxxxxxx>, > > linux-fsdevel@xxxxxxxxxxxxxxx > > Sent: Wednesday, October 5, 2016 4:05:22 PM > > Subject: Re: local DoS - systemd hang or timeout (WAS: Re: [RFC][CFT] splice_read reworked) > > > > On Wed, Oct 05, 2016 at 02:57:04PM -0400, CAI Qian wrote: > > > > > Not sure if this related, and there is always a lockdep regards procfs > > > happened > > > below unless masking by other lockdep issues before the cgroup hang. Also, > > > this > > > hang is always reproducible. > > > > Sigh... Let's get the /proc/*/auxv out of the way - this should deal with > > it: > So I applied both this and the sanity patch, and both original sanity and the > proc warnings went away. However, the cgroup hang can still be reproduced as > well as this new xfs internal error below, > > [16921.141233] XFS (dm-0): Internal error XFS_WANT_CORRUPTED_RETURN at line 5619 of file fs/xfs/libxfs/xfs_bmap.c. Caller xfs_bmap_shift_extents+0x1cc/0x3a0 [xfs] > [16921.157694] CPU: 9 PID: 52920 Comm: trinity-c108 Not tainted 4.8.0-rc8-splice-fixw-proc+ #4 iIt found a delayed allocation extent in the extent map after flushing all the dirty data in the file. Something else has gone wrong, this corruption detection is just the messenger. Maybe memory corruption? Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- 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
