From: syzbot <syzbot+41a88b825a315aac2254@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [hfs?] possible deadlock in hfs_extend_file (2)
Date: Tue, 02 Jan 2024 04:08:03 -0800 [thread overview]
Message-ID: <000000000000b8cb3f060df5592e@google.com> (raw)
In-Reply-To: <tencent_17CEBA53BB6733599E5D1B6A4BB11B5A2508@qq.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+41a88b825a315aac2254@syzkaller.appspotmail.com
Tested on:
commit: 610a9b8f Linux 6.7-rc8
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=14649d81e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=247b5a935d307ee5
dashboard link: https://syzkaller.appspot.com/bug?extid=41a88b825a315aac2254
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=1031326ee80000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-01-02 12:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 13:42 [syzbot] [hfs?] possible deadlock in hfs_extend_file (2) syzbot
2024-01-02 5:11 ` syzbot
2024-01-02 11:37 ` Edward Adam Davis
2024-01-02 12:08 ` syzbot [this message]
2024-01-02 12:36 ` [PATCH] hfs: fix deadlock in hfs_extend_file Edward Adam Davis
2024-01-03 7:45 ` Matthew Wilcox
2024-01-03 9:03 ` Viacheslav Dubeyko
2024-01-03 0:40 ` [syzbot] [hfs?] possible deadlock in hfs_extend_file (2) syzbot
2024-02-22 4:10 ` syzbot
2024-02-22 10:01 ` Jan Kara
-- strict thread matches above, loose matches on Subject: below --
2024-01-20 14:40 [syzbot] [hfs?] INFO: task hung in hfs_find_init (2) syzbot
2024-01-22 6:43 ` [syzbot] [hfs?] possible deadlock in hfs_extend_file (2) 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=000000000000b8cb3f060df5592e@google.com \
--to=syzbot+41a88b825a315aac2254@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