From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from out3-smtp.messagingengine.com ([66.111.4.27]:41683 "EHLO
        out3-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK)
        by vger.kernel.org with ESMTP id S1727425AbeI3WHF (ORCPT
        <rfc822;stable@vger.kernel.org>); Sun, 30 Sep 2018 18:07:05 -0400
Date: Sun, 30 Sep 2018 08:33:35 -0700
From: Greg KH <greg@kroah.com>
To: Greg Hackmann <ghackmann@google.com>
Cc: stable@vger.kernel.org
Subject: Re: Please apply 2c155709e4ef ("staging: android: ion: fix
 ION_IOC_{MAP,SHARE} use-after-free") to 3.18.y
Message-ID: <20180930153335.GC2942@kroah.com>
References: <85e4a24e-f4f5-5378-e347-1c62247e17b8@google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <85e4a24e-f4f5-5378-e347-1c62247e17b8@google.com>
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

On Thu, Sep 27, 2018 at 03:45:10PM -0700, Greg Hackmann wrote:
> 2c155709e4ef ("staging: android: ion: fix ION_IOC_{MAP,SHARE}
> use-after-free") was applied to 4.4.y a couple of weeks ago, and is needed
> on 3.18.y too.  The patch cherry-picks and builds as-is on top of 3.18.123.

I'm glad to apply this, but note, it breaks the build on any
qualcomm-based system as they seem to love to rely on the internals of
ion code.  So I don't know how you are going to resolve this when it
actually hits a real device's tree :(

thanks,

greg k-h