All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Xiangyu Chen <xiangyu.chen@eng.windriver.com>,
	Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.10] ext4: fix timer use-after-free on failed mount
Date: Sun, 13 Apr 2025 12:47:09 -0400	[thread overview]
Message-ID: <20250412093559-a4db30332c9399a2@stable.kernel.org> (raw)
In-Reply-To: <20250411081911.219016-2-xiangyu.chen@eng.windriver.com>

[ Sasha's backport helper bot ]

Hi,

✅ All tests passed successfully. No issues detected.
No action required from the submitter.

The upstream commit SHA1 provided is correct: 0ce160c5bdb67081a62293028dc85758a8efb22a

WARNING: Author mismatch between patch and upstream commit:
Backport author: Xiangyu Chen<xiangyu.chen@eng.windriver.com>
Commit author: Xiaxi Shen<shenxiaxi26@gmail.com>

Status in newer kernel trees:
6.14.y | Present (exact SHA1)
6.13.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: 9203817ba46e)
6.1.y | Present (different SHA1: cf3196e5e2f3)
5.15.y | Present (different SHA1: 2a4ae3bcdf05)

Note: The patch differs from the upstream commit:
---
1:  0ce160c5bdb67 < -:  ------------- ext4: fix timer use-after-free on failed mount
-:  ------------- > 1:  1c2c1669ad83f ext4: fix timer use-after-free on failed mount
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.10.y       |  Success    |  Success   |

  reply	other threads:[~2025-04-13 16:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-11  8:19 [PATCH 5.15] ext4: fix timer use-after-free on failed mount Xiangyu Chen
2025-04-11  8:19 ` [PATCH 5.10] " Xiangyu Chen
2025-04-13 16:47   ` Sasha Levin [this message]
2025-04-13 16:46 ` [PATCH 5.15] " Sasha Levin

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=20250412093559-a4db30332c9399a2@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=xiangyu.chen@eng.windriver.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 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.