From: syzbot <syzbot+2afd7e71155c7e241560@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] memory leak in hub_event (4)
Date: Sat, 25 Apr 2026 01:41:01 -0700 [thread overview]
Message-ID: <69ec7e1d.a00a0220.1901e8.0009.GAE@google.com> (raw)
In-Reply-To: <20260425075154.61497-1-kartikey406@gmail.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
checking file sound/usb/caiaq/device.c
Hunk #1 succeeded at 423 (offset 12 lines).
Hunk #2 FAILED at 501.
1 out of 2 hunks FAILED
Tested on:
commit: 27d128c1 Merge tag 'trace-ring-buffer-v7.1-3' of git:/..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=ac5083db84233db3
dashboard link: https://syzkaller.appspot.com/bug?extid=2afd7e71155c7e241560
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=118fe82a580000
next parent reply other threads:[~2026-04-25 8:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260425075154.61497-1-kartikey406@gmail.com>
2026-04-25 8:41 ` syzbot [this message]
[not found] <20260425144309.67569-1-kartikey406@gmail.com>
2026-04-25 15:23 ` [syzbot] [usb?] memory leak in hub_event (4) syzbot
[not found] <20260425125451.64534-1-kartikey406@gmail.com>
2026-04-25 14:09 ` syzbot
[not found] <20260425093612.30657-1-souradiptodas6@gmail.com>
2026-04-25 10:11 ` syzbot
[not found] <CAKVbAB1UYCWwpZvmV05TuA_NU16YY6fEr5t0HUjuixVq_f5b+w@mail.gmail.com>
2026-04-25 9:51 ` syzbot
[not found] <20260425063629.59918-1-kartikey406@gmail.com>
2026-04-25 7:13 ` syzbot
2026-04-25 2:12 syzbot
2026-04-27 11:40 ` Oliver Neukum
2026-04-27 12:37 ` syzbot
2026-04-27 14:19 ` Alan Stern
2026-04-28 11:33 ` Oliver Neukum
2026-04-28 15:12 ` Alan Stern
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=69ec7e1d.a00a0220.1901e8.0009.GAE@google.com \
--to=syzbot+2afd7e71155c7e241560@syzkaller.appspotmail.com \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.