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: <AANLkTimJm-Fd0siuuOKgmHWq2L7h0LB=wZ-6E_ZuK=wK@mail.gmail.com>
Date:	Tue, 22 Mar 2011 15:27:30 +0100
From:	Florian Mickler <florian@...kler.org>
To:	"Roedel, Joerg" <Joerg.Roedel@....com>
Cc:	Andy Walls <awalls@...metrocast.net>,
	"mchehab@...radead.org" <mchehab@...radead.org>,
	"linux-media@...r.kernel.org" <linux-media@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"js@...uxtv.org" <js@...uxtv.org>,
	"tskd2@...oo.co.jp" <tskd2@...oo.co.jp>,
	"liplianin@...by" <liplianin@...by>,
	"g.marco@...enet.de" <g.marco@...enet.de>,
	"aet@...terburn.org" <aet@...terburn.org>,
	"pb@...uxtv.org" <pb@...uxtv.org>,
	"mkrufky@...uxtv.org" <mkrufky@...uxtv.org>,
	"nick@...k-andrew.net" <nick@...k-andrew.net>,
	"max@...eto.com" <max@...eto.com>,
	"janne-dvb@...nau.be" <janne-dvb@...nau.be>,
	Oliver Neukum <oliver@...kum.org>,
	Greg Kroah-Hartman <greg@...ah.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	James Bottomley <James.Bottomley@...senpartnership.com>
Subject: Re: [PATCH 0/6] get rid of on-stack dma buffers

2011/3/22 Roedel, Joerg <Joerg.Roedel@....com>:
> On Mon, Mar 21, 2011 at 05:03:15PM -0400, Florian Mickler wrote:
>> I guess (not verified), that the dma api takes sufficient precautions
>> to abort the dma transfer if a timeout happens.  So freeing _should_
>> not be an issue. (At least, I would expect big fat warnings everywhere
>> if that were the case)
>
> Freeing is very well an issue. All you can expect from the DMA-API is to
> give you a valid DMA handle for your device. But it can not prevent that
> a device uses this handle after you returned it. You need to make sure
> yourself that any pending DMA is canceled before calling kfree().

sorry, I meant usb_control_msg above when I said 'dma api'... as that
is the function these
drivers use to do the dma.

Regards,
Flo
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ