From: syzbot <syzbot+8fb64a61fdd96b50f3b8@syzkaller.appspotmail.com>
To: hdanton@sina.com, jack@suse.cz, jeffm@suse.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
paul@paul-moore.com, reiserfs-devel@vger.kernel.org,
roberto.sassu@huawei.com, roberto.sassu@huaweicloud.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [reiserfs?] possible deadlock in open_xa_dir
Date: Thu, 01 Jun 2023 13:38:39 -0700 [thread overview]
Message-ID: <000000000000dbb63805fd176bc6@google.com> (raw)
In-Reply-To: <8a48ede1-3a45-7c3c-39e9-36001ac09283@huaweicloud.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
checking file fs/reiserfs/namei.c
patch: **** unexpected end of file in patch
Tested on:
commit: 929ed21d Merge tag '6.4-rc4-smb3-client-fixes' of git:..
git tree: upstream
dashboard link: https://syzkaller.appspot.com/bug?extid=8fb64a61fdd96b50f3b8
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=10efc079280000
next prev parent reply other threads:[~2023-06-01 20:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-31 6:35 [syzbot] [reiserfs?] possible deadlock in open_xa_dir syzbot
2023-05-05 7:10 ` syzbot
2023-05-05 20:51 ` syzbot
2023-05-05 21:36 ` Paul Moore
2023-05-05 21:36 ` Paul Moore
2023-05-31 9:49 ` Roberto Sassu
2023-05-31 9:49 ` Roberto Sassu
2023-05-31 9:52 ` Roberto Sassu
2023-06-01 21:22 ` Jeff Mahoney
2023-06-02 7:20 ` Roberto Sassu
2023-06-02 7:20 ` Roberto Sassu
2023-06-02 8:56 ` Roberto Sassu
2023-06-02 9:17 ` syzbot
2023-06-02 16:18 ` Roberto Sassu
2023-06-02 16:39 ` syzbot
2023-06-02 16:46 ` Roberto Sassu
2023-06-02 16:46 ` Roberto Sassu
2023-06-01 20:19 ` Roberto Sassu
2023-06-01 20:38 ` syzbot [this message]
2023-06-01 20:30 ` Roberto Sassu
2023-06-01 20:57 ` syzbot
2024-03-09 22:20 ` syzbot
[not found] <20230505075628.4150-1-hdanton@sina.com>
2023-05-05 8:32 ` 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=000000000000dbb63805fd176bc6@google.com \
--to=syzbot+8fb64a61fdd96b50f3b8@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=jack@suse.cz \
--cc=jeffm@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=reiserfs-devel@vger.kernel.org \
--cc=roberto.sassu@huawei.com \
--cc=roberto.sassu@huaweicloud.com \
--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.