From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1758258AbdJMO7t (ORCPT <rfc822;w@1wt.eu>);
        Fri, 13 Oct 2017 10:59:49 -0400
Received: from mail-wm0-f42.google.com ([74.125.82.42]:55247 "EHLO
        mail-wm0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1753413AbdJMO7s (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 13 Oct 2017 10:59:48 -0400
X-Google-Smtp-Source: ABhQp+RqedGEuk+V0uBV6Tv0Dd3+FS0QzrAHbwC0dl8bQfRsr1iXZACpgNfBXw6deJ3Mqq5V71J5Fg==
Subject: Re: KGDB/KDB treats WARN*() as Oops on x86 since 4.12
To: Ilya Dryomov <idryomov@gmail.com>,
        Jason Wessel <jason.wessel@windriver.com>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
        Peter Zijlstra <peterz@infradead.org>, Ingo Molnar <mingo@kernel.org>,
        kgdb-bugreport@lists.sourceforge.net,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
References: <CAOi1vP-YRgSNZ82XrMK0H3M28ux+St91AdM3bWsW0fCzmK=FjQ@mail.gmail.com>
From: Daniel Thompson <daniel.thompson@linaro.org>
Message-ID: <7d12c8e1-0389-9982-9fd8-070dc0d26bef@linaro.org>
Date: Fri, 13 Oct 2017 15:59:44 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <CAOi1vP-YRgSNZ82XrMK0H3M28ux+St91AdM3bWsW0fCzmK=FjQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On 09/10/17 13:24, Ilya Dryomov wrote:
> Hi Jason,
> 
> Starting with 4.12, WARN*() is implemented with ud0, generating an
> Invalid Opcode exception.  KGDB/KDB gets entered as if it were an Oops,
> making KGDB/KDB rather hard to use, particularly on testing kernels.
> 
> Alexander posted a fix a while back, but Peter seems to be waiting for
> your ack.  Could you please weigh in?
> 
>    [PATCH] x86/debug: Handle warnings before the notifier chain
>    https://patchwork.kernel.org/patch/9859065/

Hmnnn... IIRC arm64 code has been also been blocked for a couple of 
releases whilst Will D. waited for an ack that never came.

My own reading of the code is that the patch in question restores the 
status quo, that there will still be mechanisms to provoke entry to 
kdb/kgdb during a warning (breakpoint on __warn, engage panic_on_warn, 
etc) and that these are not obviously recursive[1].

Put another way I'm happy to dig the patch out of my mail archive and 
throw in an Acked-By: but since I have no official role within kdb/kgdb 
(I'm just an interested bystander) it might not be enough for Peter.


Daniel.


[1] I'm not a huge x86 expert so correct me if I am wrong but I think
     its ok for us to trap here providing its for a different reason.