From: syzbot <syzbot+b95d0c98f01e7a95da72@syzkaller.appspotmail.com>
To: brgl@bgdev.pl, eadavis@qq.com, linus.walleij@linaro.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [gpio?] general protection fault in gpiolib_seq_stop
Date: Mon, 16 Dec 2024 23:08:03 -0800 [thread overview]
Message-ID: <67612353.050a0220.37aaf.014c.GAE@google.com> (raw)
In-Reply-To: <tencent_A2CD92F8865949AE6ED1AED2CC9327C50606@qq.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 gpiolib_seq_start
RBP: 00007fe66f38b090 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000246 R12: 0000000000000001
R13: 0000000000000000 R14: 00007fe66e775fa0 R15: 00007ffe92372dd8
</TASK>
================================================
WARNING: lock held when returning to user space!
6.12.0-syzkaller-10299-gc1f7eb90d8d5 #0 Not tainted
------------------------------------------------
syz.0.18/6685 is leaving the kernel with locks still held!
1 lock held by syz.0.18/6685:
#0: ffffffff8e96d590 (gpio_devices_srcu){.+.+}-{0:0}, at: srcu_lock_acquire include/linux/srcu.h:158 [inline]
#0: ffffffff8e96d590 (gpio_devices_srcu){.+.+}-{0:0}, at: srcu_read_lock include/linux/srcu.h:249 [inline]
#0: ffffffff8e96d590 (gpio_devices_srcu){.+.+}-{0:0}, at: gpiolib_seq_start+0x13e/0x270 drivers/gpio/gpiolib.c:5039
Tested on:
commit: c1f7eb90 fs/seq_file: Exit the subsequent process when..
git tree: https://github.com/ea1davis/linux gpio/syz
console output: https://syzkaller.appspot.com/x/log.txt?x=12dfb4f8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e8d97faf7b870c89
dashboard link: https://syzkaller.appspot.com/bug?extid=b95d0c98f01e7a95da72
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
next prev parent reply other threads:[~2024-12-17 7:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 5:09 [syzbot] [gpio?] general protection fault in gpiolib_seq_stop syzbot
2024-12-17 6:48 ` Edward Adam Davis
2024-12-17 7:08 ` syzbot [this message]
2024-12-17 7:13 ` Edward Adam Davis
2024-12-17 7:34 ` syzbot
2024-12-17 7:37 ` [PATCH] fs/seq_file: Exit the subsequent process when seq start fails Edward Adam Davis
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=67612353.050a0220.37aaf.014c.GAE@google.com \
--to=syzbot+b95d0c98f01e7a95da72@syzkaller.appspotmail.com \
--cc=brgl@bgdev.pl \
--cc=eadavis@qq.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--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