All of lore.kernel.org
 help / color / mirror / Atom feed
* [Intel-wired-lan] [PATCH 1/3] igb: Pull timestamp from fragment before adding it to skb
@ 2015-04-23 17:10 Cong Wang
  2015-04-23 18:19 ` Alexander Duyck
  0 siblings, 1 reply; 5+ messages in thread
From: Cong Wang @ 2015-04-23 17:10 UTC (permalink / raw)
  To: intel-wired-lan

On Wed, Apr 22, 2015 at 9:49 PM, Alexander Duyck
<alexander.h.duyck@redhat.com> wrote:
> This change makes it so that we pull the timestamp from the fragment before
> we add it to the skb.  By doing this we can avoid a possible issue in which
> the fragment can possibly be less than IGB_RX_HDR_LEN due to the timestamp
> being pulled after the copybreak check.


You said the first frag is always 2K if it exists. If this is not true, then
my patch is needed too.

>
> While making this change I realized we could also pull the rest of the
> igb_pull_tail function into igb_add_rx_frag since in the case of igb,
> unlike ixgbe, we are able to unmap the entire buffer before calling
> add_rx_frag so merging the two allows for sharing of code between the two
> merged functions.

Can you make a simple change for stable? Of course unless this
patch is targeted for net-next, but $subject doesn't say so.

Also, please Cc netdev, I am not on intel-wired-lan list.

BTW, it would be nice to Cc me for all 3 patches, as they might
be related for review.

^ permalink raw reply	[flat|nested] 5+ messages in thread
* [Intel-wired-lan] [PATCH 0/3] igb/fm10k/ixgbevf: Drop XXX_pull_tail and pull header in XXX_add_rx_frag
@ 2015-04-23  4:49 Alexander Duyck
  2015-04-23  4:49 ` [Intel-wired-lan] [PATCH 1/3] igb: Pull timestamp from fragment before adding it to skb Alexander Duyck
  0 siblings, 1 reply; 5+ messages in thread
From: Alexander Duyck @ 2015-04-23  4:49 UTC (permalink / raw)
  To: intel-wired-lan

These three patches remove the _pull_tail functions for the drivers igb,
fm10k, and ixgbevf in favor of simply pulling the header in all cases at
the start of _add_rx_frag.

For igb this might be considered a driver fix, but the issue would be a
corner case in which timestamping is enabled, a packet is received that is 
between 241 and 255 bytes in size, and the header contains bad data which 
places its size something greater than the actual size.

The ixgbe driver is excluded from this set as it cannot support this due to
RSC overwriting the header data until the EOP and DD bit are written in the
last descriptor.

---

Alexander Duyck (3):
      igb: Pull timestamp from fragment before adding it to skb
      fm10k: fold fm10k_pull_tail into fm10k_add_rx_frag
      ixgbevf: fold ixgbevf_pull_tail into ixgbevf_add_rx_frag


 drivers/net/ethernet/intel/fm10k/fm10k_main.c     |   66 ++++-----------
 drivers/net/ethernet/intel/igb/igb_main.c         |   94 ++++++---------------
 drivers/net/ethernet/intel/ixgbevf/ixgbevf_main.c |   66 ++++-----------
 3 files changed, 64 insertions(+), 162 deletions(-)

--

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2015-05-05 18:34 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-04-23 17:10 [Intel-wired-lan] [PATCH 1/3] igb: Pull timestamp from fragment before adding it to skb Cong Wang
2015-04-23 18:19 ` Alexander Duyck
2015-04-24  0:09   ` Cong Wang
  -- strict thread matches above, loose matches on Subject: below --
2015-04-23  4:49 [Intel-wired-lan] [PATCH 0/3] igb/fm10k/ixgbevf: Drop XXX_pull_tail and pull header in XXX_add_rx_frag Alexander Duyck
2015-04-23  4:49 ` [Intel-wired-lan] [PATCH 1/3] igb: Pull timestamp from fragment before adding it to skb Alexander Duyck
2015-05-05 18:34   ` Brown, Aaron F

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.