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: Mon, 16 May 2022 19:57:13 -0700	[thread overview]
Message-ID: <0000000000002b39b905df2c4c30@google.com> (raw)
In-Reply-To: <20220516233918.2046-1-hdanton@sina.com>

Hello,

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

------------[ cut here ]------------
percpu ref (css_release) <= 0 (-4294967295) after switching to atomic
WARNING: CPU: 1 PID: 0 at lib/percpu-refcount.c:196 percpu_ref_switch_to_atomic_rcu+0x46c/0x560 lib/percpu-refcount.c:196
Modules linked in:
CPU: 1 PID: 0 Comm: swapper/1 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:percpu_ref_switch_to_atomic_rcu+0x46c/0x560 lib/percpu-refcount.c:196
Code: 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 c0 00 00 00 49 8b 77 e8 4c 89 e2 48 c7 c7 60 e3 26 8a e8 bc a7 31 05 <0f> 0b e9 34 ff ff ff 48 89 c6 48 c7 c7 80 39 69 8c 48 89 44 24 08
RSP: 0018:ffffc900001e0e20 EFLAGS: 00010286
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: ffff888010e71d80 RSI: ffffffff81601ae8 RDI: fffff5200003c1b6
RBP: ffff88801c8e2380 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffff815fc4be R11: 0000000000000000 R12: ffffffff00000001
R13: dffffc0000000000 R14: 0000607f4607c018 R15: ffff88801c8e23a0
FS:  0000000000000000(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555556503848 CR3: 0000000023275000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <IRQ>
 rcu_do_batch kernel/rcu/tree.c:2535 [inline]
 rcu_core+0x7b1/0x1880 kernel/rcu/tree.c:2786
 __do_softirq+0x29b/0x9c2 kernel/softirq.c:558
 invoke_softirq kernel/softirq.c:432 [inline]
 __irq_exit_rcu+0x123/0x180 kernel/softirq.c:637
 irq_exit_rcu+0x5/0x20 kernel/softirq.c:649
 sysvec_apic_timer_interrupt+0x93/0xc0 arch/x86/kernel/apic/apic.c:1097
 </IRQ>
 <TASK>
 asm_sysvec_apic_timer_interrupt+0x12/0x20 arch/x86/include/asm/idtentry.h:645
RIP: 0010:native_save_fl arch/x86/include/asm/irqflags.h:29 [inline]
RIP: 0010:arch_local_save_flags arch/x86/include/asm/irqflags.h:70 [inline]
RIP: 0010:arch_irqs_disabled arch/x86/include/asm/irqflags.h:130 [inline]
RIP: 0010:acpi_safe_halt drivers/acpi/processor_idle.c:111 [inline]
RIP: 0010:acpi_idle_do_entry+0x1c6/0x250 drivers/acpi/processor_idle.c:551
Code: 89 de e8 1d 00 09 f8 84 db 75 ac e8 34 fc 08 f8 e8 9f 44 0f f8 eb 0c e8 28 fc 08 f8 0f 00 2d c1 93 c2 00 e8 1c fc 08 f8 fb f4 <9c> 5b 81 e3 00 02 00 00 fa 31 ff 48 89 de e8 97 fe 08 f8 48 85 db
RSP: 0018:ffffc90000177d20 EFLAGS: 00000293
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: ffff888010e71d80 RSI: ffffffff897044c4 RDI: 0000000000000000
RBP: ffff88801640a864 R08: 0000000000000001 R09: 0000000000000001
R10: ffffffff817f8988 R11: 0000000000000000 R12: 0000000000000001
R13: ffff88801640a800 R14: ffff88801640a864 R15: ffff888147cb0004
 acpi_idle_enter+0x361/0x500 drivers/acpi/processor_idle.c:686
 cpuidle_enter_state+0x1b1/0xc80 drivers/cpuidle/cpuidle.c:237
 cpuidle_enter+0x4a/0xa0 drivers/cpuidle/cpuidle.c:351
 call_cpuidle kernel/sched/idle.c:155 [inline]
 cpuidle_idle_call kernel/sched/idle.c:236 [inline]
 do_idle+0x3e8/0x590 kernel/sched/idle.c:303
 cpu_startup_entry+0x14/0x20 kernel/sched/idle.c:400
 start_secondary+0x224/0x2c0 arch/x86/kernel/smpboot.c:266
 secondary_startup_64_no_verify+0xc3/0xcb
 </TASK>
----------------
Code disassembly (best guess):
   0:	89 de                	mov    %ebx,%esi
   2:	e8 1d 00 09 f8       	callq  0xf8090024
   7:	84 db                	test   %bl,%bl
   9:	75 ac                	jne    0xffffffb7
   b:	e8 34 fc 08 f8       	callq  0xf808fc44
  10:	e8 9f 44 0f f8       	callq  0xf80f44b4
  15:	eb 0c                	jmp    0x23
  17:	e8 28 fc 08 f8       	callq  0xf808fc44
  1c:	0f 00 2d c1 93 c2 00 	verw   0xc293c1(%rip)        # 0xc293e4
  23:	e8 1c fc 08 f8       	callq  0xf808fc44
  28:	fb                   	sti
  29:	f4                   	hlt
* 2a:	9c                   	pushfq <-- trapping instruction
  2b:	5b                   	pop    %rbx
  2c:	81 e3 00 02 00 00    	and    $0x200,%ebx
  32:	fa                   	cli
  33:	31 ff                	xor    %edi,%edi
  35:	48 89 de             	mov    %rbx,%rsi
  38:	e8 97 fe 08 f8       	callq  0xf808fed4
  3d:	48 85 db             	test   %rbx,%rbx


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=110e4759f00000
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=1545e62df00000


       reply	other threads:[~2022-05-17  2:57 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220516233918.2046-1-hdanton@sina.com>
2022-05-17  2:57 ` 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] <20220517111247.2103-1-hdanton@sina.com>
2022-05-17 11:35 ` 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=0000000000002b39b905df2c4c30@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.