From: bugzilla-daemon--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 220321] F2FS: workqueue: WQ_MEM_RECLAIM writeback:wb_workfn is flushing !WQ_MEM_RECLAIM events_unbound:quota_release_workfn
Date: Fri, 18 Jul 2025 09:12:48 +0000 [thread overview]
Message-ID: <bug-220321-202145-HIRPgyltJV@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220321-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220321
--- Comment #4 from Chao Yu (chao@kernel.org) ---
Sorry for the delay.
The workqueue is not allocated by f2fs, not sure this is a f2fs bug...
Can you please report this issue to fsdevel mailing list:
linux-fsdevel@vger.kernel.org?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2025-07-18 9:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 7:28 [f2fs-dev] [Bug 220321] New: F2FS: workqueue: WQ_MEM_RECLAIM writeback:wb_workfn is flushing !WQ_MEM_RECLAIM events_unbound:quota_release_workfn bugzilla-daemon--- via Linux-f2fs-devel
2025-07-07 11:51 ` [f2fs-dev] [Bug 220321] " bugzilla-daemon--- via Linux-f2fs-devel
2025-07-08 2:15 ` bugzilla-daemon--- via Linux-f2fs-devel
2025-07-18 7:22 ` bugzilla-daemon--- via Linux-f2fs-devel
2025-07-18 9:12 ` bugzilla-daemon--- via Linux-f2fs-devel [this message]
2025-07-21 6:50 ` bugzilla-daemon--- via Linux-f2fs-devel
2025-07-29 1:57 ` bugzilla-daemon--- via Linux-f2fs-devel
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=bug-220321-202145-HIRPgyltJV@https.bugzilla.kernel.org/ \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=bugzilla-daemon@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).