From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755322Ab0DALQn (ORCPT ); Thu, 1 Apr 2010 07:16:43 -0400 Received: from casper.infradead.org ([85.118.1.10]:48331 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755122Ab0DALQg (ORCPT ); Thu, 1 Apr 2010 07:16:36 -0400 Subject: Re: [COUNTERPATCH] mm: avoid overflowing preempt_count() in mmu_take_all_locks() From: Peter Zijlstra To: Avi Kivity Cc: Thomas Gleixner , Rik van Riel , linux-kernel@vger.kernel.org, aarcange@redhat.com, akpm@linux-foundation.org, Kent Overstreet , Ingo Molnar In-Reply-To: <4BB47FC3.1020606@redhat.com> References: <1270117906.1653.139.camel@laptop> <4BB47FC3.1020606@redhat.com> Content-Type: text/plain; charset="UTF-8" Date: Thu, 01 Apr 2010 13:16:32 +0200 Message-ID: <1270120592.1653.192.camel@laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.28.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2010-04-01 at 14:13 +0300, Avi Kivity wrote: > If someone is willing to audit all code paths to make sure these locks > are always taken in schedulable context I agree that's a better fix. They had better be, they're not irq-safe. Also that's what lockdep is for.