On Mon, Jun 18, 2018 at 08:17:46PM -0600, Ross Zwisler wrote:
> During some xfstest runs on next-20180615 I hit the following with DAX +
> generic/388:
>
> ================================================
> WARNING: lock held when returning to user space!
> 4.17.0-next-20180615-00001-gf09d99951966 #2 Not tainted
> ------------------------------------------------
> fsstress/6598 is leaving the kernel with locks still held!
> 2 locks held by fsstress/6598:
> #0: 00000000d8f89e14 (&sb->s_type->i_mutex_key#13){++++}, at: xfs_ilock+0x211/0x310
> #1: 000000005cc93137 (&(&ip->i_mmaplock)->mr_lock){++++}, at: xfs_ilock+0x1eb/0x310
What errors occurred before this? generic/388 is testing all sorts
of error paths by randomly shutting down the filesystem, so it'e
entirely possible that we've leaked those locks (XFS_IOLOCK and
XFS_MMAPLOCK) on some rarely travelled error path. The prior errors
might help identify that path.
> XFS: Assertion failed: !rwsem_is_locked(&inode->i_rwsem), file: fs/xfs/xfs_super.c, line: 966
As this is just a follow on issue at unmount where we expect the
inode to be unlocked before tearing it down - it's just a messenger,
not the smoking gun...
Cheers,
Dave.
--
Dave Chinner
david@xxxxxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
