Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752611AbbBLRts (ORCPT ); Thu, 12 Feb 2015 12:49:48 -0500 Received: from mx1.redhat.com ([209.132.183.28]:39427 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752349AbbBLRtq (ORCPT ); Thu, 12 Feb 2015 12:49:46 -0500 Message-ID: <54DCE783.6080200@redhat.com> Date: Thu, 12 Feb 2015 12:48:51 -0500 From: Rik van Riel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Frederic Weisbecker CC: paulmck@linux.vnet.ibm.com, luto@amacapital.net, will.deacon@arm.com, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, mtosatti@redhat.com, borntraeger@de.ibm.com, lcapitulino@redhat.com, pbonzini@redhat.com Subject: Re: [PATCH -v5 6/5] context_tracking: fix exception_enter when already in IN_KERNEL References: <1423600074-2907-1-git-send-email-riel@redhat.com> <20150211144319.2a0c29d6@cuia.bos.redhat.com> <20150212154232.GE18363@lerouge> <54DCCAFE.7080206@redhat.com> <20150212170002.GH18363@lerouge> In-Reply-To: <20150212170002.GH18363@lerouge> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1837 Lines: 47 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/12/2015 12:00 PM, Frederic Weisbecker wrote: > On Thu, Feb 12, 2015 at 10:47:10AM -0500, Rik van Riel wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> On 02/12/2015 10:42 AM, Frederic Weisbecker wrote: >>> On Wed, Feb 11, 2015 at 02:43:19PM -0500, Rik van Riel wrote: >>>> If exception_enter happens when already in IN_KERNEL state, >>>> the code still calls context_tracking_exit, which ends up in >>>> rcu_eqs_exit_common, which explodes with a WARN_ON when it >>>> is called in a situation where dynticks are not enabled. >>> >>> Fortunately context_tracking_exit() already has a current_state >>> == IN_KERNEL check so this shouldn't be a problem. >> >> No, it had a hard-coded "current_state == IN_USER" check, which >> is very close, but ... >> >> ... I replaced that with a state argument, and forgot to ensure >> that it never gets called with state == IN_KERNEL. This patch >> fixes that. > > Ah that's right! Well I'm going to merge this patch to 1/5 then to > avoid breaking bisection. Thank you, Frederic! - -- All rights reversed -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJU3OeDAAoJEM553pKExN6D7BsIAJ8CKC73jQ8T5Dqa/tlHV7Db QFSJdpxP+7jCZwssehgpjpxCwtJ0UvGgle5OwX/POUhmagHxHmxVydOBz+xfYdBr UuGkEl5TL+oyoMUr80Q4RTnJSZN08zi+THqiv33tyPUj6cNiycBZAuho3ELTRNOA bRcHrMW+xd95uqoung7dSKrgA2jcym3+umNGnQb0gniraqcNLAmWs+jfAO8yZLJg vk8bIKed6epQ3n6gcdYe0A28cLOuBvjEs5JNcEPxujY/349sjitKR2pLQ6HsfHLV frlKsh7qQIRtoUJLO9ZBBDtGrmThwBwH8rw+GcVR8zviPNvV4IRrx47VBcHDWjc= =mwFO -----END PGP SIGNATURE----- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/