From: syzbot <syzbot+df3f3ef31f60781fa911@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] BUG: corrupted list in ptp_open
Date: Sat, 04 Nov 2023 18:35:03 -0700 [thread overview]
Message-ID: <0000000000001eae8506095dbfd4@google.com> (raw)
In-Reply-To: <tencent_C46D83B2044E376BB76286CF937A63682905@qq.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
drivers/ptp/ptp_clock.c:250:23: error: no member named 'tsevq_lock' in 'struct ptp_clock'; did you mean 'tsevqs_lock'?
drivers/ptp/ptp_chardev.c:123:26: error: no member named 'tsevq_lock' in 'struct ptp_clock'; did you mean 'tsevqs_lock'?
drivers/ptp/ptp_chardev.c:126:31: error: no member named 'tsevq_lock' in 'struct ptp_clock'; did you mean 'tsevqs_lock'?
drivers/ptp/ptp_chardev.c:150:27: error: no member named 'tsevq_lock' in 'struct ptp_clock'; did you mean 'tsevqs_lock'?
drivers/ptp/ptp_chardev.c:153:32: error: no member named 'tsevq_lock' in 'struct ptp_clock'; did you mean 'tsevqs_lock'?
Tested on:
commit: 2dac7569 Add linux-next specific files for 20231018
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
kernel config: https://syzkaller.appspot.com/x/.config?x=d855e3560c4c99c4
dashboard link: https://syzkaller.appspot.com/bug?extid=df3f3ef31f60781fa911
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=15743708e80000
next parent reply other threads:[~2023-11-05 1:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_C46D83B2044E376BB76286CF937A63682905@qq.com>
2023-11-05 1:35 ` syzbot [this message]
[not found] <tencent_77D0E91EEE8ECDB47BF26C5C2FFD6E68960A@qq.com>
2023-11-06 14:40 ` [syzbot] [net?] BUG: corrupted list in ptp_open syzbot
[not found] <tencent_E146F1D2D4464049842EEEEEE24C8EA7C306@qq.com>
2023-11-06 13:38 ` syzbot
[not found] <tencent_564ACA75C777AD66F83C0D370896CA360E09@qq.com>
2023-11-06 13:26 ` syzbot
[not found] <tencent_C16C882E596CC49668E85AECB6CD307BC60A@qq.com>
2023-11-05 2:06 ` syzbot
[not found] <tencent_42EB25AE0D8292425D8CDD9119714FA30D07@qq.com>
2023-11-04 3:13 ` syzbot
[not found] <tencent_C32CC16DCC9600E83EEC5ECC707B066C480A@qq.com>
2023-11-03 11:56 ` syzbot
[not found] <20231028113238.1092-1-hdanton@sina.com>
2023-10-28 11:57 ` syzbot
[not found] <20231028071018.1016-1-hdanton@sina.com>
2023-10-28 8:08 ` syzbot
[not found] <20231028011908.956-1-hdanton@sina.com>
2023-10-28 2:55 ` syzbot
2023-10-26 14:20 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=0000000000001eae8506095dbfd4@google.com \
--to=syzbot+df3f3ef31f60781fa911@syzkaller.appspotmail.com \
--cc=eadavis@qq.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox