All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+180dd013ba371eabc162@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, heming.zhao@suse.com, jack@suse.cz,
	 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?] possible deadlock in deactivate_super (2)
Date: Tue, 10 Jun 2025 09:28:04 -0700	[thread overview]
Message-ID: <68485d14.050a0220.33aa0e.035f.GAE@google.com> (raw)
In-Reply-To: <679f7c8e.050a0220.163cdc.002f.GAE@google.com>

syzbot suspects this issue was fixed by commit:

commit fcaf3b2683b05a9684acdebda706a12025a6927a
Author: Jan Kara <jack@suse.cz>
Date:   Thu Apr 24 13:45:13 2025 +0000

    ocfs2: stop quota recovery before disabling quotas

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=123ce9d4580000
start commit:   8560697b23dc Merge tag '6.15-rc2-smb3-client-fixes' of git..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=170d968a88ba5c06
dashboard link: https://syzkaller.appspot.com/bug?extid=180dd013ba371eabc162
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12d39b98580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10fbd204580000

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

#syz fix: ocfs2: stop quota recovery before disabling quotas

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

  reply	other threads:[~2025-06-10 16:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-02 14:09 [syzbot] [ocfs2?] possible deadlock in deactivate_super (2) syzbot
2025-06-10 16:28 ` syzbot [this message]
2025-06-12  8:24   ` Jan Kara

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=68485d14.050a0220.33aa0e.035f.GAE@google.com \
    --to=syzbot+180dd013ba371eabc162@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=heming.zhao@suse.com \
    --cc=jack@suse.cz \
    --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.