From: syzbot <syzbot+062317ea1d0a6d5e29e7@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [reiserfs?] possible deadlock in super_lock
Date: Tue, 10 Oct 2023 04:49:33 -0700 [thread overview]
Message-ID: <000000000000e45bec06075b4cc8@google.com> (raw)
In-Reply-To: <20231010111343.2257-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+062317ea1d0a6d5e29e7@syzkaller.appspotmail.com
Tested on:
commit: 94f6f055 Linux 6.6-rc5
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=159efc7e680000
kernel config: https://syzkaller.appspot.com/x/.config?x=1b8c825e0d5f3f72
dashboard link: https://syzkaller.appspot.com/bug?extid=062317ea1d0a6d5e29e7
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=15784cde680000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2023-10-10 11:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231010111343.2257-1-hdanton@sina.com>
2023-10-10 11:49 ` syzbot [this message]
[not found] <20231009112906.2143-1-hdanton@sina.com>
2023-10-09 14:01 ` [syzbot] [reiserfs?] possible deadlock in super_lock syzbot
[not found] <20230923040320.1384-1-hdanton@sina.com>
2023-09-23 4:26 ` syzbot
[not found] <20230923024635.1249-1-hdanton@sina.com>
2023-09-23 3:02 ` syzbot
[not found] <20230923010437.297-1-hdanton@sina.com>
2023-09-23 1:14 ` syzbot
[not found] <20230922124125.240-1-hdanton@sina.com>
2023-09-22 13:11 ` syzbot
[not found] <20230921111321.181-1-hdanton@sina.com>
2023-09-21 11:33 ` syzbot
2023-09-03 22:30 [f2fs-dev] [syzbot] [f2fs?] " syzbot
2023-09-20 9:13 ` [syzbot] [reiserfs?] " syzbot
2023-10-08 15:14 ` syzbot
2023-10-09 2:05 ` syzbot
2023-10-09 12:37 ` Christian Brauner
2023-10-09 14:19 ` syzbot
2023-12-24 16:40 ` syzbot
2023-12-28 10:50 ` Christian Brauner
2024-01-02 12:14 ` Jan Kara
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=000000000000e45bec06075b4cc8@google.com \
--to=syzbot+062317ea1d0a6d5e29e7@syzkaller.appspotmail.com \
--cc=hdanton@sina.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 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.