All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+6bdbdd12cf8cdbc66466@syzkaller.appspotmail.com>
To: anders.roxell@linaro.org, arnd@arndb.de, brauner@kernel.org,
	 frank.li@vivo.com, glaubitz@physik.fu-berlin.de,
	 linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	 slava@dubeyko.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [hfs?] INFO: task hung in hfs_mdb_commit (3)
Date: Mon, 11 Aug 2025 06:11:04 -0700	[thread overview]
Message-ID: <6899ebe8.a70a0220.7865.003f.GAE@google.com> (raw)
In-Reply-To: <684c05ba.050a0220.be214.029e.GAE@google.com>

syzbot suspects this issue was fixed by commit:

commit 42b0ef01e6b5e9c77b383d32c25a0ec2a735d08a
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Fri Jul 11 08:46:51 2025 +0000

    block: fix FS_IOC_GETLBMD_CAP parsing in blkdev_common_ioctl()

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=133fa9a2580000
start commit:   19272b37aa4f Linux 6.16-rc1
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=c07f08ee4bcfb276
dashboard link: https://syzkaller.appspot.com/bug?extid=6bdbdd12cf8cdbc66466
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=16e6ca0c580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=15d429d4580000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: block: fix FS_IOC_GETLBMD_CAP parsing in blkdev_common_ioctl()

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      reply	other threads:[~2025-08-11 13:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-13 11:04 [syzbot] [hfs?] INFO: task hung in hfs_mdb_commit (3) syzbot
2025-08-11 13:11 ` syzbot [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=6899ebe8.a70a0220.7865.003f.GAE@google.com \
    --to=syzbot+6bdbdd12cf8cdbc66466@syzkaller.appspotmail.com \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=brauner@kernel.org \
    --cc=frank.li@vivo.com \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=slava@dubeyko.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.