[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240418084051.esp56zy6ncoay3g2@quack3>
Date: Thu, 18 Apr 2024 10:40:51 +0200
From: Jan Kara <jack@...e.cz>
To: syzbot <syzbot+9157524e62303fd7b21c@...kaller.appspotmail.com>
Cc: axboe@...nel.dk, brauner@...nel.org, jack@...e.cz,
jfs-discussion@...ts.sourceforge.net, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, shaggy@...nel.org,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [jfs?] INFO: task hung in jfs_commit_inode (2)
On Thu 18-04-24 00:25:03, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
>
> commit 6f861765464f43a71462d52026fbddfc858239a5
> Author: Jan Kara <jack@...e.cz>
> Date: Wed Nov 1 17:43:10 2023 +0000
>
> fs: Block writes to mounted block devices
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=155eb8f7180000
> start commit: 4f9e7fabf864 Merge tag 'trace-v6.5-rc6' of git://git.kerne..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=1b32f62c755c3a9c
> dashboard link: https://syzkaller.appspot.com/bug?extid=9157524e62303fd7b21c
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=101aff5ba80000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14d78db0680000
>
> If the result looks correct, please mark the issue as fixed by replying with:
Looks unlikely. The reproducer just mounts the jfs image and then a fuse
image...
Honza
--
Jan Kara <jack@...e.com>
SUSE Labs, CR
Powered by blists - more mailing lists