From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755105Ab2GWXk3 (ORCPT ); Mon, 23 Jul 2012 19:40:29 -0400 Received: from mail-pb0-f46.google.com ([209.85.160.46]:61248 "EHLO mail-pb0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754966Ab2GWXk2 (ORCPT ); Mon, 23 Jul 2012 19:40:28 -0400 Date: Mon, 23 Jul 2012 16:38:20 -0700 From: Anton Vorontsov To: Andrew Morton Cc: Linus Torvalds , Kay Sievers , Jason Wessel , Greg Kroah-Hartman , linux-kernel@vger.kernel.org, kgdb-bugreport@lists.sourceforge.net, stable@vger.kernel.org Subject: Re: [PATCH for-3.5 1/4] kdb: Revive dmesg command Message-ID: <20120723233819.GA6711@lizard> References: <20120721002529.GA20567@lizard> <20120721002737.GA2213@lizard> <20120723161927.9af62e29.akpm@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20120723161927.9af62e29.akpm@linux-foundation.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jul 23, 2012 at 04:19:27PM -0700, Andrew Morton wrote: > > dmesg command appears to be broken after the printk rework. The old logic > > in kdb code makes no sense in terms of current printk/logging storage > > format, and KDB simply hangs forever. > > > > This patch revives the command by switching to kmsg_dumper iterator. > > > > The code is now much more simpler and shorter. > > > > Signed-off-by: Anton Vorontsov > > This one should me merged into 3.5.1 methinks. Note that it has been > merged into mainline without a -stable tag. Thanks to Linus, it made it into v3.5 release, so I believe there is no need for -stable. Cheers, -- Anton Vorontsov Email: cbouatmailru@gmail.com