summaryrefslogtreecommitdiffstats
path: root/scripts/const_structs.checkpatch
diff options
context:
space:
mode:
authorSushil Singh <sushilkumars@nvidia.com>2021-09-29 11:02:31 -0400
committermobile promotions <svcmobile_promotions@nvidia.com>2021-10-15 19:54:31 -0400
commit85696c17b91a5e30a621ffa3ed71623559f46ab9 (patch)
treec7dfa52f3ce390aa9e703efba649187aca3342d6 /scripts/const_structs.checkpatch
parent916bb90add1c9a589b70d80d6c409e8caddce673 (diff)
rel-32:eqos Drop Rx pkt if MTU and pkt len differs
Issue: The len of buffers allocated is based on the MTU configured at the DUT. In case a Rx packet received is more than the MTU configured, then the packet appears in the ring with LD bit set which further gets processed even if the buffers length allocated is less than the received packet len. The frame hence consumes more than 1 rx desc and kfree for an skb with no LD bit set and neither error bits set got called causing kernel panic. Fix: Drops such pkts for which the configured MTU and received pkt len is different to avoid packects consuming more than 1 rx desc, and always accommodate single packet in single rx desc buffer. Bug 200712686 Change-Id: I798185ff584507fc31906c0977d3c53e447ae48f Signed-off-by: Sushil Singh <sushilkumars@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvidia/+/2602767 Reviewed-by: svcacv <svcacv@nvidia.com> Reviewed-by: Bhadram Varka <vbhadram@nvidia.com> Reviewed-by: Srinivas Ramachandran <srinivasra@nvidia.com> Reviewed-by: mobile promotions <svcmobile_promotions@nvidia.com> Tested-by: mobile promotions <svcmobile_promotions@nvidia.com> GVS: Gerrit_Virtual_Submit
Diffstat (limited to 'scripts/const_structs.checkpatch')
0 files changed, 0 insertions, 0 deletions