linux-kernel - Re: [PATCH] driver/base: add BUS_NOTIFY_UNBOUND

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]

Date:	Fri, 24 Apr 2009 16:44:32 -0700
From:	Greg KH <gregkh@...e.de>
To:	Joerg Roedel <joro@...tes.org>
Cc:	Joerg Roedel <joerg.roedel@....com>,
	iommu@...ts.linux-foundation.org, Ingo Molnar <mingo@...hat.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] driver/base: add BUS_NOTIFY_UNBOUND_DRIVER event

On Sat, Apr 25, 2009 at 01:24:47AM +0200, Joerg Roedel wrote:
> On Fri, Apr 24, 2009 at 11:44:25AM -0700, Greg KH wrote:
> > On Fri, Apr 24, 2009 at 02:57:00PM +0200, Joerg Roedel wrote:
> > > This patch adds a new bus notifier event which is emitted _after_ a
> > > device is removed from its driver. This event will be used by the
> > > dma-api debug code to check if a driver has released all dma allocations
> > > for that device.
> > 
> > Heh, I was wondering if people were going to need that.  I'll queue it
> > up for 2.6.31, is that ok with you?  Do you have patches that depend on
> > it?
> 
> 2.6.31 is ok for me. I sent Ingo a patch to remove the broken feature
> which uses the wrong event for 2.6.30. I can reintroduce the fixed
> version for 2.6.31 too.
> Other way may be to send this patch to 2.6.30 which makes a smaller fix
> possible for dma-api debugging. But I am not sure if this new event
> could go in after the merge window. So I choosed this way :)
> For me, 2.6.31 for this patch is fine.

Great, it will go in for 2.6.31 then.

thanks,

greg k-h
--
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/