From: syzbot <syzbot+0192952caa411a3be209@syzkaller.appspotmail.com>
To: contact@arnaud-lcm.com, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, mchehab@kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [media?] BUG: corrupted list in az6007_i2c_xfer
Date: Mon, 21 Apr 2025 06:44:02 -0700 [thread overview]
Message-ID: <68064ba2.050a0220.4e547.000f.GAE@google.com> (raw)
In-Reply-To: <20250421134021.155569-1-contact@arnaud-lcm.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
checking file drivers/media/usb/dvb-usb-v2/az6007.c
patch: **** malformed patch at line 15: }
Tested on:
commit: 9d7a0577 gcc-15: disable '-Wunterminated-string-initia..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=7a7c679f880028f0
dashboard link: https://syzkaller.appspot.com/bug?extid=0192952caa411a3be209
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=16719ccc580000
next prev parent reply other threads:[~2025-04-21 13:44 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 1:41 [syzbot] [media?] BUG: corrupted list in az6007_i2c_xfer syzbot
2025-04-21 13:40 ` syz test Arnaud Lecomte
2025-04-21 13:44 ` syzbot [this message]
2025-04-21 13:43 ` [syzbot] [media?] BUG: corrupted list in az6007_i2c_xfer Edward Adam Davis
2025-04-21 14:25 ` syzbot
2025-04-21 13:46 ` syz test Arnaud Lecomte
2025-04-21 14:58 ` [syzbot] [media?] BUG: corrupted list in az6007_i2c_xfer syzbot
2025-04-21 14:22 ` syz test Arnaud Lecomte
2025-04-21 16:12 ` [syzbot] [media?] BUG: corrupted list in az6007_i2c_xfer syzbot
2025-04-21 14:31 ` [PATCH] media: az6007: Add upper bound check to the data of device state Edward Adam Davis
2025-04-21 15:11 ` Arnaud Lecomte
2025-11-03 10:06 ` Hans Verkuil
2025-09-05 14:25 ` [syzbot] [media?] BUG: corrupted list in az6007_i2c_xfer Jeongjun Park
2025-09-05 15:53 ` syzbot
2025-09-05 16:06 ` Jeongjun Park
2025-09-05 16:48 ` syzbot
2025-09-06 2:58 ` Jeongjun Park
2025-09-06 3:16 ` syzbot
2025-09-06 3:32 ` Jeongjun Park
2025-09-06 4:12 ` syzbot
2025-09-06 4:56 ` Jeongjun Park
2025-09-06 5:54 ` syzbot
2025-09-06 10:04 ` Jeongjun Park
2025-09-06 10:24 ` syzbot
2025-09-06 10:56 ` Jeongjun Park
2025-09-06 12:28 ` syzbot
2025-09-06 15:24 ` Jeongjun Park
2025-09-06 16:09 ` syzbot
2025-09-06 16:40 ` Jeongjun Park
2025-09-06 17:21 ` syzbot
2025-09-07 8:26 ` Jeongjun Park
2025-09-07 9:56 ` syzbot
2025-09-07 10:05 ` Jeongjun Park
2025-09-07 10:30 ` 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=68064ba2.050a0220.4e547.000f.GAE@google.com \
--to=syzbot+0192952caa411a3be209@syzkaller.appspotmail.com \
--cc=contact@arnaud-lcm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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.