From: Chuck Lever <chuck.lever@oracle.com>
To: Chen Chen via Bugspray Bot <bugbot@kernel.org>,
anna@kernel.org, linux-nfs@vger.kernel.org, linux-mm@kvack.org,
jlayton@kernel.org, cel@kernel.org, trondmy@kernel.org
Subject: Re: Possible memory leak on nfsd
Date: Fri, 10 Jan 2025 15:35:20 -0500 [thread overview]
Message-ID: <463b4513-5c5a-4394-8a93-58c0feef3149@oracle.com> (raw)
In-Reply-To: <20250110-b219535c15-7cebc629b312@bugzilla.kernel.org>
On 1/10/25 11:50 AM, Chen Chen via Bugspray Bot wrote:
> Chen Chen writes via Kernel.org Bugzilla:
>
> Sorry for my rudeness in my previous discussion.
>
> After switching to 6.12.4, the server stayed stable for 30 days.
That's good news!
> So whatever caused the memleak should have been resolved between 6.1.119 to 6.12.
That's tens of thousands of commits over two years. Unfortunately that
doesn't really tell us what the problem is.
> You might want to close this bug if backport is not worthwhile.
We need to know the exact commit that contains the fix before it can
be determined whether a backport is feasible.
Are you able to bisect between v6.1 and v6.12 ? If not, do you have
a simple, narrow reproducer that we can use to explore this ourselves?
--
Chuck Lever
next prev parent reply other threads:[~2025-01-10 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241127-b219535c0-4d5445e74947@bugzilla.kernel.org>
2025-01-10 16:50 ` Chen Chen via Bugspray Bot
2025-01-10 20:35 ` Chuck Lever [this message]
2025-01-22 20:45 ` JJ Jordan via Bugspray Bot
2025-01-22 21:25 ` JJ Jordan via Bugspray Bot
2025-01-22 21:25 ` JJ Jordan via Bugspray Bot
2025-01-22 21:25 ` JJ Jordan via Bugspray Bot
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=463b4513-5c5a-4394-8a93-58c0feef3149@oracle.com \
--to=chuck.lever@oracle.com \
--cc=anna@kernel.org \
--cc=bugbot@kernel.org \
--cc=cel@kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@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