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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 8 Jun 2011 14:16:08 +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 07:03:36AM -0400, Johannes Berg wrote:
> On Mon, 2011-05-23 at 14:35 +0200, Roedel, Joerg wrote:
> 
> > > +#ifdef CONFIG_STACKTRACE
> > > +	num_show_pending_dent = debugfs_create_u32("num_show_pending", 0644,
> > > +						   dma_debug_dent,
> > > +						   &num_show_pending);
> > > +	if (!num_show_pending_dent)
> > > +		goto out_err;
> > > +#endif
> > 
> > Hmm, thinking more about this, do we need to introduce a new variable at
> > all? It should fit well into the dma-api/all_errors and
> > dma-api/num_errors configurables. 
> 
> 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.

	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/