[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKFNMonK2VcZx=KEG8cz61bhwMvChEJ=T+FecxpGg1QiRCcZhA@mail.gmail.com>
Date: Sun, 30 Apr 2023 17:56:47 +0900
From: Ryusuke Konishi <konishi.ryusuke@...il.com>
To: "Theodore Ts'o" <tytso@....edu>
Cc: syzbot <syzbot+221d75710bde87fa0e97@...kaller.appspotmail.com>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
syzkaller-bugs@...glegroups.com, viro@...iv.linux.org.uk
Subject: Re: INFO: task hung in lock_mount
On Sun, Apr 30, 2023 at 3:59 PM Theodore Ts'o wrote:
>
> #syz set subsystems: nilfs
>
> Per the information in the dashboard:
>
> https://syzkaller.appspot.com/bug?extid=221d75710bde87fa0e97
>
> There is no mention of ext4 anywhere, and nilfs does show up in the
> stack trace. So why this is marked with the lables "ext4", "nilfs" is
> a mystery.
>
> Fix it.
I don't know why it got the ext4 tag.
As you say, it looks like an issue on the nilfs2 side. I will
identify and fix it.
Regards,
Ryusuke Konishi
Powered by blists - more mailing lists