From: Yu Liao <liaoyu15@huawei.com>
To: syzbot <syzbot+ed7d0f71a89e28557a77@syzkaller.appspotmail.com>,
<brauner@kernel.org>, <broonie@kernel.org>,
<catalin.marinas@arm.com>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <madvenka@linux.microsoft.com>,
<scott@os.amperecomputing.com>, <syzkaller-bugs@googlegroups.com>,
<will@kernel.org>
Cc: <bobo.shaobowang@huawei.com>, <liwei391@huawei.com>
Subject: Re: [syzbot] INFO: task hung in gfs2_gl_hash_clear (3)
Date: Thu, 1 Dec 2022 14:15:13 +0800 [thread overview]
Message-ID: <771e309e-d7c6-d4db-ab11-0df05db6b9a0@huawei.com> (raw)
In-Reply-To: <000000000000d482ba05ee97d4e3@google.com>
On 2022/11/29 16:32, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 6d464646530f Merge branch 'for-next/core' into for-kernelci
> git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
> console output: https://syzkaller.appspot.com/x/log.txt?x=167aebbb880000
> kernel config: https://syzkaller.appspot.com/x/.config?x=54b747d981acc7b7
> dashboard link: https://syzkaller.appspot.com/bug?extid=ed7d0f71a89e28557a77
> compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
> userspace arch: arm64
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16467353880000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=168c3d03880000
>
Fix missing call gfs2_make_fs_ro() int gfs2_put_super()
#syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
b7b275e60bcd
--- a/fs/gfs2/super.c
+++ b/fs/gfs2/super.c
@@ -584,9 +584,7 @@ static void gfs2_put_super(struct super_block *sb)
}
spin_unlock(&sdp->sd_jindex_spin);
- if (!sb_rdonly(sb)) {
- gfs2_make_fs_ro(sdp);
- }
+ gfs2_make_fs_ro(sdp);
WARN_ON(gfs2_withdrawing(sdp));
/* At this point, we're through modifying the disk */
--
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-12-01 6:16 UTC|newest]
Thread overview: 11+ 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-30 10:01 ` Wangshaobo (bobo)
2022-11-30 10:07 ` Dmitry Vyukov
2022-12-01 1:37 ` Wangshaobo (bobo)
2022-11-30 19:26 ` syzbot
2022-12-01 1:34 ` Wangshaobo (bobo)
2022-12-01 4:18 ` syzbot
2022-12-01 6:15 ` Yu Liao [this message]
2022-12-01 6:30 ` syzbot
2024-01-22 4:21 ` [syzbot] [gfs2?] " syzbot
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=771e309e-d7c6-d4db-ab11-0df05db6b9a0@huawei.com \
--to=liaoyu15@huawei.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=syzbot+ed7d0f71a89e28557a77@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).