linux-kernel - Re: [PATCH v3] dma-debug: print some unfreed allocations

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20110608123758.GB21591@amd.com>
Date:	Wed, 8 Jun 2011 14:37:58 +0200
From:	"Roedel, Joerg" <Joerg.Roedel@....com>
To:	Johannes Berg <johannes@...solutions.net>
CC:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3] dma-debug: print some unfreed allocations

On Wed, Jun 08, 2011 at 08:26:47AM -0400, Johannes Berg wrote:
> On Wed, 2011-06-08 at 14:16 +0200, Roedel, Joerg wrote:
> 
> > > I see something similar was merged printing just the first one (and
> > > without stack trace it seems?). Are you still interested in this?
> > 
> > Sure, still interested. The code which prints out the first entry has
> > been around for some time, its nothing new afaik.
> 
> Ok. I was thinking of 
> commit ba4b87ad5497cba555954885db99c99627f93748
> Author: Stanislaw Gruszka <sgruszka@...hat.com>
> Date:   Thu Mar 31 08:08:09 2011 -0400
> 
>     dma-debug: print information about leaked entry
> 
> which is fairly recent, recent enough that my original patch no longer
> applied anyway :-)

Ah, okay. I thought this change was older :-)

	Joerg

-- 
AMD Operating System Research Center

Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632

--
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/