diff options
| author | Chuck Lever | 2018-12-19 10:58:13 -0500 |
|---|---|---|
| committer | Anna Schumaker | 2019-01-02 12:05:16 -0500 |
| commit | e2f34e26710bfaa545a9d9cd0c70137406401467 (patch) | |
| tree | d888bf12d1ce95d407bbd2511a73d2c326b26ef8 /net/mac802154 | |
| parent | 594d1644cd59447f4fceb592448d5cd09eb09b5e (diff) | |
xprtrdma: Yet another double DMA-unmap
While chasing yet another set of DMAR fault reports, I noticed that
the frwr recycler conflates whether or not an MR has been DMA
unmapped with frwr->fr_state. Actually the two have only an indirect
relationship. It's in fact impossible to guess reliably whether the
MR has been DMA unmapped based on its fr_state field, especially as
the surrounding code and its assumptions have changed over time.
A better approach is to track the DMA mapping status explicitly so
that the recycler is less brittle to unexpected situations, and
attempts to DMA-unmap a second time are prevented.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Cc: stable@vger.kernel.org # v4.20
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
Diffstat (limited to 'net/mac802154')
0 files changed, 0 insertions, 0 deletions