[PATCH 0/4] Improve robustness of calculations related to frame size limits

[David Gibson <david@gibson.dropbear.id.au>]

There are a number of places where we make calculations and checks
around how large frames can be and where they sit in memory.  Several
of these are roughly correct, but can be wrong in certain edge cases.
Improve robustness by clarifying what we're doing and being more
careful about the edge cases.

David Gibson (4):
  vu_common: Tighten vu_packet_check_range()
  packet: More cautious checks to avoid pointer arithmetic UB
  tap: Make size of pool_tap[46] purely a tuning parameter
  tap: Clarify calculation of TAP_MSGS

 packet.c    | 25 +++++++++++++++++++++----
 packet.h    |  3 +++
 passt.h     |  2 --
 tap.c       | 43 ++++++++++++++++++++++++++++++++++++-------
 tap.h       |  3 ++-
 vu_common.c | 15 ++++++++++-----
 6 files changed, 72 insertions(+), 19 deletions(-)

-- 
2.48.1