From: Thomas Gleixner <tglx@linutronix.de>
To: syzbot <syzbot+a234c2d63e0c171ca10e@syzkaller.appspotmail.com>,
brauner@kernel.org, gregkh@linuxfoundation.org, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, linux-usb@vger.kernel.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [serial?] BUG: soft lockup in debug_check_no_obj_freed
Date: Sun, 27 Oct 2024 10:33:01 +0100 [thread overview]
Message-ID: <87iktd51rm.ffs@tglx> (raw)
In-Reply-To: <6713d23a.050a0220.1e4b4d.0029.GAE@google.com>
On Sat, Oct 19 2024 at 08:37, syzbot wrote:
That's not a soft lockup in debug_check_no_obj_freed().
What actually happens is:
> serial_in drivers/tty/serial/8250/8250.h:137 [inline]
> serial_lsr_in drivers/tty/serial/8250/8250.h:159 [inline]
> wait_for_lsr+0xda/0x180 drivers/tty/serial/8250/8250_port.c:2068
> serial8250_console_fifo_write drivers/tty/serial/8250/8250_port.c:3315 [inline]
> serial8250_console_write+0xf5a/0x17c0 drivers/tty/serial/8250/8250_port.c:3393
> console_emit_next_record kernel/printk/printk.c:3092 [inline]
> console_flush_all+0x800/0xc60 kernel/printk/printk.c:3180
> __console_flush_and_unlock kernel/printk/printk.c:3239 [inline]
> console_unlock+0xd9/0x210 kernel/printk/printk.c:3279
> vprintk_emit+0x424/0x6f0 kernel/printk/printk.c:2407
> vprintk+0x7f/0xa0 kernel/printk/printk_safe.c:68
> _printk+0xc8/0x100 kernel/printk/printk.c:2432
> printk_stack_address arch/x86/kernel/dumpstack.c:72 [inline]
> show_trace_log_lvl+0x1b7/0x3d0 arch/x86/kernel/dumpstack.c:285
> sched_show_task kernel/sched/core.c:7589 [inline]
> sched_show_task+0x3f0/0x5f0 kernel/sched/core.c:7564
> show_state_filter+0xee/0x320 kernel/sched/core.c:7634
> k_spec drivers/tty/vt/keyboard.c:667 [inline]
> k_spec+0xed/0x150 drivers/tty/vt/keyboard.c:656
HID injects a sysrq-t and the task dump takes ages, which is what stalls
RCU.
There is not much what can be done about this as the dump is initiated
from soft interrupt context at interrupt return.
Thanks,
tglx
prev parent reply other threads:[~2024-10-27 9:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-19 15:37 [syzbot] [serial?] BUG: soft lockup in debug_check_no_obj_freed syzbot
2024-10-27 9:33 ` Thomas Gleixner [this message]
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=87iktd51rm.ffs@tglx \
--to=tglx@linutronix.de \
--cc=brauner@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=syzbot+a234c2d63e0c171ca10e@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).