From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: vgiraud.opensource@witekio.com, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.6] ext4: filesystems without casefold feature cannot be mounted with siphash
Date: Fri, 7 Feb 2025 17:50:44 -0500 [thread overview]
Message-ID: <20250207162100-e89711bfcf43067a@stable.kernel.org> (raw)
In-Reply-To: <20250207113703.2444446-1-vgiraud.opensource@witekio.com>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: 985b67cd86392310d9e9326de941c22fc9340eec
WARNING: Author mismatch between patch and upstream commit:
Backport author: vgiraud.opensource@witekio.com
Commit author: Lizhi Xu<lizhi.xu@windriver.com>
Status in newer kernel trees:
6.13.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Not found
Note: The patch differs from the upstream commit:
---
1: 985b67cd86392 < -: ------------- ext4: filesystems without casefold feature cannot be mounted with siphash
-: ------------- > 1: e8a78ebe11154 ext4: filesystems without casefold feature cannot be mounted with siphash
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.6.y | Success | Failed |
Build Errors:
Build error for stable/linux-6.6.y:
ssh: connect to host 192.168.1.58 port 22: No route to host
next prev parent reply other threads:[~2025-02-07 22:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 11:37 [PATCH 6.6] ext4: filesystems without casefold feature cannot be mounted with siphash vgiraud.opensource
2025-02-07 22:50 ` Sasha Levin [this message]
2025-02-13 13:53 ` Greg KH
2025-02-13 13:55 ` Greg KH
2025-02-13 21:08 ` Vasiliy Kovalev
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=20250207162100-e89711bfcf43067a@stable.kernel.org \
--to=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vgiraud.opensource@witekio.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.