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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20140507.155613.630399521517455317.davem@davemloft.net>
Date:	Wed, 07 May 2014 15:56:13 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	nhorman@...driver.com
Cc:	netdev@...r.kernel.org, cooldavid@...ldavid.org
Subject: Re: [PATCH] jme: Fix DMA unmap warning

From: Neil Horman <nhorman@...driver.com>
Date: Mon,  5 May 2014 14:51:47 -0400

> The jme driver forgot to check the return status from pci_map_page in its tx
> path, causing a dma api warning on unmap.  Easy fix, just do the check and
> augment the tx path to tell the stack that the driver is busy so we re-queue the
> frame.
> 
> Signed-off-by: Neil Horman <nhorman@...driver.com>

Applied thanks Neil.

Probably we should eventually come up with a perhaps more suitable recovery
scheme in the generic netdev queuing layer for these situations.

If a mapping fails, usually it's because of resource exhaustion and that's
a "wait and try again" type situation in hoping that whatever releases
are keeping the allocation from happening will get released.

But that's not exactly what we do right now when NETDEV_TX_BUSY is
signalled.  We'll just loop over and over in the TX software interrupt
handler for the qdisc.

Perhaps an hrtimer or similar would be more appropriate.
--
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