linux-kernel - Re: [PATCH 1/4] dma-debug: add variables and checks for driver filter

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090602082714.GK4062@amd.com>
Date:	Tue, 2 Jun 2009 10:27:15 +0200
From:	Joerg Roedel <joerg.roedel@....com>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/4] dma-debug: add variables and checks for driver
	filter

On Mon, Jun 01, 2009 at 02:55:02PM -0700, Andrew Morton wrote:
> On Thu, 28 May 2009 17:19:28 +0200
> Joerg Roedel <joerg.roedel@....com> wrote:
> 
> > This patch adds the state variables for the driver filter and a function
> > to check if the filter is enabled and matches to the current device. The
> > check is built into the err_printk function.
> > 
> 
> The path by which lib/dma-debug.c patches get into mainline seems to
> be largely random.  Is it a dwmw2 tree?  An Ingo tree?  A Joerg tree? -mm?

When I addresses your comment I will repost and send it to Ingo later
on. He will send it upstream. At least thats the current plan :-)

Joerg

-- 
           | Advanced Micro Devices GmbH
 Operating | Karl-Hammerschmidt-Str. 34, 85609 Dornach bei München
 System    | 
 Research  | Geschäftsführer: Thomas M. McCoy, Giuliano Meroni
 Center    | Sitz: Dornach, Gemeinde Aschheim, Landkreis München
           | Registergericht München, 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/