From: syzbot <syzbot+c319bb5b1014113a92cf@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, syzkaller@googlegroups.com
Subject: Re: [syzbot] [reiserfs?] possible deadlock in reiserfs_dirty_inode
Date: Thu, 13 Jul 2023 07:01:31 -0700 [thread overview]
Message-ID: <000000000000f2f8c506005ec4e1@google.com> (raw)
In-Reply-To: <20230713133230.398-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+c319bb5b1014113a92cf@syzkaller.appspotmail.com
Tested on:
commit: e40939bb Merge branch 'for-next/core' into for-kernelci
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=127d29a6a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=c4a2640e4213bc2f
dashboard link: https://syzkaller.appspot.com/bug?extid=c319bb5b1014113a92cf
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=14dc6ed8a80000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2023-07-13 14:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230713133230.398-1-hdanton@sina.com>
2023-07-13 14:01 ` syzbot [this message]
2022-11-28 10:04 [syzbot] possible deadlock in reiserfs_dirty_inode syzbot
2023-07-13 2:00 ` [syzbot] [reiserfs?] " syzbot
2023-11-06 8:34 ` syzbot
2023-11-06 22:53 ` Paul Moore
2023-11-07 11:03 ` Roberto Sassu
2023-11-07 22:26 ` Paul Moore
2023-11-08 8:00 ` Roberto Sassu
2024-03-09 9:59 ` syzbot
2024-03-10 0:54 ` Tetsuo Handa
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=000000000000f2f8c506005ec4e1@google.com \
--to=syzbot+c319bb5b1014113a92cf@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=syzkaller@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.