From: Luis Henriques <luis.henriques@canonical.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: David Miller <davem@davemloft.net>,
stable <stable@vger.kernel.org>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] sfc: Fix efx_rx_buf_offset() for recycled pages
Date: Mon, 30 Sep 2013 17:48:27 +0100 [thread overview]
Message-ID: <87zjqu1cis.fsf@canonical.com> (raw)
In-Reply-To: <1379607231.1514.13.camel@bwh-desktop.uk.level5networks.com> (Ben Hutchings's message of "Thu, 19 Sep 2013 17:13:51 +0100")
Ben Hutchings <bhutchings@solarflare.com> writes:
> [Re-sending with cc to the current stable address. I still had the old
> address in contacts, though I've definitely sent to the current address
> previously...]
>
> This bug fix is only for stable branches older than 3.10. The bug was
> fixed upstream by commit 2768935a4660 ('sfc: reuse pages to avoid DMA
> mapping/unmapping costs'), but that change is totally unsuitable for
> stable.
>
> Commit b590ace09d51 ('sfc: Fix efx_rx_buf_offset() in the presence of
> swiotlb') added an explicit page_offset member to struct
> efx_rx_buffer, which must be set consistently with the u.page and
> dma_addr fields. However, it failed to add the necessary assignment
> in efx_resurrect_rx_buffer(). It also did not correct the calculation
> of efx_rx_buffer::dma_addr in efx_resurrect_rx_buffer(), which assumes
> that DMA-mapping a page will result in a page-aligned DMA address
> (exactly what swiotlb violates).
>
> Add the assignment of efx_rx_buffer::page_offset and change the
> calculation of dma_addr to make use of it.
>
> I'm attaching the patches for 3.0.y, 3.2.y and 3.4.y (the last of which
> should also be applicable to the later unofficial stable branches).
>
> Ben.
Thanks Ben. I'm queuing it for the 3.5 kernel.
Cheers,
--
Luis
next prev parent reply other threads:[~2013-09-30 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 16:13 [stable] [PATCH] sfc: Fix efx_rx_buf_offset() for recycled pages Ben Hutchings
2013-09-19 17:43 ` David Miller
2013-09-30 16:48 ` Luis Henriques [this message]
2013-10-20 12:52 ` Ben Hutchings
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zjqu1cis.fsf@canonical.com \
--to=luis.henriques@canonical.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).