Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	stable@vger.kernel.org, linux-unionfs@vger.kernel.org
Subject: [PATCH 6.6 0/2] ovl: backports of fixes that failed to apply
Date: Wed,  4 Nov 2026 19:45:57 +0100	[thread overview]
Message-ID: <20261104184559.3630145-1-amir73il@gmail.com> (raw)

Greg,

These are backports of two overlayfs fixes from ovl-fixes-7.3 that
failed to apply to the 6.6 and 6.1 stable trees:

  65bf000962a3 ("ovl: take a snapshot of the name for copy up")
  4f61ff2ebfb3 ("ovl: use the pinned upper dir in ovl_fix_origin()")

The same backports are expected to apply cleanly to 6.6 and 6.1, so
please apply this series to both trees. The upstream commits are
already queued for 6.18 and 6.12.

The patches do not depend on each other and can be applied in any order.

Thanks,
Amir.

Chris Mason (2):
  ovl: take a snapshot of the name for copy up
  ovl: use the pinned upper dir in ovl_fix_origin()

 fs/overlayfs/copy_up.c   | 16 ++++++++++++++--
 fs/overlayfs/namei.c     |  6 ++++--
 fs/overlayfs/overlayfs.h |  6 ++++++
 3 files changed, 24 insertions(+), 4 deletions(-)

-- 
backport

             reply	other threads:[~2026-11-04 18:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04 18:45 Amir Goldstein [this message]
2026-11-04 18:45 ` [PATCH 6.6 1/2] ovl: take a snapshot of the name for copy up Amir Goldstein
2026-11-04 18:45 ` [PATCH 6.6 2/2] ovl: use the pinned upper dir in ovl_fix_origin() 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=20261104184559.3630145-1-amir73il@gmail.com \
    --to=amir73il@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox