Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965342AbaKNLV5 (ORCPT ); Fri, 14 Nov 2014 06:21:57 -0500 Received: from mail-wi0-f170.google.com ([209.85.212.170]:60795 "EHLO mail-wi0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965011AbaKNLVx (ORCPT ); Fri, 14 Nov 2014 06:21:53 -0500 From: Daniel Thompson To: Steven Rostedt , Ingo Molnar Cc: Daniel Thompson , kgdb-bugreport@lists.sourceforge.net, linux-kernel@vger.kernel.org, Andrew Morton , patches@linaro.org, linaro-kernel@lists.linaro.org, John Stultz , Sumit Semwal Subject: [PATCH 3.18-rc3 v3 0/2] trace: kdb: Bug fixes for ftdump Date: Fri, 14 Nov 2014 11:21:21 +0000 Message-Id: <1415964083-10354-1-git-send-email-daniel.thompson@linaro.org> X-Mailer: git-send-email 1.9.3 In-Reply-To: <1415277716-19419-1-git-send-email-daniel.thompson@linaro.org> References: <1415277716-19419-1-git-send-email-daniel.thompson@linaro.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This patchset makes it possible to use kdb's ftdump command without panicing, crashing or livelocking. The ftdump command cannot be used at all without these changes. IIRC this patches are still pending Jason's ack. v3: * Remove lines leading with --- from the patch comments, now it it -~- cut here -~- and "git am" did the right thing when I checked (Steven Rostedt) v2: * Fixed use-after-free problems in v1 by adding logic to NULL out buffer_iter during free operations. * Introduced a second patch to fix a live lock when trying to display an empty trace buffer. Daniel Thompson (2): trace: kdb: Fix kernel panic during ftdump trace: kdb: Fix kernel livelock with empty buffers kernel/trace/trace_kdb.c | 21 +++++++++++++-------- 1 file changed, 13 insertions(+), 8 deletions(-) -- 1.9.3 -- 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/