From: Oliver Neukum <oneukum@suse.com>
To: sanan.hasanou@gmail.com, gregkh@linuxfoundation.org,
kees@kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: syzkaller@googlegroups.com, contact@pgazz.com, willy@haproxy.com,
ksenija.stanojevic@gmail.com, sudipm.mukherjee@gmail.com
Subject: Re: BUG: sleeping function called from invalid context in submit_async_request
Date: Sat, 27 Jun 2026 10:05:51 +0200 [thread overview]
Message-ID: <806cfa93-3fbe-4655-bdc6-913eacba3229@suse.com> (raw)
In-Reply-To: <6a3eee6a.87857ece.10923b.6588@mx.google.com>
Hi,
On 26.06.26 23:26, sanan.hasanou@gmail.com wrote:
> kzalloc_noprof include/linux/slab.h:1200 [inline]
> submit_async_request+0xd2/0x9c0 drivers/usb/misc/uss720.c:137
> set_1284_register drivers/usb/misc/uss720.c:237 [inline]
> parport_uss720_write_data+0x70/0x130 drivers/usb/misc/uss720.c:337
> lcd_write_cmd_p8+0x94/0x7f0 drivers/auxdisplay/panel.c:752
> hd44780_common_init_display+0x188/0x4f0 drivers/auxdisplay/hd44780_common.c:124
> charlcd_init drivers/auxdisplay/charlcd.c:585 [inline]
> charlcd_register+0x1e6/0x320 drivers/auxdisplay/charlcd.c:652
> panel_attach+0x19f9/0x1f20 drivers/auxdisplay/panel.c:1644
> driver_check+0x51/0x60 drivers/parport/share.c:158
Are you connecting an auxdisplay to a USB parport?
It seems the issue is that
static void lcd_write_cmd_p8(struct hd44780_common *hdc, int cmd)
{
spin_lock_irq(&pprt_lock);
/* present the data to the data port */
w_dtr(pprt, cmd);
assumes that you can write to a parport with a spinlock held.
uss720 assumes that the method implementing that can use GFP_KERNEL.
I am not sure whether this was even ever defined.
Adding relevant people.
Regards
Oliver
prev parent reply other threads:[~2026-06-27 8:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 21:26 sanan.hasanou
2026-06-27 8:05 ` Oliver Neukum [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=806cfa93-3fbe-4655-bdc6-913eacba3229@suse.com \
--to=oneukum@suse.com \
--cc=contact@pgazz.com \
--cc=gregkh@linuxfoundation.org \
--cc=kees@kernel.org \
--cc=ksenija.stanojevic@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sanan.hasanou@gmail.com \
--cc=sudipm.mukherjee@gmail.com \
--cc=syzkaller@googlegroups.com \
--cc=willy@haproxy.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 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®