From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH kernel 1/2] add fix for CIFS client memory leak
Date: Fri, 12 Jul 2024 16:54:10 +0200 [thread overview]
Message-ID: <bba8bc13-6202-4e59-8473-0660ea9af2c4@proxmox.com> (raw)
In-Reply-To: <20240710113709.1415909-1-f.ebner@proxmox.com>
On 10/07/2024 13:37, Fiona Ebner wrote:
> As reported in the community forum [0], there currently is a memory
> leak in the CIFS client code. Reproduced by running a backup with CIFS
> target storage:
>
>> while true; do vzdump 101 --storage cifs --prune-backups keep-last=1; echo 3 > /proc/sys/vm/drop_caches; done
>
> A fix was found on the kernel mailing list tagged for stable v6.6+
> and it does solve the issue, but is not yet included in any (stable)
> kernels.
>
> [0]: https://forum.proxmox.com/threads/147603/post-682388
>
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
> ...ix-pagecache-leak-when-do-writepages.patch | 108 ++++++++++++++++++
> 1 file changed, 108 insertions(+)
> create mode 100644 patches/kernel/0018-cifs-fix-pagecache-leak-when-do-writepages.patch
>
>
applied both patches, thanks!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-07-12 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 11:37 [pve-devel] " Fiona Ebner
2024-07-10 11:37 ` [pve-devel] [PATCH kernel 2/2] cherry-pick potential fix for NULL pointer deref with AMD Arcturus GPU during boot Fiona Ebner
2024-07-16 9:41 ` Alexander Zeidler
2024-07-12 14:54 ` Thomas Lamprecht [this message]
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=bba8bc13-6202-4e59-8473-0660ea9af2c4@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.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