From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Amir Goldstein <amir73il@gmail.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.15 1/2] ext4: make 'abort' mount option handling standard
Date: Thu, 19 Jun 2025 05:02:30 -0400 [thread overview]
Message-ID: <20250618163746-e5d04fd8379a58c2@stable.kernel.org> (raw)
In-Reply-To: <20250617210956.146158-2-amir73il@gmail.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: 22b8d707b07e6e06f50fe1d9ca8756e1f894eb0d
WARNING: Author mismatch between patch and upstream commit:
Backport author: Amir Goldstein<amir73il@gmail.com>
Commit author: Jan Kara<jack@suse.cz>
Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (exact SHA1)
6.1.y | Present (different SHA1: a8dad6db0ed6)
Note: The patch differs from the upstream commit:
---
1: 22b8d707b07e6 < -: ------------- ext4: make 'abort' mount option handling standard
-: ------------- > 1: 448450a6537d0 ext4: make 'abort' mount option handling standard
---
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-06-19 9:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 21:09 [PATCH 5.15 0/2] fix LTP regression in fanotify22 Amir Goldstein
2025-06-17 21:09 ` [PATCH 5.15 1/2] ext4: make 'abort' mount option handling standard Amir Goldstein
2025-06-19 9:02 ` Sasha Levin [this message]
2025-06-17 21:09 ` [PATCH 5.15 2/2] ext4: avoid remount errors with 'abort' mount option Amir Goldstein
2025-06-19 9:04 ` Sasha Levin
2025-06-17 21:16 ` [PATCH 5.15 0/2] fix LTP regression in fanotify22 Amir Goldstein
2025-06-18 15:30 ` Jan Kara
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=20250618163746-e5d04fd8379a58c2@stable.kernel.org \
--to=sashal@kernel.org \
--cc=amir73il@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox