From: Jan Kara <jack@suse.cz>
To: syzbot <syzbot+9157524e62303fd7b21c@syzkaller.appspotmail.com>
Cc: axboe@kernel.dk, brauner@kernel.org, jack@suse.cz,
jfs-discussion@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
shaggy@kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [jfs?] INFO: task hung in jfs_commit_inode (2)
Date: Thu, 18 Apr 2024 10:40:51 +0200 [thread overview]
Message-ID: <20240418084051.esp56zy6ncoay3g2@quack3> (raw)
In-Reply-To: <000000000000a4f241061659def0@google.com>
On Thu 18-04-24 00:25:03, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
>
> commit 6f861765464f43a71462d52026fbddfc858239a5
> Author: Jan Kara <jack@suse.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@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2024-04-18 8:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 19:55 [syzbot] [jfs?] INFO: task hung in jfs_commit_inode (2) syzbot
2024-04-18 7:25 ` syzbot
2024-04-18 8:40 ` Jan Kara [this message]
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=20240418084051.esp56zy6ncoay3g2@quack3 \
--to=jack@suse.cz \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@kernel.org \
--cc=syzbot+9157524e62303fd7b21c@syzkaller.appspotmail.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 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).