netdev - Re: [PATCH] jme: Fix DMA unmap warning

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: <20140507215448.GA21071@localhost.localdomain>
Date:	Wed, 7 May 2014 17:54:48 -0400
From:	Neil Horman <nhorman@...driver.com>
To:	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org, cooldavid@...ldavid.org
Subject: Re: [PATCH] jme: Fix DMA unmap warning

On Wed, May 07, 2014 at 04:44:34PM -0400, David Miller wrote:
> From: Neil Horman <nhorman@...driver.com>
> Date: Wed, 7 May 2014 16:33:17 -0400
> 
> > Perhaps a solution is a signalling mechanism tied to completion interrupts?
> > I.e. a mapping failure gets reported to the stack, which causes the
> > correspondnig queue to be stopped, until such time a the driver signals a safe
> > restart by the reception of a tx completion interrupt?  I'm actually tinkering
> > right now with a mechanism that provides guidance to the stack as to how many
> > dma descriptors are available in a given net_device that might come in handy
> > here
> 
> Another idea is to signal it from the IOMMU unmap itself, since that is the
> point where the resource becomes available.
> 
> Actually either approach is fine with me.
> 
I'll look into it shortly.  Thanks for the idea!
Neil

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html