From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 211329] XFS related memory leak on ppc64le
Date: Mon, 25 Jan 2021 02:15:54 +0000 [thread overview]
Message-ID: <bug-211329-201763-ncdailIAH4@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-211329-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=211329
Cameron (cam@neo-zeon.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|XFS |Other
Product|File System |IO/Storage
--- Comment #5 from Cameron (cam@neo-zeon.de) ---
Yes, they're all blkg_alloc.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-01-25 2:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 23:02 [Bug 211329] New: XFS related memory leak on ppc64le bugzilla-daemon
2021-01-24 23:16 ` [Bug 211329] " bugzilla-daemon
2021-01-25 0:20 ` bugzilla-daemon
2021-01-25 0:38 ` bugzilla-daemon
2021-01-25 1:56 ` bugzilla-daemon
2021-01-25 2:15 ` bugzilla-daemon [this message]
2021-01-26 17:02 ` [Bug 211329] blkg_alloc " bugzilla-daemon
2021-01-30 16:32 ` bugzilla-daemon
2021-01-31 6:44 ` bugzilla-daemon
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-211329-201763-ncdailIAH4@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-xfs@vger.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