The virtnet_transmit() logic for waiting the packet to be transmitted is reversed: we can't wait the packet to be transmitted if we didn't kick() the ring yet. The vring_more_used() while loop logic is reversed also, that explains why the code works today. The current code risks trying to free a buffer from the used ring when none was available, that will happen most times because KVM doesn't handle the packet immediately on kick(). Luckily it was working because it was unlikely to have a buffer still queued for transmit when virtnet_transmit() was called. Also, adds a BUG_ON() to vring_get_buf(), to catch cases where we try to free a buffer from the used ring when there was none available. Patch for Etherboot. gPXE has the same problem on the code, but I hadn't a chance to test gPXE using virtio-net yet. Signed-off-by: Eduardo Habkost <ehabkost@redhat.com> Signed-off-by: Stefan Hajnoczi <stefanha@gmail.com>tags/v0.9.6
|
|
||
187 |
|
187 |
|
188 |
|
188 |
|
189 |
|
189 |
|
|
190 |
|
|
|
191 |
|
|
190 |
|
192 |
|
191 |
|
193 |
|
192 |
|
194 |
|
|
|
||
365 |
|
367 |
|
366 |
|
368 |
|
367 |
|
369 |
|
|
370 |
|
|
|
371 |
|
|
368 |
|
372 |
|
369 |
|
373 |
|
370 |
|
374 |
|
|
|
||
372 |
|
376 |
|
373 |
|
377 |
|
374 |
|
378 |
|
375 |
|
|
|
|
379 |
|
|
376 |
|
380 |
|
377 |
|
381 |
|
378 |
|
382 |
|
379 |
|
383 |
|
380 |
|
|
|
381 |
|
|
|
382 |
|
384 |
|
383 |
|
385 |
|
384 |
|
386 |
|