From: Sasha Levin <sashal@kernel.org>
To: Hungyu Lin <dennylin0707@gmail.com>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, Chris Mason <mason@kernel.org>,
Amir Goldstein <amir73il@gmail.com>
Subject: Re: [PATCH 6.18.y] ovl: fail the mount if the casefold flag has changed
Date: Fri, 13 Nov 2026 14:10:03 -0500 [thread overview]
Message-ID: <draft-0013-regoldsteinovlcasefo@kernel.org> (raw)
In-Reply-To: <CAOQ4uxirbtnBbeyHbq=gm+ttA=0nusQjsCoK0FsajZfqL1ZEMA@mail.gmail.com>
On Thu, Nov 12, 2026 at 9:43 AM Hungyu Lin <dennylin0707@gmail.com> wrote:
> From: Chris Mason <mason@kernel.org>
>
> [ Upstream commit c782fc8ada811569811c0fdea5c3412511be95d0 ]
>
> The casefold flag of the overlay root must match the flag recorded when
> validating the layer roots.
On Thu, Nov 12, 2026, Amir Goldstein wrote:
> What happened to the original commit message?
Agreed. A stable backport keeps the upstream commit message as is. What changed
for this tree goes in a bracketed note just above the backporter's
Signed-off-by, e.g. "[ Hungyu: ... ]".
Hungyu, please resend with the original message restored and the 6.18
explanation moved into such a note.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-11-13 19:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 1:05 FAILED: patch "[PATCH] ovl: fail the mount if the casefold flag has changed" failed to apply to 6.18-stable tree Sasha Levin
2026-11-12 8:43 ` [PATCH 6.18.y] ovl: fail the mount if the casefold flag has changed Hungyu Lin
2026-11-12 9:05 ` Amir Goldstein
2026-11-13 19:10 ` Sasha Levin [this message]
2026-11-13 19:13 ` Amir Goldstein
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=draft-0013-regoldsteinovlcasefo@kernel.org \
--to=sashal@kernel.org \
--cc=amir73il@gmail.com \
--cc=dennylin0707@gmail.com \
--cc=mason@kernel.org \
--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 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.