On 12/11/24 09:47, Johannes Thumshirn wrote:
> >
> And another thing (sorry for spamming you)
>
> When running the test on for-next (HEAD == e82c936293a) with lockdep
> enabled I get the following:
>
>
> johannes@nuc:ci$ cat ../fstests/results/btrfs/333.dmesg
> [ 5.826816] run fstests btrfs/333 at 2024-11-12 09:43:20
> [ 6.992664] BTRFS: device fsid c92bd0ac-9334-40e5-8c01-75a45093c706
> devid 1 transid 6 /dev/nvme1n1 (259:2) scanned by mount (659)
> [ 6.994951] BTRFS info (device nvme1n1): first mount of filesystem
> c92bd0ac-9334-40e5-8c01-75a45093c706
> [ 6.996139] BTRFS info (device nvme1n1): using crc32c (crc32c-intel)
> checksum algorithm
> [ 6.997099] BTRFS info (device nvme1n1): using free-space-tree
> [ 7.000920] BTRFS info (device nvme1n1): checking UUID tree
>
> [ 7.465790] ================================================
> [ 7.466415] WARNING: lock held when returning to user space!
> [ 7.467024] 6.12.0-rc7+ #1044 Not tainted
> [ 7.467470] ------------------------------------------------
> [ 7.468135] btrfs_encoded_r/703 is leaving the kernel with locks
> still held!
> [ 7.468955] 1 lock held by btrfs_encoded_r/703:
> [ 7.469486] #0: ffff8881163ca4e0
> (&sb->s_type->i_mutex_key#14){....}-{3:3}, at: btrfs_inode_lock+0x2a/0x70
> [ 11.346356] BTRFS info (device nvme1n1): last unmount of filesystem
> c92bd0ac-9334-40e5-8c01-75a45093c706
> [ 11.375284] BTRFS info (device nvme0n1): last unmount of filesystem
> 5c716421-ae86-49ee-b283-13cc4758d395
>
> Byte,
> Johannes
Thanks Johannes, I'll send a patch for this.
Mark
