From: Greg KH <gregkh@linuxfoundation.org>
To: Rajani kantha <rajanikantha@engineer.com>
Cc: lizhi.xu@windriver.com, tytso@mit.edu, stable@vger.kernel.org
Subject: Re: [PATCH 6.6.y] ext4: filesystems without casefold feature cannot be mounted with siphash
Date: Thu, 30 Jan 2025 13:58:27 +0100 [thread overview]
Message-ID: <2025013034-whooping-defraud-f4bd@gregkh> (raw)
In-Reply-To: <trinity-9fdb9995-866f-4221-8e4b-f08e3d33894b-1737681797536@3c-app-mailcom-lxa10>
On Fri, Jan 24, 2025 at 02:23:17AM +0100, Rajani kantha wrote:
> From: Lizhi Xu <lizhi.xu@windriver.com>
>
> [ upstream commit 985b67cd86392310d9e9326de941c22fc9340eec ]
>
> When mounting the ext4 filesystem, if the default hash version is set to
> DX_HASH_SIPHASH but the casefold feature is not set, exit the mounting.
>
> Reported-by: syzbot+340581ba9dceb7e06fb3@syzkaller.appspotmail.com
> Signed-off-by: Lizhi Xu <lizhi.xu@windriver.com>
> Link: https://patch.msgid.link/20240605012335.44086-1-lizhi.xu@windriver.com
> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
> Signed-off-by: Rajani Kantha <rajanikantha@engineer.com>
> ---
> fs/ext4/super.c | 7 +++++++
> 1 file changed, 7 insertions(+)
Why are you submitting this for these 2 kernels? Why are they required
for them? You didn't provide any information here at all :(
And what about the fix for this commit? You forgot that. Please send a
proper series of backports and make sure you actually tested them.
thanks,
gre gk-h
prev parent reply other threads:[~2025-01-30 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 1:23 [PATCH 6.6.y] ext4: filesystems without casefold feature cannot be mounted with siphash Rajani kantha
2025-01-30 12:58 ` Greg KH [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=2025013034-whooping-defraud-f4bd@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=lizhi.xu@windriver.com \
--cc=rajanikantha@engineer.com \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
/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