From: Eric Dumazet <edumazet@google.com>
+commit 06669ea346e476a5339033d77ef175566a40efbb upstream.
+
Locking newsk while still holding the listener lock triggered
a lockdep splat [1]
From: Eric Dumazet <edumazet@google.com>
+commit 06669ea346e476a5339033d77ef175566a40efbb upstream.
+
Locking newsk while still holding the listener lock triggered
a lockdep splat [1]
From: Eric Dumazet <edumazet@google.com>
+commit 06669ea346e476a5339033d77ef175566a40efbb upstream.
+
Locking newsk while still holding the listener lock triggered
a lockdep splat [1]
From: Madalin Bucur <madalin.bucur@nxp.com>
+commit b54d3900862374e1bb2846e6b39d79c896c0b200 upstream.
+
The LS1043A SoC is affected by the A050385 erratum stating that
FMAN DMA read or writes under heavy traffic load may cause FMAN
internal resource leak thus stopping further packet processing.
From: Madalin Bucur <madalin.bucur@nxp.com>
+commit 3c68b8fffb48c0018c24e73c48f2bac768c6203e upstream.
+
Align buffers, data start, SG fragment length to avoid DMA splits.
These changes prevent the A050385 erratum to manifest itself:
From: Madalin Bucur <madalin.bucur@nxp.com>
+commit 26d5bb9e4c4b541c475751e015072eb2cbf70d15 upstream.
+
FMAN DMA read or writes under heavy traffic load may cause FMAN
internal resource leak; thus stopping further packet processing.
From: Madalin Bucur <madalin.bucur@nxp.com>
+commit b281f7b93b258ce1419043bbd898a29254d5c9c7 upstream.
+
Detect the presence of the A050385 erratum.
Signed-off-by: Madalin Bucur <madalin.bucur@nxp.com>
From: Eric Dumazet <edumazet@google.com>
+commit 06669ea346e476a5339033d77ef175566a40efbb upstream.
+
Locking newsk while still holding the listener lock triggered
a lockdep splat [1]