From: Suman Anna <s-anna@ti.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Robin Murphy" <robin.murphy@arm.com>,
ivo.g.dimitrov.75@gmail.com, khilman@kernel.org,
"Tony Lindgren" <tony@atomide.com>,
aaro.koskinen@iki.fi,
"kernel list" <linux-kernel@vger.kernel.org>,
sre@kernel.org, martijn@brixit.nl,
"Filip Matijević" <filip.matijevic.pz@gmail.com>,
abcloriens@gmail.com, sakari.ailus@linux.intel.com,
pali.rohar@gmail.com, clayton@craftyguy.net,
linux-omap@vger.kernel.org, patrikbachan@gmail.com,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
serge@hallyn.com,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>
Subject: Re: Nokia N900: refcount_t underflow, use after free
Date: Thu, 24 May 2018 21:37:41 -0500 [thread overview]
Message-ID: <09e30e44-4904-3bb3-c977-19ccd8d76a08@ti.com> (raw)
In-Reply-To: <20180524110533.GA20599@amd>
On 05/24/2018 06:05 AM, Pavel Machek wrote:
> Hi!
>
>>>>
>>>> OK, see if the following fixes the issue for you, only build tested.
>>>
>>> Word-wrapped, so I applied by hand. And yes, the oops at boot is
>>> gone. Thanks!
>>
>> Sorry about that, have to check my mail settings. Anyway will post the
>> patch again, glad that it fixed your issue.
>
> Any news here? AFAICT the bug creeped into v4.17-rcX in the
> meantime...
>
The patch has been on linux-next for sometime now.
regards
Suman
> Pavel
>
>> regards
>> Suman
>>
>>>
>>> (Camera still does not work in -next... kills system. Oh well. Lets
>>> debug that some other day.)
>>>
>>>> 8< ---------------------
>>>> >From bac9a48fb646dc51f2030d676a0dbe3298c3b134 Mon Sep 17 00:00:00 2001
>>>> From: Suman Anna <s-anna@ti.com>
>>>> Date: Fri, 9 Mar 2018 16:39:59 -0600
>>>> Subject: [PATCH] media: omap3isp: fix unbalanced dma_iommu_mapping
>>>>
>>>> The OMAP3 ISP driver manages its MMU mappings through the IOMMU-aware
>>>> ARM DMA backend. The current code creates a dma_iommu_mapping and
>>>> attaches this to the ISP device, but never detaches the mapping in
>>>> either the probe failure paths or the driver remove path resulting
>>>> in an unbalanced mapping refcount and a memory leak. Fix this properly.
>>>>
>>>> Reported-by: Pavel Machek <pavel@ucw.cz>
>>>> Signed-off-by: Suman Anna <s-anna@ti.com>
>>>
>>> Tested-by: Pavel Machek <pavel@ucw.cz>
>>> Pavel
>>>
>
prev parent reply other threads:[~2018-05-25 2:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 14:30 Nokia N900: refcount_t underflow, use after free Pavel Machek
2018-03-08 16:59 ` Tony Lindgren
2018-03-08 18:21 ` Suman Anna
2018-03-08 18:50 ` Pavel Machek
2018-03-09 12:08 ` Robin Murphy
2018-03-09 22:13 ` Suman Anna
2018-03-09 22:18 ` Pavel Machek
2018-03-09 23:06 ` Suman Anna
2018-03-10 11:26 ` Pavel Machek
2018-03-12 16:10 ` Suman Anna
2018-05-24 11:05 ` Pavel Machek
2018-05-25 2:37 ` Suman Anna [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=09e30e44-4904-3bb3-c977-19ccd8d76a08@ti.com \
--to=s-anna@ti.com \
--cc=aaro.koskinen@iki.fi \
--cc=abcloriens@gmail.com \
--cc=clayton@craftyguy.net \
--cc=filip.matijevic.pz@gmail.com \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=khilman@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=martijn@brixit.nl \
--cc=pali.rohar@gmail.com \
--cc=patrikbachan@gmail.com \
--cc=pavel@ucw.cz \
--cc=robin.murphy@arm.com \
--cc=sakari.ailus@linux.intel.com \
--cc=serge@hallyn.com \
--cc=sre@kernel.org \
--cc=tony@atomide.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