From: syzbot <syzbot+5cf270e2069645b6bd2c@syzkaller.appspotmail.com>
To: djahchankoike@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] general protection fault in phy_start_cable_test_tdr
Date: Tue, 27 Aug 2024 19:28:02 -0700 [thread overview]
Message-ID: <000000000000801bab0620b51be7@google.com> (raw)
In-Reply-To: <20240828013519.7810-1-djahchankoike@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING: lock held when returning to user space in ethnl_act_cable_test_tdr
================================================
WARNING: lock held when returning to user space!
6.11.0-rc4-syzkaller-00681-ge5899b60f52a-dirty #0 Not tainted
------------------------------------------------
syz.0.15/6086 is leaving the kernel with locks still held!
1 lock held by syz.0.15/6086:
#0: ffffffff8fc84c08 (rtnl_mutex){+.+.}-{3:3}, at: ethnl_act_cable_test_tdr+0x3d2/0x10c0 net/ethtool/cabletest.c:341
Tested on:
commit: e5899b60 Merge branch '100GbE' of git://git.kernel.org..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=16a5267b980000
kernel config: https://syzkaller.appspot.com/x/.config?x=df2f0ed7e30a639d
dashboard link: https://syzkaller.appspot.com/bug?extid=5cf270e2069645b6bd2c
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=17c1c57b980000
next parent reply other threads:[~2024-08-28 2:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240828013519.7810-1-djahchankoike@gmail.com>
2024-08-28 2:28 ` syzbot [this message]
2024-08-28 0:09 [syzbot] [net?] general protection fault in phy_start_cable_test_tdr syzbot
2024-08-28 1:34 ` Edward Adam Davis
2024-08-28 2:09 ` syzbot
2024-08-28 6:23 ` Maxime Chevallier
2024-10-04 2:26 ` 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=000000000000801bab0620b51be7@google.com \
--to=syzbot+5cf270e2069645b6bd2c@syzkaller.appspotmail.com \
--cc=djahchankoike@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox