[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201204052334.EBI17103.OOFOSLFQJVHFtM@I-love.SAKURA.ne.jp>
Date: Thu, 5 Apr 2012 23:34:41 +0900
From: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To: levinsasha928@...il.com, garlick@...l.gov, ericvh@...il.com
Cc: oleg@...hat.com, eric.dumazet@...il.com, davem@...emloft.net,
kuznet@....inr.ac.ru, jmorris@...ei.org, yoshfuji@...ux-ipv6.org,
kaber@...sh.net, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, davej@...hat.com,
penguin-kernel@...ove.SAKURA.ne.jp
Subject: Re: ipv6: tunnel: hang when destroying ipv6 tunnel
Tetsuo Handa wrote:
> Good. -512 is -ERESTARTSYS, and this hang occurs after -ERESTARTSYS is
> returned. It indicates that c->trans_mod->request() is interrupted by signal.
> Since c->trans_mod->request is pointing at p9_virtio_request, the location
> returning that error would be
(...snipped...)
> 281 err = wait_event_interruptible(*chan->vc_wq,
> 282 chan->ring_bufs_avail);
>
> here.
Oops. Not p9_virtio_request().
It is p9_client_rpc(). I misread the output lines.
> > > + printk("%u:req->status = %u\n", current->pid, req->status);
> > > err = wait_event_interruptible(*req->wq,
> > > req->status >= REQ_STATUS_RCVD);
> > > + printk("%u:wait = %d\n", current->pid, err);
But anyway, I think this is interupt related bug.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists