All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+ab509d831d9b0222f5fd@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, glass.su@suse.com, jack@suse.com,
	 jlbec@evilplan.org, joseph.qi@linux.alibaba.com,
	linux-kernel@vger.kernel.org,  mark@fasheh.com,
	ocfs2-devel@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] INFO: task hung in flush_delayed_work
Date: Mon, 22 Sep 2025 14:21:02 -0700	[thread overview]
Message-ID: <68d1bdbe.a70a0220.1b52b.0003.GAE@google.com> (raw)
In-Reply-To: <672b23bd.050a0220.2a847.1ba3.GAE@google.com>

syzbot suspects this issue was fixed by commit:

commit 276c61385f6bc3223a5ecd307cf4aba2dfbb9a31
Author: Su Yue <glass.su@suse.com>
Date:   Mon Jan 6 14:06:53 2025 +0000

    ocfs2: mark dquot as inactive if failed to start trans while releasing dquot

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=140da8e2580000
start commit:   2e1b3cc9d7f7 Merge tag 'arm-fixes-6.12-2' of git://git.ker..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=11254d3590b16717
dashboard link: https://syzkaller.appspot.com/bug?extid=ab509d831d9b0222f5fd
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=142f4e30580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=12c00d87980000

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

#syz fix: ocfs2: mark dquot as inactive if failed to start trans while releasing dquot

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

      reply	other threads:[~2025-09-22 21:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-06  8:07 [syzbot] [ocfs2?] INFO: task hung in flush_delayed_work syzbot
2025-09-22 21:21 ` 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=68d1bdbe.a70a0220.1b52b.0003.GAE@google.com \
    --to=syzbot+ab509d831d9b0222f5fd@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=glass.su@suse.com \
    --cc=jack@suse.com \
    --cc=jlbec@evilplan.org \
    --cc=joseph.qi@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark@fasheh.com \
    --cc=ocfs2-devel@lists.linux.dev \
    --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.