From: syzbot <syzbot+fe63e4d633540f230624@syzkaller.appspotmail.com>
To: syedtayyabfarooq08@gmail.com
Cc: syedtayyabfarooq08@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: test patch
Date: Tue, 08 Sep 2026 23:36:35 -0700 [thread overview]
Message-ID: <6aa0fe73.f81106d8.285f0a.000b.GAE@google.com> (raw)
In-Reply-To: <20260909063623.6999-1-syedtayyabfarooq08@gmail.com>
> #syz test
"" does not look like a valid git branch or commit.
>
> diff --git a/drivers/usb/gadget/function/u_serial.c b/drivers/usb/gadget/function/u_serial.c
> index cdd1dfc666c4..4435cc42d1c0 100644
> --- a/drivers/usb/gadget/function/u_serial.c
> +++ b/drivers/usb/gadget/function/u_serial.c
> @@ -603,6 +603,41 @@ static int gserial_wakeup_host(struct gserial *gser)
>
> /* TTY Driver */
>
> +static int gs_install(struct tty_driver *driver, struct tty_struct *tty)
> +{
> + struct gs_port *port;
> + struct tty_port *tport;
> + int ret;
> +
> + mutex_lock(&ports[tty->index].lock);
> + port = ports[tty->index].port;
> + if (!port) {
> + mutex_unlock(&ports[tty->index].lock);
> + return -ENODEV;
> + }
> +
> + tport = tty_port_get(&port->port);
> + mutex_unlock(&ports[tty->index].lock);
> +
> + if (!tport)
> + return -ENODEV;
> +
> + ret = tty_port_install(tport, driver, tty);
> + if (ret) {
> + tty_port_put(tport);
> + return ret;
> + }
> +
> + tty->driver_data = port;
> +
> + return 0;
> +}
> +
> +static void gs_cleanup(struct tty_struct *tty)
> +{
> + tty_port_put(tty->port);
> +}
> +
> /*
> * gs_open sets up the link between a gs_port and its associated TTY.
> * That link is broken *only* by TTY close(), and all driver methods
> @@ -911,6 +946,8 @@ static int gs_get_icount(struct tty_struct *tty,
> static const struct tty_operations gs_tty_ops = {
> .open = gs_open,
> .close = gs_close,
> + .install = gs_install,
> + .cleanup = gs_cleanup,
> .write = gs_write,
> .put_char = gs_put_char,
> .flush_chars = gs_flush_chars,
> @@ -1203,6 +1240,18 @@ static void gs_console_exit(struct gs_port *port)
>
> #endif
>
> +static void gs_port_destruct(struct tty_port *tport)
> +{
> + struct gs_port *port = container_of(tport, struct gs_port, port);
> +
> + kfree(port);
> +}
> +
> +static const struct tty_port_operations gs_port_ops = {
> + .destruct = gs_port_destruct,
> +};
> +
> +
> static int
> gs_port_alloc(unsigned port_num, struct usb_cdc_line_coding *coding)
> {
> @@ -1222,6 +1271,7 @@ gs_port_alloc(unsigned port_num, struct usb_cdc_line_coding *coding)
> }
>
> tty_port_init(&port->port);
> + port->port.ops = &gs_port_ops;
> spin_lock_init(&port->port_lock);
> init_waitqueue_head(&port->drain_wait);
> init_waitqueue_head(&port->close_wait);
> @@ -1258,8 +1308,7 @@ static void gserial_free_port(struct gs_port *port)
> /* wait for old opens to finish */
> wait_event(port->close_wait, gs_closed(port));
> WARN_ON(port->port_usb != NULL);
> - tty_port_destroy(&port->port);
> - kfree(port);
> + tty_port_put(&port->port);
> }
>
> void gserial_free_line(unsigned char port_num)
next parent reply other threads:[~2026-09-09 6:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260909063623.6999-1-syedtayyabfarooq08@gmail.com>
2026-09-09 6:36 ` syzbot [this message]
[not found] <20260910114712.20455-1-tahasami8@gmail.com>
2026-09-10 11:47 ` 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=6aa0fe73.f81106d8.285f0a.000b.GAE@google.com \
--to=syzbot+fe63e4d633540f230624@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syedtayyabfarooq08@gmail.com \
--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 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®