From: syzbot <syzbot+325b61d3c9a17729454b@syzkaller.appspotmail.com>
To: aha310510@gmail.com, akpm@linux-foundation.org,
brauner@kernel.org, chao@kernel.org, jack@suse.cz,
jlayton@kernel.org, josef@toxicpanda.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk,
willy@infradead.org
Subject: Re: [syzbot] [hfs?] possible deadlock in hfsplus_file_extend
Date: Fri, 27 Sep 2024 20:15:03 -0700 [thread overview]
Message-ID: <66f774b7.050a0220.46d20.002d.GAE@google.com> (raw)
In-Reply-To: <0000000000002dabd805ee5b222e@google.com>
syzbot suspects this issue was fixed by commit:
commit be4edd1642ee205ed7bbf66edc0453b1be1fb8d7
Author: Chao Yu <chao@kernel.org>
Date: Fri Jun 7 14:23:04 2024 +0000
hfsplus: fix to avoid false alarm of circular locking
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16c5f59f980000
start commit: 90d35da658da Linux 6.8-rc7
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=70429b75d4a1a401
dashboard link: https://syzkaller.appspot.com/bug?extid=325b61d3c9a17729454b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=159253ee180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11afd4fe180000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: hfsplus: fix to avoid false alarm of circular locking
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-09-28 3:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 8:07 [syzbot] possible deadlock in hfsplus_file_extend syzbot
2022-12-02 8:18 ` syzbot
2024-04-25 15:39 ` [PATCH] hfsplus: Fix deadlock in hfsplus filesystem Jeongjun Park
2024-04-24 16:12 ` [syzbot] possible deadlock in hfsplus_file_extend Jeongjun Park
2024-04-24 23:38 ` [syzbot] [hfs?] " syzbot
2024-09-28 3:15 ` syzbot [this message]
2024-10-08 6:18 ` Chao Yu
2024-10-09 20:59 ` [syzbot] Re: [syzbot] " syzbot
[not found] <65233b0c-cf11-4ef6-957c-e0434742d6e8@sandeen.net>
2024-10-09 23:23 ` [syzbot] [hfs?] " 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=66f774b7.050a0220.46d20.002d.GAE@google.com \
--to=syzbot+325b61d3c9a17729454b@syzkaller.appspotmail.com \
--cc=aha310510@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=chao@kernel.org \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/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.