All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+5b1e53987f858500ec00@syzkaller.appspotmail.com>
To: 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 04:35:09 -0700	[thread overview]
Message-ID: <0000000000007cf04605df3388a8@google.com> (raw)
In-Reply-To: <20220517111247.2103-1-hdanton@sina.com>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in mntput_no_expire

------------[ cut here ]------------
WARNING: CPU: 0 PID: 4042 at fs/namespace.c:1239 mntput_no_expire+0xb02/0xfe0 fs/namespace.c:1239
Modules linked in:
CPU: 0 PID: 4042 Comm: syz-executor.2 Not tainted 5.18.0-rc6-syzkaller-00009-gfeb9c5e19e91-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:mntput_no_expire+0xb02/0xfe0 fs/namespace.c:1239
Code: 00 48 c7 c7 c0 16 db 89 c6 05 33 c9 c8 0b 01 e8 c9 55 4d 07 e9 57 ff ff ff e8 2a bd 9d ff 0f 0b e9 df f9 ff ff e8 1e bd 9d ff <0f> 0b e9 d3 f9 ff ff e8 12 bd 9d ff e8 4d b7 88 ff 31 ff 89 c3 89
RSP: 0018:ffffc9000313fcf0 EFLAGS: 00010293

RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: ffff88801ba15880 RSI: ffffffff81db8412 RDI: 0000000000000003
RBP: 0000000000000008 R08: 0000000000000000 R09: ffffffff9006e94f
R10: ffffffff81db7dce R11: 0000000000000001 R12: ffffc9000313fd40
R13: ffff88801f6ea800 R14: 0000000000000002 R15: dffffc0000000000
FS:  000055555676b400(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fff05411c78 CR3: 000000007a034000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 path_umount+0x7d4/0x1260 fs/namespace.c:1819
 ksys_umount fs/namespace.c:1838 [inline]
 __do_sys_umount fs/namespace.c:1843 [inline]
 __se_sys_umount fs/namespace.c:1841 [inline]
 __x64_sys_umount+0x159/0x180 fs/namespace.c:1841
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x7f67c148a557
Code: ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffc7f7ec938 EFLAGS: 00000246
 ORIG_RAX: 00000000000000a6
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f67c148a557
RDX: 00007ffc7f7eca0a RSI: 000000000000000a RDI: 00007ffc7f7eca00
RBP: 00007ffc7f7eca00 R08: 00000000ffffffff R09: 00007ffc7f7ec7d0
R10: 000055555676c8b3 R11: 0000000000000246 R12: 00007f67c14e21f8
R13: 00007ffc7f7edac0 R14: 000055555676c810 R15: 00007ffc7f7edb00
 </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=10df1295f00000
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=16f621b9f00000


       reply	other threads:[~2022-05-17 11:35 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220517111247.2103-1-hdanton@sina.com>
2022-05-17 11:35 ` syzbot [this message]
     [not found] <20220518104052.2373-1-hdanton@sina.com>
2022-05-18 11:00 ` [syzbot] WARNING in mntput_no_expire (3) syzbot
     [not found] <20220517223806.2299-1-hdanton@sina.com>
2022-05-17 22:49 ` syzbot
2022-05-17 22:58   ` Al Viro
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] <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=0000000000007cf04605df3388a8@google.com \
    --to=syzbot+5b1e53987f858500ec00@syzkaller.appspotmail.com \
    --cc=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --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.