From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Zijlstra Subject: Re: [rfc][patch] store-free path walking Date: Thu, 08 Oct 2009 20:00:45 +0200 Message-ID: <1255024846.26976.329.camel@twins> References: <20091006064919.GB30316@wotan.suse.de> <20091006101414.GM5216@kernel.dk> <20091006122623.GE30316@wotan.suse.de> <20091006124941.GS5216@kernel.dk> <20091007085849.GN30316@wotan.suse.de> <20091008123622.GA30316@wotan.suse.de> <20091008125746.GL9228@kernel.dk> <20091008132200.GB30316@wotan.suse.de> <20091008133003.GM9228@kernel.dk> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Nick Piggin , Linus Torvalds , Linux Kernel Mailing List , linux-fsdevel@vger.kernel.org, Ravikiran G Thirumalai To: Jens Axboe Return-path: In-Reply-To: <20091008133003.GM9228@kernel.dk> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, 2009-10-08 at 15:30 +0200, Jens Axboe wrote: > > IIRC, there was a bug with thread accounting very recently. Why would it > not hit -rc3 alone, though? Does look fishy, though. That was caused by: def0a9b2573e00ab0b486cb5382625203ab4c4a6 sched_clock: Make it NMI safe And was fixed by: 152f9d0710a62708710161bce1b29fa8292c8c11 sched_clock: Fix atomicity/continuity bug by using cmpxchg64() Which is in -rc3