netlink: 4 bytes leftover after parsing attributes in process `syz.0.0'.

============================================
WARNING: possible recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
syz.0.0/5322 is trying to acquire lock:
ffff8880540c80a0 (&HFS_I(tree->inode)->extents_lock){+.+.}-{4:4}, at: hfs_extend_file+0xf9/0x1680 fs/hfs/extent.c:397

but task is already holding lock:
ffff8880540c7a20 (&HFS_I(tree->inode)->extents_lock){+.+.}-{4:4}, at: hfs_extend_file+0xf9/0x1680 fs/hfs/extent.c:397

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(&HFS_I(tree->inode)->extents_lock);
  lock(&HFS_I(tree->inode)->extents_lock);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

locks held by syz.0.0/5322: 5, last CPU#0:
 #0: ffff888030f56460 (sb_writers#12){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:527
 #1: ffff8880540c7600 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:1069 [inline]
 #1: ffff8880540c7600 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: __start_dirop fs/namei.c:2947 [inline]
 #1: ffff8880540c7600 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: start_dirop fs/namei.c:2971 [inline]
 #1: ffff8880540c7600 (&type->i_mutex_dir_key#8/1){+.+.}-{4:4}, at: filename_create+0x200/0x370 fs/namei.c:5121
 #2: ffff88803ec620a8 (&tree->tree_lock){+.+.}-{4:4}, at: hfs_find_init+0x18d/0x300 fs/hfs/bfind.c:-1
 #3: ffff8880540c7a20 (&HFS_I(tree->inode)->extents_lock){+.+.}-{4:4}, at: hfs_extend_file+0xf9/0x1680 fs/hfs/extent.c:397
 #4: ffff8880439020a8 (&tree->tree_lock/1){+.+.}-{4:4}, at: hfs_find_init+0x18d/0x300 fs/hfs/bfind.c:-1

stack backtrace:
CPU: 0 UID: 0 PID: 5322 Comm: syz.0.0 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_deadlock_bug+0x27a/0x290 kernel/locking/lockdep.c:3085
 check_deadlock kernel/locking/lockdep.c:3137 [inline]
 validate_chain kernel/locking/lockdep.c:3939 [inline]
 __lock_acquire+0x25db/0x2de0 kernel/locking/lockdep.c:5288
 lock_acquire+0x115/0x350 kernel/locking/lockdep.c:5942
 __mutex_lock_common kernel/locking/mutex.c:646 [inline]
 __mutex_lock+0x19d/0x1550 kernel/locking/mutex.c:821
 hfs_extend_file+0xf9/0x1680 fs/hfs/extent.c:397
 hfs_bmap_reserve+0x108/0x430 fs/hfs/btree.c:399
 __hfs_ext_write_extent+0x1fc/0x470 fs/hfs/extent.c:121
 __hfs_ext_cache_extent+0x6e/0x9b0 fs/hfs/extent.c:174
 hfs_ext_read_extent fs/hfs/extent.c:202 [inline]
 hfs_extend_file+0x3ad/0x1680 fs/hfs/extent.c:401
 hfs_bmap_reserve+0x108/0x430 fs/hfs/btree.c:399
 hfs_cat_create+0x23d/0x870 fs/hfs/catalog.c:104
 hfs_mkdir+0x73/0xe0 fs/hfs/dir.c:226
 vfs_mkdir+0x40c/0x620 fs/namei.c:5439
 filename_mkdirat+0x285/0x510 fs/namei.c:5472
 __do_sys_mkdirat fs/namei.c:5493 [inline]
 __se_sys_mkdirat+0x35/0x150 fs/namei.c:5490
 do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
 do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f242d39d047
Code: 00 66 90 48 89 f2 b9 00 01 00 00 48 89 fe bf 9c ff ff ff e9 db f7 ff ff 66 2e 0f 1f 84 00 00 00 00 00 90 b8 02 01 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f242e2fce18 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007f242e2fcea0 RCX: 00007f242d39d047
RDX: 00000000000001ff RSI: 0000200000008200 RDI: 00000000ffffff9c
RBP: 00002000000081c0 R08: 0000200000008300 R09: 0000000000000000
R10: 00002000000081c0 R11: 0000000000000246 R12: 0000200000008200
R13: 00007f242e2fce60 R14: 0000000000000000 R15: 0000000000000000
 </TASK>