Re: notify_change() WARN_ON being triggered on XFS.

[Dave Chinner]

On Wed, May 27, 2015 at 05:44:48PM -0400, Dave Jones wrote:
> WARNING: CPU: 1 PID: 29887 at fs/attr.c:198 notify_change+0x2e6/0x390()
> CPU: 1 PID: 29887 Comm: trinity-c13 Not tainted 4.1.0-rc5-gelk-debug+ #1
>  0000000000000009 ffff880041fb7b28 ffffffff967685f0 ffff8800bf7d12b8
>  0000000000000000 ffff880041fb7b68 ffffffff9607eaaa ffff880041fb7b58
>  0000000000000a00 ffff880073442510 000000000000888f ffff8800a61c2698
> Call Trace:
>  [<ffffffff967685f0>] dump_stack+0x4f/0x7b
>  [<ffffffff9607eaaa>] warn_slowpath_common+0x8a/0xc0
>  [<ffffffff9607eb9a>] warn_slowpath_null+0x1a/0x20
>  [<ffffffff9622c3f6>] notify_change+0x2e6/0x390
>  [<ffffffff9622a072>] file_remove_suid+0x92/0xb0
>  [<ffffffff962311f2>] ? __mnt_drop_write_file+0x12/0x20
>  [<ffffffff9622a138>] ? file_update_time+0xa8/0xf0
>  [<ffffffffc04e936e>] xfs_file_aio_write_checks+0x11e/0x160 [xfs]
>  [<ffffffffc04e9477>] xfs_file_dio_aio_write+0xc7/0x590 [xfs]
>  [<ffffffff9676cca3>] ? mutex_lock_nested+0x283/0x440
>  [<ffffffff9621318a>] ? pipe_wait+0x8a/0xb0
>  [<ffffffffc04e9dd5>] xfs_file_write_iter+0x105/0x120 [xfs]
>  [<ffffffff9620980d>] vfs_iter_write+0x6d/0xa0
>  [<ffffffff962417e4>] iter_file_splice_write+0x264/0x3c0
>  [<ffffffff962432a1>] SyS_splice+0x361/0x7d0
>  [<ffffffff9619fba3>] ? context_tracking_user_exit+0x13/0x20
>  [<ffffffff9677223c>] tracesys_phase2+0x84/0x89

There's a fix pending. Waiting on Al Viro to pick it up for the next
merge window...

Cheers,

Dave.
-- 
Dave Chinner
david@xxxxxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/