From: Greg KH <gregkh@linuxfoundation.org>
To: vgiraud.opensource@witekio.com
Cc: stable@vger.kernel.org, Lizhi Xu <lizhi.xu@windriver.com>,
syzbot+340581ba9dceb7e06fb3@syzkaller.appspotmail.com,
Theodore Ts'o <tytso@mit.edu>, Bruno VERNAY <bruno.vernay@se.com>
Subject: Re: [PATCH 6.6] ext4: filesystems without casefold feature cannot be mounted with siphash
Date: Thu, 13 Feb 2025 14:55:08 +0100 [thread overview]
Message-ID: <2025021331-neuron-alarm-ecfc@gregkh> (raw)
In-Reply-To: <2025021313-aware-yam-ffec@gregkh>
On Thu, Feb 13, 2025 at 02:53:56PM +0100, Greg KH wrote:
> On Fri, Feb 07, 2025 at 12:37:03PM +0100, vgiraud.opensource@witekio.com wrote:
> > From: Lizhi Xu <lizhi.xu@windriver.com>
> >
> > commit 985b67cd86392310d9e9326de941c22fc9340eec upstream.
> >
> > 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: Bruno VERNAY <bruno.vernay@se.com>
> > Signed-off-by: Victor Giraud <vgiraud.opensource@witekio.com>
> > ---
> > fs/ext4/super.c | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> >
> > diff --git a/fs/ext4/super.c b/fs/ext4/super.c
> > index f019ce64eba4..b69d791be846 100644
> > --- a/fs/ext4/super.c
> > +++ b/fs/ext4/super.c
> > @@ -3627,6 +3627,14 @@ int ext4_feature_set_ok(struct super_block *sb, int readonly)
> > }
> > #endif
> >
> > + if (EXT4_SB(sb)->s_es->s_def_hash_version == DX_HASH_SIPHASH &&
> > + !ext4_has_feature_casefold(sb)) {
> > + ext4_msg(sb, KERN_ERR,
> > + "Filesystem without casefold feature cannot be "
> > + "mounted with siphash");
> > + return 0;
> > + }
> > +
> > if (readonly)
> > return 1;
> >
> > --
> > 2.34.1
> >
> >
>
> Any specific reason you asked for just this one commit to be backported
> and NOT the fix for this commit?
>
> How did you test this?
And the fix did not apply either, so I'm dropping this from all queues.
Be more careful please! Don't submit patches that actually cause
documented problems.
greg k-h
next prev parent reply other threads:[~2025-02-13 13:55 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
2025-02-13 13:53 ` Greg KH
2025-02-13 13:55 ` Greg KH [this message]
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=2025021331-neuron-alarm-ecfc@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bruno.vernay@se.com \
--cc=lizhi.xu@windriver.com \
--cc=stable@vger.kernel.org \
--cc=syzbot+340581ba9dceb7e06fb3@syzkaller.appspotmail.com \
--cc=tytso@mit.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox