From: Heming Zhao <heming.zhao@suse.com>
To: syzbot <syzbot+f59a1ae7b7227c859b8f@syzkaller.appspotmail.com>,
jack@suse.cz, joseph.qi@linux.alibaba.com,
linux-kernel@vger.kernel.org, m.masimov@mt-integration.ru,
ocfs2-devel@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] possible deadlock in ocfs2_finish_quota_recovery
Date: Thu, 17 Apr 2025 13:05:40 +0800 [thread overview]
Message-ID: <e426eaa2-3c17-42d6-906f-c41443ac48d3@suse.com> (raw)
In-Reply-To: <680081ae.050a0220.d9ef5.0003.GAE@google.com>
On 4/17/25 12:21, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch but the reproducer is still triggering an issue:
> unregister_netdevice: waiting for DEV to become free
>
> unregister_netdevice: waiting for batadv0 to become free. Usage count = 3
This is another module's issue, and the deadlock issue disappeared.
- Heming
>
>
> Tested on:
>
> commit: 11376431 ocfs2: Stop quota recovery before disabling q..
> git tree: https://github.com/zhaohem/linux jans_ocfs2
> console output: https://syzkaller.appspot.com/x/log.txt?x=14183a3f980000
> kernel config: https://syzkaller.appspot.com/x/.config?x=5348e7fd1b89a770
> dashboard link: https://syzkaller.appspot.com/bug?extid=f59a1ae7b7227c859b8f
> compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
>
> Note: no patches were applied.
next prev parent reply other threads:[~2025-04-17 5:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <89d94f84-8e88-4860-aaf7-102a51c11537@suse.com>
2025-04-17 4:21 ` [syzbot] [ocfs2?] possible deadlock in ocfs2_finish_quota_recovery syzbot
2025-04-17 5:05 ` Heming Zhao [this message]
2025-02-02 9:01 syzbot
2025-03-13 13:50 ` syzbot
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=e426eaa2-3c17-42d6-906f-c41443ac48d3@suse.com \
--to=heming.zhao@suse.com \
--cc=jack@suse.cz \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.masimov@mt-integration.ru \
--cc=ocfs2-devel@lists.linux.dev \
--cc=syzbot+f59a1ae7b7227c859b8f@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