This fixes the crash, thanks.
One doubt though: suppose that while we drop the lock the skb gets aggregated
with the one after it. If the original skb is fully consumed in the receive
actor, then the we will eat the new, aggregated skb, loosing data.
Here is a patch, based on your idea, which tries to cope with the above
scenario. The !skb check was added for the case in which the actor does not
consume anything in the current interration.
tavi