linux-kernel - Re: [PATCH 0/4] dmaengine redux continued

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]

Date:	Thu, 4 Dec 2008 11:52:28 -0700
From:	"Dan Williams" <dan.j.williams@...el.com>
To:	"Guennadi Liakhovetski" <g.liakhovetski@....de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] dmaengine redux continued

On Thu, Dec 4, 2008 at 1:51 AM, Guennadi Liakhovetski
<g.liakhovetski@....de> wrote:
> What about the last hunk from the patch at
>
> http://marc.info/?l=linux-arm-kernel&m=122607472721145&w=2
>
> ? Can we add this tx_free pointer? Would you like me to submit it as a
> separate patch? I'd like to be able to reuse tx-descriptors in clients, so
> I then have to explicitly release them in the dmaengine device
> (controller) driver.
>

I took a look but the description does not explain why the driver
needs an explicit release.  In what cases is the implied release, when
the descriptor is acked && done, insufficient?
--
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/