From: syzbot <syzbot+c041985778e4069e1ce3@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fs?] WARNING: bad unlock balance in seq_read_iter
Date: Fri, 31 Jan 2025 21:50:02 -0800 [thread overview]
Message-ID: <679db60a.050a0220.163cdc.001b.GAE@google.com> (raw)
In-Reply-To: <tencent_C95D9CDDB01966CFA00DC1A5898D84920707@qq.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+c041985778e4069e1ce3@syzkaller.appspotmail.com
Tested-by: syzbot+c041985778e4069e1ce3@syzkaller.appspotmail.com
Tested on:
commit: 60c828cf Merge tag 'for-linus-hexagon-6.14-rc1' of git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17443ddf980000
kernel config: https://syzkaller.appspot.com/x/.config?x=f83a535fbb3de0e8
dashboard link: https://syzkaller.appspot.com/bug?extid=c041985778e4069e1ce3
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=122995f8580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-02-01 5:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 20:47 [syzbot] [fs?] WARNING: bad unlock balance in seq_read_iter syzbot
2025-02-01 1:04 ` Edward Adam Davis
2025-02-01 1:24 ` syzbot
2025-02-01 2:27 ` Edward Adam Davis
2025-02-01 2:48 ` syzbot
2025-02-01 3:43 ` Edward Adam Davis
2025-02-01 4:04 ` syzbot
2025-02-01 5:30 ` Edward Adam Davis
2025-02-01 5:50 ` syzbot [this message]
2025-02-01 5:50 ` [PATCH] tracing: keep the event lock balanced Edward Adam Davis
[not found] <tencent_58E8BAED46CE2479A26D8C2E716D5895940A@qq.com>
2025-02-01 2:03 ` [syzbot] [fs?] WARNING: bad unlock balance in seq_read_iter 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=679db60a.050a0220.163cdc.001b.GAE@google.com \
--to=syzbot+c041985778e4069e1ce3@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