From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Sasha Levin <sashal@kernel.org>,
Miklos Szeredi <miklos@szeredi.hu>, Jan Kara <jack@suse.cz>,
Dmitry Safonov <dima@arista.com>,
Ignat Korchagin <ignat@cloudflare.com>,
linux-fsdevel@vger.kernel.org, linux-unionfs@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 6.6 0/3] Manual backport of overlayfs fixes from v6.6.72
Date: Tue, 21 Jan 2025 12:21:48 +0100 [thread overview]
Message-ID: <2025012133-gradually-unsteady-6783@gregkh> (raw)
In-Reply-To: <CAOQ4uxj+LF602e3ypBHLpgWhO46CUaqn+sQ6Fcbq8r2cLJu8iA@mail.gmail.com>
On Tue, Jan 21, 2025 at 12:14:28PM +0100, Amir Goldstein wrote:
> On Tue, Jan 21, 2025 at 12:08 PM Amir Goldstein <amir73il@gmail.com> wrote:
> >
> > Greg,
> >
> > Per your request, here is a manual backport of the overlayfs fixes that
> > were applied in v6.6.72 and reverted in v6.6.73.
> >
>
> Forgot to mention that I backported one extra patch from 6.12.y.
> It is not an overlayfs patch, but it fixes in a more generic way
> (removing an unneeded assertion) the same bug report that the
> overlayfs patches fix.
>
> Both fixes are needed, because the assertion could have been hit
> without overlayfs and because the overlayfs fixes are needed to
> fix bugs other than the assertion.
No worries, looks good, thanks for the backports, I'll go queue them up
right now.
greg k-h
prev parent reply other threads:[~2025-01-21 11:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 11:08 [PATCH 6.6 0/3] Manual backport of overlayfs fixes from v6.6.72 Amir Goldstein
2025-01-21 11:08 ` [PATCH 6.6 1/3] ovl: pass realinode to ovl_encode_real_fh() instead of realdentry Amir Goldstein
2025-01-21 19:52 ` Sasha Levin
2025-01-21 11:08 ` [PATCH 6.6 2/3] ovl: support encoding fid from inode with no alias Amir Goldstein
2025-01-21 11:08 ` [PATCH 6.6 3/3] fs: relax assertions on failure to encode file handles Amir Goldstein
2025-01-21 11:14 ` [PATCH 6.6 0/3] Manual backport of overlayfs fixes from v6.6.72 Amir Goldstein
2025-01-21 11:21 ` Greg Kroah-Hartman [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=2025012133-gradually-unsteady-6783@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=amir73il@gmail.com \
--cc=dima@arista.com \
--cc=ignat@cloudflare.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=sashal@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.