From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Gleixner Subject: Re: Process Hang in __read_seqcount_begin Date: Fri, 26 Oct 2012 23:54:28 +0200 (CEST) Message-ID: References: <1350925299.8609.978.camel@edumazet-glaptop> <1351053164.6537.95.camel@edumazet-glaptop> <1351270087.30380.9.camel@edumazet-glaptop> <1351285552.30380.20.camel@edumazet-glaptop> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Eric Dumazet , linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org, netfilter@vger.kernel.org To: Peter LaDow Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-rt-users.vger.kernel.org On Fri, 26 Oct 2012, Peter LaDow wrote: > On Fri, Oct 26, 2012 at 2:05 PM, Eric Dumazet wrote: > If this were safe, we wouldn't be seeing this lockup and your patch > wouldn't be needed. So it seems that your patch doesn't really > address the issue that we are not "sure a thread cannot be interrupted > by a softirq, and cannot migrate to another cpu". Well, we know it > cannot migrate to another CPU, because there isn't another CPU. So > apparently, it can be interrupted by a softirq. So local_bh_disable > isn't doing anything useful in the RT patches with regard to this. RT changes the semantics slightly. And yes it's not prepared for stuff which is relying on some of the magic mainline implicit semantics. Let me have a look at the whole scenario, once I'm more awake. Thanks, tglx