From: syzbot <syzbot+0a05df8ed151f2ed3a05@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
rafael@kernel.org, syzkaller-bugs@googlegroups.com
Subject: WARNING in put_i2c_dev
Date: Mon, 09 Nov 2020 23:45:19 -0800 [thread overview]
Message-ID: <000000000000484e4b05b3bbdcf4@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 521b619a Merge tag 'linux-kselftest-kunit-fixes-5.10-rc3' ..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10760a34500000
kernel config: https://syzkaller.appspot.com/x/.config?x=61033507391c77ff
dashboard link: https://syzkaller.appspot.com/bug?extid=0a05df8ed151f2ed3a05
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1672e7a8500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15f6b4b2500000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+0a05df8ed151f2ed3a05@syzkaller.appspotmail.com
pvrusb2: Attached sub-driver cx25840
pvrusb2: ***WARNING*** pvrusb2 device hardware appears to be jammed and I can't clear it.
pvrusb2: You might need to power cycle the pvrusb2 device in order to recover.
------------[ cut here ]------------
sysfs group 'power' not found for kobject 'i2c-1'
WARNING: CPU: 1 PID: 4041 at fs/sysfs/group.c:279 sysfs_remove_group+0x126/0x170 fs/sysfs/group.c:279
Modules linked in:
CPU: 1 PID: 4041 Comm: pvrusb2-context Not tainted 5.10.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:sysfs_remove_group+0x126/0x170 fs/sysfs/group.c:279
Code: 48 89 d9 49 8b 14 24 48 b8 00 00 00 00 00 fc ff df 48 c1 e9 03 80 3c 01 00 75 37 48 8b 33 48 c7 c7 60 72 5b 89 e8 81 52 c4 06 <0f> 0b eb 98 e8 11 7e ca ff e9 01 ff ff ff 48 89 df e8 04 7e ca ff
RSP: 0018:ffffc9000367fa38 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffffffff89b53740 RCX: 0000000000000000
RDX: ffff88801d0d8000 RSI: ffffffff8158d055 RDI: fffff520006cff39
RBP: 0000000000000000 R08: 0000000000000001 R09: ffff8880b9f309e7
R10: 0000000000000000 R11: 0000000000000000 R12: ffff888143e19018
R13: ffffffff89b53ce0 R14: ffff888143e1e000 R15: ffffffff8c2c7d20
FS: 0000000000000000(0000) GS:ffff8880b9f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fc516e9a020 CR3: 0000000020556000 CR4: 00000000001506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
dpm_sysfs_remove+0x97/0xb0 drivers/base/power/sysfs.c:837
device_del+0x20c/0xec0 drivers/base/core.c:3092
cdev_device_del+0x19/0x100 fs/char_dev.c:573
put_i2c_dev+0x160/0x1b0 drivers/i2c/i2c-dev.c:93
i2cdev_detach_adapter.part.0+0x10f/0x1a0 drivers/i2c/i2c-dev.c:689
i2cdev_detach_adapter drivers/i2c/i2c-dev.c:647 [inline]
i2cdev_notifier_call+0xad/0xc0 drivers/i2c/i2c-dev.c:704
notifier_call_chain+0xb5/0x200 kernel/notifier.c:83
blocking_notifier_call_chain kernel/notifier.c:337 [inline]
blocking_notifier_call_chain+0x67/0x90 kernel/notifier.c:325
device_del+0x1ff/0xec0 drivers/base/core.c:3089
device_unregister+0x22/0xc0 drivers/base/core.c:3148
i2c_del_adapter+0x4d6/0x680 drivers/i2c/i2c-core-base.c:1690
pvr2_i2c_core_done+0x69/0xc0 drivers/media/usb/pvrusb2/pvrusb2-i2c-core.c:652
pvr2_hdw_destroy+0x179/0x3b0 drivers/media/usb/pvrusb2/pvrusb2-hdw.c:2679
pvr2_context_destroy+0x84/0x230 drivers/media/usb/pvrusb2/pvrusb2-context.c:70
pvr2_context_check drivers/media/usb/pvrusb2/pvrusb2-context.c:137 [inline]
pvr2_context_thread_func+0x641/0x850 drivers/media/usb/pvrusb2/pvrusb2-context.c:158
kthread+0x3af/0x4a0 kernel/kthread.c:292
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
next reply other threads:[~2020-11-10 7:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 7:45 syzbot [this message]
2021-01-14 3:34 ` WARNING in put_i2c_dev 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=000000000000484e4b05b3bbdcf4@google.com \
--to=syzbot+0a05df8ed151f2ed3a05@syzkaller.appspotmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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.