From: Al Viro <viro@zeniv.linux.org.uk>
To: syzbot <syzbot+5b1e53987f858500ec00@syzkaller.appspotmail.com>
Cc: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in mntput_no_expire (3)
Date: Tue, 17 May 2022 22:58:15 +0000 [thread overview]
Message-ID: <YoQohxAFD3EPujRC@zeniv-ca.linux.org.uk> (raw)
In-Reply-To: <000000000000be329205df3cf252@google.com>
On Tue, May 17, 2022 at 03:49:07PM -0700, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch but the reproducer is still triggering an issue:
> WARNING in mntput_no_expire
Obvious question: which filesystem it is?
> entry_SYSCALL_64_after_hwframe+0x44/0xae
> RIP: 0033:0x7f3b7a03bd2b
> Code: 0f 05 48 3d 00 f0 ff ff 77 45 c3 0f 1f 40 00 48 83 ec 18 89 7c 24 0c e8 63 fc ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 89 44 24 0c e8 a1 fc ff ff 8b 44
> RSP: 002b:00007ffe9eb268b0 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
> RAX: 0000000000000000 RBX: 0000000000000004 RCX: 00007f3b7a03bd2b
> RDX: 0000001b2ff20000 RSI: 0000000000000000 RDI: 0000000000000003
> RBP: 00007f3b7a19d960 R08: 0000000000000000 R09: 00007ffe9ebbf080
> R10: 00007ffe9ebbf090 R11: 0000000000000293 R12: 00000000000181f5
> R13: 00007ffe9eb269b0 R14: 00007ffe9eb269d0 R15: 0000000000000032
> </TASK>
>
>
> Tested on:
>
> commit: feb9c5e1 Merge tag 'for_linus' of git://git.kernel.org..
> git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
> console output: https://syzkaller.appspot.com/x/log.txt?x=15ee4759f00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=79caa0035f59d385
> dashboard link: https://syzkaller.appspot.com/bug?extid=5b1e53987f858500ec00
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> patch: https://syzkaller.appspot.com/x/patch.diff?x=1108ae3af00000
>
next prev parent reply other threads:[~2022-05-17 22:58 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220517223806.2299-1-hdanton@sina.com>
2022-05-17 22:49 ` [syzbot] WARNING in mntput_no_expire (3) syzbot
2022-05-17 22:58 ` Al Viro [this message]
2022-05-18 0:59 ` Al Viro
2022-05-18 1:10 ` Al Viro
2022-05-18 1:58 ` Al Viro
2022-05-18 4:38 ` Al Viro
2022-05-18 4:57 ` Al Viro
2022-05-18 5:37 ` Al Viro
2022-05-18 6:25 ` Al Viro
2022-05-18 6:45 ` syzbot
[not found] <20220518104052.2373-1-hdanton@sina.com>
2022-05-18 11:00 ` syzbot
[not found] <20220517111247.2103-1-hdanton@sina.com>
2022-05-17 11:35 ` syzbot
[not found] <20220516233918.2046-1-hdanton@sina.com>
2022-05-17 2:57 ` syzbot
[not found] <20220516122225.1986-1-hdanton@sina.com>
2022-05-16 12:33 ` syzbot
[not found] <20220515133111.1864-1-hdanton@sina.com>
2022-05-15 13:42 ` syzbot
[not found] <20220515094719.1786-1-hdanton@sina.com>
2022-05-15 9:59 ` syzbot
[not found] <20220515050556.1646-1-hdanton@sina.com>
2022-05-15 7:52 ` syzbot
[not found] <20220515012731.1529-1-hdanton@sina.com>
2022-05-15 7:23 ` syzbot
[not found] <20220514233453.1426-1-hdanton@sina.com>
2022-05-15 0:22 ` syzbot
[not found] <20220514132858.1322-1-hdanton@sina.com>
2022-05-14 13:40 ` syzbot
[not found] <20220514114718.1254-1-hdanton@sina.com>
2022-05-14 11:59 ` syzbot
[not found] <20220514084129.1104-1-hdanton@sina.com>
2022-05-14 9:20 ` syzbot
[not found] <20220514073117.965-1-hdanton@sina.com>
2022-05-14 7:42 ` syzbot
[not found] <20220514062752.900-1-hdanton@sina.com>
2022-05-14 6:38 ` syzbot
[not found] <20220514005032.346-1-hdanton@sina.com>
2022-05-14 1:30 ` syzbot
[not found] <20220513144536.279-1-hdanton@sina.com>
2022-05-13 15:14 ` syzbot
[not found] <20220513134852.6446-1-hdanton@sina.com>
2022-05-13 14:12 ` syzbot
[not found] <20220513123641.6379-1-hdanton@sina.com>
2022-05-13 12:48 ` syzbot
[not found] <20220512133426.6300-1-hdanton@sina.com>
2022-05-12 14:05 ` syzbot
[not found] <20220512120234.6088-1-hdanton@sina.com>
2022-05-12 12:20 ` syzbot
[not found] <20220511135117.5993-1-hdanton@sina.com>
2022-05-11 14:03 ` syzbot
2021-11-15 22:27 syzbot
2022-05-11 5:34 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YoQohxAFD3EPujRC@zeniv-ca.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+5b1e53987f858500ec00@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.