From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: linux-usb@vger.kernel.org
Cc: syzbot <syzbot+de553c19cb054f174a35@syzkaller.appspotmail.com>,
gregkh@linuxfoundation.org,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Felipe Balbi <felipe.balbi@linux.intel.com>
Subject: [PATCH REPOST] usb: udc: Make tracing aware that usb_ep_alloc_request() can return NULL
Date: Mon, 12 Oct 2026 11:49:11 +0200 [thread overview]
Message-ID: <20261012094911.wHPc_9lJ@linutronix.de> (raw)
The alloc_request callback of the EP can return NULL if it was not able
to allocate a request. This NULL pointer will then be dereferenced by
tracing in order to show details about it.
Let tracing check the req pointer and if NULL just write 0.
Fixes: 5e42d710a108c ("usb: gadget: add tracepoints to the gadget API")
Reported-by: syzbot+de553c19cb054f174a35@syzkaller.appspotmail.com
Closes: https://lore.kernel.org/all/6aab0160.e91c2013.3bdb06.0005.GAE@google.com/
Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
---
drivers/usb/gadget/udc/trace.h | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/usb/gadget/udc/trace.h b/drivers/usb/gadget/udc/trace.h
index fa3e6ddf0a128..05533eb1bae0c 100644
--- a/drivers/usb/gadget/udc/trace.h
+++ b/drivers/usb/gadget/udc/trace.h
@@ -239,15 +239,15 @@ DECLARE_EVENT_CLASS(udc_log_req,
),
TP_fast_assign(
__assign_str(name);
- __entry->length = req->length;
- __entry->actual = req->actual;
- __entry->num_sgs = req->num_sgs;
- __entry->num_mapped_sgs = req->num_mapped_sgs;
- __entry->stream_id = req->stream_id;
- __entry->no_interrupt = req->no_interrupt;
- __entry->zero = req->zero;
- __entry->short_not_ok = req->short_not_ok;
- __entry->status = req->status;
+ __entry->length = req ? req->length : 0;
+ __entry->actual = req ? req->actual : 0;
+ __entry->num_sgs = req ? req->num_sgs : 0;
+ __entry->num_mapped_sgs = req ? req->num_mapped_sgs : 0;
+ __entry->stream_id = req ? req->stream_id : 0;
+ __entry->no_interrupt = req ? req->no_interrupt : 0;
+ __entry->zero = req ? req->zero : 0;
+ __entry->short_not_ok = req ? req->short_not_ok : 0;
+ __entry->status = req ? req->status : 0;
__entry->ret = ret;
__entry->req = req;
),
--
2.55.0
next reply other threads:[~2026-10-12 9:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 9:49 Sebastian Andrzej Siewior [this message]
2026-10-12 10:00 ` [PATCH REPOST] usb: udc: Make tracing aware that usb_ep_alloc_request() can return NULL sashiko-bot
2026-10-12 11:26 ` Greg KH
2026-10-12 16:29 ` Sebastian Andrzej Siewior
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=20261012094911.wHPc_9lJ@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=syzbot+de553c19cb054f174a35@syzkaller.appspotmail.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