From: "Kohli, Gaurav" <gkohli@codeaurora.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Arve Hjønnevåg" <arve@android.com>,
"Riley Andrews" <riandrews@android.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: Query:Regarding object poison overwritten in binder_transaction
Date: Mon, 5 Mar 2018 17:09:53 +0530 [thread overview]
Message-ID: <55a473e8-a2eb-f4d4-3d9d-d37254e18f8c@codeaurora.org> (raw)
In-Reply-To: <20180303192736.GA22510@kroah.com>
Thanks Greg,
I will check the common tree, and it seems to me a new bug , will file a
bug if won't be able to
resolve from android-common tree.
Regards
Gaurav
On 3/4/2018 12:57 AM, Greg Kroah-Hartman wrote:
> On Sat, Mar 03, 2018 at 08:22:35PM +0530, Kohli, Gaurav wrote:
>> HI ,
>>
>> Is there any known issue of slab poisoning in binder_transaction variable on kernel 4.9,
> If you are using binder in an Android device with 4.9, please use the
> version in the android-common tree, as it has all of the newer features
> backported properly there. You will need that for newer Android systems
> (like Android O and newer) anyway, so please try that tree. If you
> still have problems there, please file a bug in AOSP.
>
> thanks,
>
> greg k-h
--
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.
prev parent reply other threads:[~2018-03-05 11:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4d2b6014-ea76-b489-fdde-2e058e2fac4d@codeaurora.org>
2018-03-03 14:52 ` Query:Regarding object poison overwritten in binder_transaction Kohli, Gaurav
2018-03-03 19:27 ` Greg Kroah-Hartman
2018-03-05 11:39 ` Kohli, Gaurav [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=55a473e8-a2eb-f4d4-3d9d-d37254e18f8c@codeaurora.org \
--to=gkohli@codeaurora.org \
--cc=arve@android.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riandrews@android.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).