From: Sasha Levin <sashal@kernel.org>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: stable@vger.kernel.org, Minchan Kim <minchan@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 6.11.y 1/2] zram: free secondary algorithms names
Date: Fri, 11 Oct 2024 08:13:48 -0400 [thread overview]
Message-ID: <ZwkWfP3I5WC69Z9_@sashalap> (raw)
In-Reply-To: <20241009044639.812634-1-senozhatsky@chromium.org>
On Wed, Oct 09, 2024 at 01:46:38PM +0900, Sergey Senozhatsky wrote:
>We need to kfree() secondary algorithms names when reset zram device that
>had multi-streams, otherwise we leak memory.
>
>[senozhatsky@chromium.org: kfree(NULL) is legal]
> Link: https://lkml.kernel.org/r/20240917013021.868769-1-senozhatsky@chromium.org
>Link: https://lkml.kernel.org/r/20240911025600.3681789-1-senozhatsky@chromium.org
>Fixes: 001d92735701 ("zram: add recompression algorithm sysfs knob")
>Signed-off-by: Sergey Senozhatsky <senozhatsky@chromium.org>
>Cc: Minchan Kim <minchan@kernel.org>
>Cc: <stable@vger.kernel.org>
>Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
>(cherry picked from commit 684826f8271ad97580b138b9ffd462005e470b99)
>Signed-off-by: Sergey Senozhatsky <senozhatsky@chromium.org>
Queued up, thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2024-10-11 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 15:06 FAILED: patch "[PATCH] zram: free secondary algorithms names" failed to apply to 6.11-stable tree gregkh
2024-10-09 4:46 ` [PATCH 6.11.y 1/2] zram: free secondary algorithms names Sergey Senozhatsky
2024-10-09 4:46 ` [PATCH 6.11.y 2/2] zram: don't free statically defined names Sergey Senozhatsky
2024-10-11 12:13 ` Sasha Levin [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=ZwkWfP3I5WC69Z9_@sashalap \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=minchan@kernel.org \
--cc=senozhatsky@chromium.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).