From: Johan Hovold <johan@kernel.org>
To: Farhad Alemi <farhad.alemi@berkeley.edu>
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [BUG] general protection fault in upd78f0730_tiocmset
Date: Wed, 16 Sep 2026 15:47:19 +0200 [thread overview]
Message-ID: <aqqd55r5Nl00FBFt@hovoldconsulting.com> (raw)
In-Reply-To: <CA+0ovChXjGWuRQuKHHWkSiLbdt-WEWv=M0mGOB2eKcJjFiEY=A@mail.gmail.com>
On Fri, Sep 11, 2026 at 01:16:11PM -0700, Farhad Alemi wrote:
> We are reporting the following crash (reproducer attached):
> Linux version 7.3.0-rc2 50d05c7c76c96b90462f24debacca971d2e86713
> Build Config: UpstreamAppArmorKASAN (KASAN + UBSAN, panic_on_warn=1)
>
> [ 44.256596][ T9490] Oops: general protection fault, probably for
> non-canonical address 0xdffffc00000000ba: 0000 [#1] SMP KASAN NOPTI
> [ 44.258408][ T9490] KASAN: null-ptr-deref in range
> [0x00000000000005d0-0x00000000000005d7]
> [ 44.259206][ T9490] CPU: 0 UID: 0 PID: 9490 Comm: repro Not tainted
> 7.3.0-rc2-00099-g50d05c7c76c9 #1 PREEMPT(full)
> [ 44.260235][ T9490] Hardware name: QEMU Standard PC (Q35 + ICH9,
> 2009), BIOS 1.17.0-debian-1.17.0-1ubuntu1 04/01/2014
> [ 44.261396][ T9490] RIP: 0010:upd78f0730_tiocmset+0x86/0x4b0
> [ 44.270495][ T9490] Call Trace:
> [ 44.270882][ T9490] <TASK>
> [ 44.271160][ T9490] ? __pfx_upd78f0730_tiocmset+0x10/0x10
> [ 44.271694][ T9490] ? __pfx_serial_port_dtr_rts+0x10/0x10
> [ 44.272208][ T9490] tty_port_shutdown+0x165/0x220
> [ 44.272672][ T9490] tty_port_hangup+0xee/0x170
> [ 44.273101][ T9490] ? __pfx_serial_hangup+0x10/0x10
> [ 44.273600][ T9490] __tty_hangup+0x5a7/0x650
> [ 44.274074][ T9490] tty_ioctl+0x757/0xde0
Another symptom of this issue was reported by syzbot a couple of weeks
ago and I posted a fix for the tty layer last week:
https://lore.kernel.org/lkml/20260910125114.640880-1-johan@kernel.org/
Johan
prev parent reply other threads:[~2026-09-16 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 20:16 Farhad Alemi
2026-09-16 13:47 ` Johan Hovold [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=aqqd55r5Nl00FBFt@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=farhad.alemi@berkeley.edu \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®