On 01/30/2017 11:47 AM, Vineeth Remanan Pillai wrote:Sorry, I got the ordering wrong. Thanks for the clarification..
If the timer is deleted in xennet_disconnect_backend() then why would2. It tickles a latent bug during resume where the timer triggersI think we may hit this bug after removing the timer as well. We call
before we re-connect. The trouble is that we now try to dereference
queue->rx.sring which is NULL since we disconnect in
netfront_resume(). (Curiously, I only observe it with 32-bit guests)
RING_PUSH_REQUESTS_AND_CHECK_NOTIFY soon after, which also dereference
anyone be pushing anything to the backend after that?