memory corruption panic on FreeBSD11.0 with ena0 about amzn-drivers HOT 6 CLOSED

kyenduri@ Thanks your report.
Would it be possible to share your AMI with us? (AWS ID 890902708306 & 255982136585)

Also,we will be soon publishing new version 0.7, which should be fixing few stability issues.

from amzn-drivers.

Unfortunately, this AMI can not be shared. It is closest to the public FreeBSD AMI ami-0307a163. I will retry with version 0.7 once it is out.

from amzn-drivers.

kyenduri, is it possible for you to share the following files to assist us in reproducing the issue
/etc/hosts, /etc/pf.conf, /etc/pf.os?
If possible, feel free to send it to me by email

from amzn-drivers.

I got a fix for this. The driver is doing ena_free_counters() twice for rx_stats. I no longer see the panic with this patch (attached).
fix.txt

--- ./freebsd/sys/dev/ena/ena.c	2017-05-05 13:49:22.000000000 -0700
+++ ena.c	2017-05-11 18:10:44.000000000 -0700
@@ -879,10 +879,6 @@
 	ENA_MEM_FREE(adapter->ena_dev->dmadev, rx_ring->rx_buffer_info);
 	rx_ring->rx_buffer_info = NULL;
 
-	/* free counters... */
-	ena_free_counters((counter_u64_t *)&rx_ring->rx_stats,
-	    sizeof(rx_ring->rx_stats));
-
 	/* ... and destroy mutex. Voila! */
 	mtx_destroy(&rx_ring->ring_mtx);

from amzn-drivers.

thanks @kyenduri
we already fix the above issue in our latest code.
I will upload new version with the fix in few days

from amzn-drivers.

the issue fixed on f171fc9

from amzn-drivers.