From: syzbot <syzbot+c2ada45c23d98d646118@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com, boqun.feng@gmail.com,
hdanton@sina.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, ntfs3@lists.linux.dev,
penguin-kernel@i-love.sakura.ne.jp,
syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org
Subject: Re: [syzbot] [ntfs3?] possible deadlock in ntfs_set_state (2)
Date: Mon, 26 Feb 2024 03:46:02 -0800 [thread overview]
Message-ID: <00000000000044c2da06124774f7@google.com> (raw)
In-Reply-To: <20240226105506.1398-1-hdanton@sina.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to checkout kernel repo https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git on commit 716f4aaa7b48: failed to run ["git" "fetch" "--force" "--tags" "4d52a57a3858a6eee0d0b25cc3a0c9533f747d8f" "716f4aaa7b48"]: exit status 128
fatal: couldn't find remote ref 716f4aaa7b48
Tested on:
commit: [unknown
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 716f4aaa7b48
kernel config: https://syzkaller.appspot.com/x/.config?x=1d7c92dd8d5c7a1e
dashboard link: https://syzkaller.appspot.com/bug?extid=c2ada45c23d98d646118
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=172e5f4a180000
next prev parent reply other threads:[~2024-02-26 11:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 7:12 [syzbot] [ntfs3?] possible deadlock in ntfs_set_state (2) syzbot
2024-02-13 10:37 ` Edward Adam Davis
2024-02-13 11:10 ` syzbot
2024-02-13 11:41 ` Hillf Danton
2024-02-26 4:23 ` Boqun Feng
2024-02-26 10:55 ` Hillf Danton
2024-02-26 11:46 ` syzbot [this message]
2024-02-26 12:06 ` Hillf Danton
2024-02-26 15:00 ` syzbot
2024-07-17 6:31 ` [syzbot] ntfs3.git syzbot
2024-08-23 8:56 ` [syzbot] possible deadlock in ntfs_set_state (linux-ntfs3.git/master) syzbot
[not found] <6fb088e7-3385-4c06-945f-0a58da0bf138@paragon-software.com>
2024-07-17 7:27 ` [syzbot] [ntfs3?] possible deadlock in ntfs_set_state (2) syzbot
[not found] <e80cfc67-ff1c-484f-bf42-8c9d72408c36@paragon-software.com>
2024-08-23 9:26 ` 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=00000000000044c2da06124774f7@google.com \
--to=syzbot+c2ada45c23d98d646118@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=boqun.feng@gmail.com \
--cc=hdanton@sina.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.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.