From: syzbot <syzbot+ed7d0f71a89e28557a77@syzkaller.appspotmail.com>
To: bobo.shaobowang@huawei.com, brauner@kernel.org,
broonie@kernel.org, catalin.marinas@arm.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, liwei391@huawei.com,
madvenka@linux.microsoft.com, scott@os.amperecomputing.com,
syzkaller-bugs@googlegroups.com, will@kernel.org
Subject: Re: [syzbot] INFO: task hung in gfs2_gl_hash_clear (3)
Date: Wed, 30 Nov 2022 11:26:17 -0800 [thread overview]
Message-ID: <0000000000001767a405eeb514eb@google.com> (raw)
In-Reply-To: <cd4158d0-bfc0-099c-c914-4889eaf95036@huawei.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
checking file fs/gfs2/super.c
patch: **** unexpected end of file in patch
Tested on:
commit: b7b275e6 Linux 6.1-rc7
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
dashboard link: https://syzkaller.appspot.com/bug?extid=ed7d0f71a89e28557a77
compiler:
userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=1751c2bd880000
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+ed7d0f71a89e28557a77@syzkaller.appspotmail.com>
To: bobo.shaobowang@huawei.com, brauner@kernel.org,
broonie@kernel.org, catalin.marinas@arm.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, liwei391@huawei.com,
madvenka@linux.microsoft.com, scott@os.amperecomputing.com,
syzkaller-bugs@googlegroups.com, will@kernel.org
Subject: Re: [syzbot] INFO: task hung in gfs2_gl_hash_clear (3)
Date: Wed, 30 Nov 2022 11:26:17 -0800 [thread overview]
Message-ID: <0000000000001767a405eeb514eb@google.com> (raw)
In-Reply-To: <cd4158d0-bfc0-099c-c914-4889eaf95036@huawei.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
checking file fs/gfs2/super.c
patch: **** unexpected end of file in patch
Tested on:
commit: b7b275e6 Linux 6.1-rc7
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
dashboard link: https://syzkaller.appspot.com/bug?extid=ed7d0f71a89e28557a77
compiler:
userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=1751c2bd880000
next prev parent reply other threads:[~2022-11-30 19:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 8:32 [syzbot] INFO: task hung in gfs2_gl_hash_clear (3) syzbot
2022-11-29 8:32 ` syzbot
2022-11-30 10:01 ` Wangshaobo (bobo)
2022-11-30 10:01 ` Wangshaobo (bobo)
2022-11-30 10:07 ` Dmitry Vyukov
2022-11-30 10:07 ` Dmitry Vyukov
2022-12-01 1:37 ` Wangshaobo (bobo)
2022-12-01 1:37 ` Wangshaobo (bobo)
2022-11-30 19:26 ` syzbot [this message]
2022-11-30 19:26 ` syzbot
2022-12-01 1:34 ` Wangshaobo (bobo)
2022-12-01 1:34 ` Wangshaobo (bobo)
2022-12-01 4:18 ` syzbot
2022-12-01 4:18 ` syzbot
2022-12-01 6:15 ` Yu Liao
2022-12-01 6:15 ` Yu Liao
2022-12-01 6:30 ` syzbot
2022-12-01 6:30 ` syzbot
2024-01-22 4:21 ` [syzbot] [gfs2?] " syzbot
2024-01-22 4:21 ` syzbot
2024-01-23 9:05 ` Jan Kara
2024-01-23 9:05 ` Jan Kara
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=0000000000001767a405eeb514eb@google.com \
--to=syzbot+ed7d0f71a89e28557a77@syzkaller.appspotmail.com \
--cc=bobo.shaobowang@huawei.com \
--cc=brauner@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liwei391@huawei.com \
--cc=madvenka@linux.microsoft.com \
--cc=scott@os.amperecomputing.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=will@kernel.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.