From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936530AbcJTNDE (ORCPT ); Thu, 20 Oct 2016 09:03:04 -0400 Received: from mail-pf0-f195.google.com ([209.85.192.195]:32894 "EHLO mail-pf0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932543AbcJTNDD (ORCPT ); Thu, 20 Oct 2016 09:03:03 -0400 Date: Thu, 20 Oct 2016 22:02:02 +0900 From: Sergey Senozhatsky To: Peter Zijlstra Cc: Sergey Senozhatsky , Petr Mladek , Andrew Morton , Jan Kara , Tejun Heo , Calvin Owens , Thomas Gleixner , Mel Gorman , Steven Rostedt , Ingo Molnar , linux-kernel@vger.kernel.org, Jason Wessel Subject: Re: [PATCH 1/3] printk: Fix kdb_trap_printk placement Message-ID: <20161020130202.GA473@swordfish> References: <20161018170830.405990950@infradead.org> <20161018171513.585962054@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161018171513.585962054@infradead.org> User-Agent: Mutt/1.7.1 (2016-10-04) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (10/18/16 19:08), Peter Zijlstra wrote: > > Some people figured vprintk_emit() makes for a nice API and exported > it, bypassing the kdb trap. > > This still leaves vprintk_nmi() outside of the kbd reach, should that > be fixed too? > > Cc: Jason Wessel > Signed-off-by: Peter Zijlstra (Intel) looks good to me. Reviewed-by: Sergey Senozhatsky -ss