public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Miklos Szeredi <mszeredi@redhat.com>
Cc: chengzhihao1@huawei.com, amir73il@gmail.com, brauner@kernel.org,
	stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] ovl: fix null pointer dereference in ovl_permission()" failed to apply to 6.1-stable tree
Date: Thu, 27 Jul 2023 12:57:48 +0200	[thread overview]
Message-ID: <2023072739-arrest-scrimmage-2b16@gregkh> (raw)
In-Reply-To: <CAOssrKdkLGRNn7z=7cOFpq5UtK2pXcZ37cOvn-zH8zrTAA5afA@mail.gmail.com>

On Wed, Jul 26, 2023 at 02:35:38PM +0200, Miklos Szeredi wrote:
> On Sun, Jul 16, 2023 at 6:30 PM <gregkh@linuxfoundation.org> wrote:
> >
> >
> > The patch below does not apply to the 6.1-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
> >
> > To reproduce the conflict and resubmit, you may use the following commands:
> >
> > git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-6.1.y
> > git checkout FETCH_HEAD
> > git cherry-pick -x 1a73f5b8f079fd42a544c1600beface50c63af7c
> 
> Applies and tests cleanly against v6.1.41.
> 
> Maybe the failure was due to dependency on commit b2dd05f107b1 ("ovl:
> let helper ovl_i_path_real() return the realinode")?

Odd, maybe?  I've queued this up now, thanks.

greg k-h

      reply	other threads:[~2023-07-27 10:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-16 16:30 FAILED: patch "[PATCH] ovl: fix null pointer dereference in ovl_permission()" failed to apply to 6.1-stable tree gregkh
2023-07-26 12:35 ` Miklos Szeredi
2023-07-27 10:57   ` 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=2023072739-arrest-scrimmage-2b16@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=amir73il@gmail.com \
    --cc=brauner@kernel.org \
    --cc=chengzhihao1@huawei.com \
    --cc=mszeredi@redhat.com \
    --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