PSOD in vmk_PktFrameLenSet

kamalpr — Mon, 29 Aug 2022 10:49:07 GMT

Hello,

I got a PSOD when i called vmware's api function vmk_PktFrameLenSet() inside my nic driver. The arguments to the function were:-

vmk_PktFrameLenSet(0x45ba60dfa3c0, 68)

The first parameter is not NULL and valid, and the length is also valid. The same function was called several times with the same argument when receiving packets in an isr. so, it is not a functional problem or a problem of passing bad arguments according to me.

The relevant stack trace for vmware is given below.. Can someone tell me if it is a problem from vmware's side:-

#GP Exception 13 in world 2097959:vmnic2-pollW @ 0x42000ba749ec
2022-08-29T13:56:44.746Z cpu12:2097959)cr0=0x8001003d cr2=0xa58d7a3460 cr3=0x800fb000 cr4=0x216c
2022-08-29T13:56:44.762Z cpu12:2097959)FMS=06/2c/2 uCode=0x1f
2022-08-29T13:56:44.775Z cpu12:2097959)frame=0x451a1171bc20 ip=0x42000ba749ec err=0 rflags=0x10206
2022-08-29T13:56:44.793Z cpu12:2097959)rax=0x4b4a494847464544 rbx=0x44 rcx=0x8
2022-08-29T13:56:44.806Z cpu12:2097959)rdx=0x1 rbp=0x0 rsi=0x44
2022-08-29T13:56:44.817Z cpu12:2097959)rdi=0x45ba60dfa3c0 r8=0x5b92a4 r9=0x1
2022-08-29T13:56:44.831Z cpu12:2097959)r10=0x0 r11=0x0 r12=0x45ba60dfa3c0
2022-08-29T13:56:44.844Z cpu12:2097959)r13=0x1000 r14=0x0 r15=0x431759f87300
2022-08-29T13:56:44.863Z cpu12:2097959)pcpu:0 world:2097984 name:"vmnic7-pollWorld-0-0x43004fa3b9c0" (S)
2022-08-29T13:56:44.874Z cpu12:2097959)pcpu:1 world:2104458 name:"vmkping" (U)
2022-08-29T13:56:44.881Z cpu12:2097959)pcpu:2 world:2097348 name:"itRebalance" (S)
2022-08-29T13:56:44.888Z cpu12:2097959)pcpu:3 world:2097155 name:"idle3" (IS)
2022-08-29T13:56:44.895Z cpu12:2097959)pcpu:4 world:2104485 name:"vmkping" (U)
2022-08-29T13:56:44.902Z cpu12:2097959)pcpu:5 world:2102574 name:"Tcpip4 wtask" (S)
2022-08-29T13:56:44.910Z cpu12:2097959)pcpu:6 world:2097551 name:"logterm" (S)
2022-08-29T13:56:44.917Z cpu12:2097959)pcpu:7 world:2097181 name:"serialLogger" (S)
2022-08-29T13:56:44.924Z cpu12:2097959)pcpu:8 world:2102579 name:"Tcpip4 wtask" (S)
2022-08-29T13:56:44.932Z cpu12:2097959)pcpu:9 world:2097947 name:"vmnic1-pollWorld-0-0x43004fa22e80" (S)
2022-08-29T13:56:44.941Z cpu12:2097959)pcpu:10 world:2097972 name:"vmnic6-pollWorld-0-0x43004fa335c0" (S)
2022-08-29T13:56:44.951Z cpu12:2097959)pcpu:11 world:2097625 name:"vmsyslogd" (U)
2022-08-29T13:56:44.958Z cpu12:2097959)pcpu:12 world:2097959 name:"vmnic2-pollWorld-0-0x43004fa2b1c0" (S)
2022-08-29T13:56:44.967Z cpu12:2097959)pcpu:13 world:2099766 name:"hostd-worker" (U)
2022-08-29T13:56:44.975Z cpu12:2097959)pcpu:14 world:2102839 name:"vmk8-rx-0" (S)
2022-08-29T13:56:44.982Z cpu12:2097959)pcpu:15 world:2102664 name:"Tcpip4 wtask" (S)
2022-08-29T13:56:44.990Z cpu12:2097959)pcpu:16 world:2097340 name:"retireWld.0016" (S)
2022-08-29T13:56:44.997Z cpu12:2097959)pcpu:17 world:2099768 name:"hostd-IO" (U)
2022-08-29T13:56:45.005Z cpu12:2097959)pcpu:18 world:2098273 name:"net-lacp" (U)
2022-08-29T13:56:45.012Z cpu12:2097959)pcpu:19 world:2097481 name:"VSCSIPoll" (S)
2022-08-29T13:56:45.019Z cpu12:2097959)pcpu:20 world:2102595 name:"vmk2-rx-0" (S)
2022-08-29T13:56:45.026Z cpu12:2097959)pcpu:21 world:2097627 name:"vmsyslogd" (U)
2022-08-29T13:56:45.034Z cpu12:2097959)pcpu:22 world:2097174 name:"idle22" (IS)
2022-08-29T13:56:45.041Z cpu12:2097959)pcpu:23 world:2102673 name:"vmk4-rx-0" (S)
2022-08-29T13:56:45.048Z cpu12:2097959)@BlueScreen: #GP Exception 13 in world 2097959:vmnic2-pollW @ 0x42000ba749ec
2022-08-29T13:56:45.064Z cpu12:2097959)Code start: 0x42000b800000 VMK uptime: 0:00:25:35.012
2022-08-29T13:56:45.085Z cpu12:2097959)0x451a1171bce8:[0x42000b

a749ec]vmk_PktFrameLenSet@vmkernel#nover+0x4 stack: 0x42000c35c7ab

topic PSOD in vmk_PktFrameLenSet in VMware {code} Members

PSOD in vmk_PktFrameLenSet