From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Carlos Llamas <cmllamas@google.com>
Cc: "Arve Hjønnevåg" <arve@android.com>,
"Todd Kjos" <tkjos@android.com>,
"Martijn Coenen" <maco@android.com>,
"Joel Fernandes" <joel@joelfernandes.org>,
"Christian Brauner" <brauner@kernel.org>,
"Suren Baghdasaryan" <surenb@google.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
"Michal Hocko" <mhocko@kernel.org>,
"Vlastimil Babka" <vbabka@suse.cz>,
"Matthew Wilcox" <willy@infradead.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, kernel-team@android.com,
"Jann Horn" <jannh@google.com>,
stable@vger.kernel.org, "Minchan Kim" <minchan@kernel.org>,
"Yang Shi" <yang.shi@linux.alibaba.com>,
"Liam Howlett" <liam.howlett@oracle.com>,
"Todd Kjos" <tkjos@google.com>
Subject: Re: [PATCH] binder: fix UAF of alloc->vma in race with munmap()
Date: Sat, 20 May 2023 10:54:15 +0100 [thread overview]
Message-ID: <2023052048-sloping-credible-8871@gregkh> (raw)
In-Reply-To: <20230519195950.1775656-1-cmllamas@google.com>
On Fri, May 19, 2023 at 07:59:49PM +0000, Carlos Llamas wrote:
> [ cmllamas: clean forward port from commit 015ac18be7de ("binder: fix
> UAF of alloc->vma in race with munmap()") in 5.10 stable. It is needed
> in mainline after the revert of commit a43cfc87caaf ("android: binder:
> stop saving a pointer to the VMA") as pointed out by Liam. The commit
> log and tags have been tweaked to reflect this. ]
I'm confused, is this for a stable release (and if so, which one), or is
this for Linus's tree?
thanks,
greg k-h
next prev parent reply other threads:[~2023-05-20 9:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 19:59 [PATCH] binder: fix UAF of alloc->vma in race with munmap() Carlos Llamas
2023-05-20 9:54 ` Greg Kroah-Hartman [this message]
2023-05-20 12:35 ` Carlos Llamas
2023-05-20 9:55 ` Greg Kroah-Hartman
2023-05-20 12:51 ` Carlos Llamas
2023-05-20 16:29 ` Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2023-05-20 10:22 Fred Lewis
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=2023052048-sloping-credible-8871@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=arve@android.com \
--cc=brauner@kernel.org \
--cc=cmllamas@google.com \
--cc=jannh@google.com \
--cc=joel@joelfernandes.org \
--cc=kernel-team@android.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=mhocko@kernel.org \
--cc=minchan@kernel.org \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=tkjos@android.com \
--cc=tkjos@google.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=yang.shi@linux.alibaba.com \
/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.