From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: rcu_sched self-detect stall when disable vif device Date: Tue, 27 Jan 2015 16:47:45 +0000 Message-ID: <54C7C131.9030502@linaro.org> References: <54C7B6E8.9080106@linaro.org> <20150127164539.GJ24026@zion.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20150127164539.GJ24026@zion.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Wei Liu Cc: Ian Campbell , xen-devel List-Id: xen-devel@lists.xenproject.org On 27/01/15 16:45, Wei Liu wrote: > On Tue, Jan 27, 2015 at 04:03:52PM +0000, Julien Grall wrote: >> Hi, >> >> While I'm working on support for 64K page in netfront, I got >> an rcu_sced self-detect message. It happens when netback is >> disabling the vif device due to an error. >> >> I'm using Linux 3.19-rc5 on seattle (ARM64). Any idea why >> the processor is stucked in xenvif_rx_queue_purge? >> > > When you try to release a SKB, core network driver need to enter some > RCU cirital region to clean up. dst_release for one, calls call_rcu. But this message shouldn't happen in normal condition or because of netfront. Right? Regards, -- Julien Grall