From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Dominique Martinet <dominique.martinet@atmark-techno.com>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.15 3/3] zram: fix uninitialized ZRAM not releasing backing device
Date: Sat, 11 Jan 2025 14:04:56 -0500 [thread overview]
Message-ID: <20250111134018-34f885f17251392f@stable.kernel.org> (raw)
In-Reply-To: <20250110075844.1173719-4-dominique.martinet@atmark-techno.com>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: 74363ec674cb172d8856de25776c8f3103f05e2f
WARNING: Author mismatch between patch and upstream commit:
Backport author: Dominique Martinet<dominique.martinet@atmark-techno.com>
Commit author: Kairui Song<kasong@tencent.com>
Status in newer kernel trees:
6.12.y | Present (different SHA1: 6fb92e9a52e3)
6.6.y | Present (different SHA1: 0b5b0b65561b)
6.1.y | Present (different SHA1: ac3b5366b9b7)
5.15.y | Not found
Note: The patch differs from the upstream commit:
---
Failed to apply patch cleanly, falling back to interdiff...
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.15.y | Success | Success |
next prev parent reply other threads:[~2025-01-11 19:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 7:58 [PATCH 5.15 0/3] ZRAM not releasing backing device backport Dominique Martinet
2025-01-10 7:58 ` [PATCH 5.15 1/3] drivers/block/zram/zram_drv.c: do not keep dangling zcomp pointer after zram reset Dominique Martinet
2025-01-11 19:04 ` Sasha Levin
2025-01-10 7:58 ` [PATCH 5.15 2/3] zram: check comp is non-NULL before calling comp_destroy Dominique Martinet
2025-01-10 22:59 ` kernel test robot
2025-01-11 19:05 ` Sasha Levin
2025-01-10 7:58 ` [PATCH 5.15 3/3] zram: fix uninitialized ZRAM not releasing backing device Dominique Martinet
2025-01-11 19:04 ` Sasha Levin [this message]
2025-01-12 10:03 ` [PATCH 5.15 0/3] ZRAM not releasing backing device backport Greg Kroah-Hartman
2025-01-14 7:39 ` Dominique Martinet
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=20250111134018-34f885f17251392f@stable.kernel.org \
--to=sashal@kernel.org \
--cc=dominique.martinet@atmark-techno.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.