linux-kernel - Re: put_page on transparent huge page leaks?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <3104bf891faf02691e4f2e0de44a59a9@jcornwall.me>
Date:	Sat, 22 Feb 2014 13:31:19 -0600
From:	Jay Cornwall <jay@...rnwall.me>
To:	"Kirill A. Shutemov" <kirill@...temov.name>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: put_page on transparent huge page leaks?

On 2014-02-22 11:44, Jay Cornwall wrote:
> On 2014-02-21 20:31, Kirill A. Shutemov wrote:
>> On Fri, Feb 21, 2014 at 11:23:39AM -0600, Jay Cornwall wrote:
>>> I'm tracking a possible memory leak in iommu/amd. The driver uses 
>>> this logic
>>> to fault a page in response to a PRI from a device:
> 
> The head page appears to be leaking a reference. There is *no leak* if
> the driver faults the head page directly.

My apologies, this was fixed somewhere in the patch series: "mm: tail 
page refcounting optimization for slab and hugetlbfs" (Jan 22nd).

Our merge was slightly older than I'd thought.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/