From: Jens Axboe <axboe@kernel.dk>
To: syzbot <syzbot+c29db0c6705a06cb65f2@syzkaller.appspotmail.com>,
anna-maria@linutronix.de, frederic@kernel.org,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de
Subject: Re: [syzbot] [io-uring?] INFO: task hung in vfs_coredump
Date: Thu, 10 Jul 2025 17:03:51 -0600 [thread overview]
Message-ID: <b3b56a18-fdaf-4d62-946b-89dfba89f044@kernel.dk> (raw)
In-Reply-To: <687040ca.a00a0220.26a83e.0026.GAE@google.com>
On 7/10/25 4:38 PM, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch and the reproducer did not trigger any issue:
>
> Reported-by: syzbot+c29db0c6705a06cb65f2@syzkaller.appspotmail.com
> Tested-by: syzbot+c29db0c6705a06cb65f2@syzkaller.appspotmail.com
>
> Tested on:
>
> commit: 5f9df768 Merge branch 'mm-everything' of git://git.ker..
> git tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git --
> console output: https://syzkaller.appspot.com/x/log.txt?x=137fc0f0580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=44a6ca1881a12208
> dashboard link: https://syzkaller.appspot.com/bug?extid=c29db0c6705a06cb65f2
> compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
>
> Note: no patches were applied.
> Note: testing is done by a robot and is best-effort only.
Pretty sure this was a fluke in linux-next, as it triggered around
that coredump rework, but then stopped triggering.
#syz invalid
--
Jens Axboe
prev parent reply other threads:[~2025-07-10 23:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 15:52 [syzbot] [io-uring?] INFO: task hung in vfs_coredump syzbot
2025-07-03 16:38 ` Jens Axboe
2025-07-03 20:20 ` syzbot
2025-07-10 18:01 ` Jens Axboe
2025-07-10 22:38 ` syzbot
2025-07-10 23:03 ` Jens Axboe [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=b3b56a18-fdaf-4d62-946b-89dfba89f044@kernel.dk \
--to=axboe@kernel.dk \
--cc=anna-maria@linutronix.de \
--cc=frederic@kernel.org \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+c29db0c6705a06cb65f2@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/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