[PATCH v2 00/11] 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.

v2:
 * Added additional patches 5..11
 * Patches 1..4 rebased but unchanged

David Gibson (11):
  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: Correct type of PACKET_MAX_LEN
  packet: Avoid integer overflows in packet_get_do()
  packet: Move checks against PACKET_MAX_LEN to packet_check_range()
  packet: Rework packet_get() versus packet_get_try()
  util: Add abort_with_msg() and ASSERT_WITH_MSG() helpers
  packet: ASSERT on signs of pool corruption
  packet: Upgrade severity of most packet errors

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

-- 
2.48.1