Bug ID 435855: Possible panic when a cloned packet from an IP fragment fails to transmit

Last Modified: Feb 13, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1

Fixed In:
11.5.0, 11.4.1 HF6

Opened: Oct 29, 2013
Severity: 3-Major
Related AskF5 Article:
K14981

Symptoms

You may experience a TMM panic if a packet is cloned from a packet with an IP fragment and TMM fails to transmit the cloned packet. The following is present in the TMM log: <13> Oct 15 11:37:16 f5-5a notice panic: ../net/packet.c:136: Assertion "packet is not locked by a driver" failed.

Impact

TMM will panic and restart. This will repeat any times this condition occurs.

Conditions

This happens when using a clone pool. If a packet is received that needs to be cloned, originates from an IP fragment, and fails to transmit, then this condition can occur.

Workaround

None.

Fix Information

When a packet is cloned, the original packet flags were preserved. If the original packet was locked, then this flag was propagated to the cloned packet. The fix is to clear this flag in the cloned packet when it is created.

Behavior Change