From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: jannh@google.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] mm: lock_vma_under_rcu() must check vma->anon_vma under vma" failed to apply to 6.4-stable tree
Date: Fri, 4 Aug 2023 12:27:27 +0200 [thread overview]
Message-ID: <2023080418-anvil-grumbly-c3ff@gregkh> (raw)
In-Reply-To: <CAHk-=wjfdPq6=rwECsYaSzFaehBoGxGEHwyJmAVK0ekXoS89FQ@mail.gmail.com>
On Tue, Aug 01, 2023 at 09:34:10AM -0700, Linus Torvalds wrote:
> On Mon, 31 Jul 2023 at 23:28, <gregkh@linuxfoundation.org> wrote:
> >
> > The patch below does not apply to the 6.4-stable tree.
>
> Ahh. The vma_is_tcp() checks are new.
>
> I think you can literally just remove all occurrences of
>
> && !vma_is_tcp(vma)
>
> in that patch to make it apply.
>
> The end result should look something like the attached, afaik.
Thanks, that worked, now queued up.
greg k-h
prev parent reply other threads:[~2023-08-04 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 6:28 FAILED: patch "[PATCH] mm: lock_vma_under_rcu() must check vma->anon_vma under vma" failed to apply to 6.4-stable tree gregkh
2023-08-01 16:34 ` Linus Torvalds
2023-08-04 10:27 ` 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=2023080418-anvil-grumbly-c3ff@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jannh@google.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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