From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932088Ab3CUGal (ORCPT ); Thu, 21 Mar 2013 02:30:41 -0400 Received: from cantor2.suse.de ([195.135.220.15]:42625 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756515Ab3CUGak (ORCPT ); Thu, 21 Mar 2013 02:30:40 -0400 Date: Thu, 21 Mar 2013 07:30:38 +0100 Message-ID: From: Takashi Iwai To: Borislav Petkov Cc: Andrew Morton , Joern Engel , linux-kernel@vger.kernel.org, Jeff Moyer Subject: Re: [PATCH 0/9] Add blockconsole version 1.1 (try 2) In-Reply-To: <20130320225231.GG15471@pd.tnic> References: <1362087602-8979-1-git-send-email-joern@logfs.org> <20130320225231.GG15471@pd.tnic> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/24.2 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org At Wed, 20 Mar 2013 23:52:31 +0100, Borislav Petkov wrote: > > Hi Andrew, > > On Thu, Feb 28, 2013 at 04:39:53PM -0500, Joern Engel wrote: > > Blockconsole is a console driver very roughly similar to netconsole. > > Instead of sending messages out via UDP, they are written to a block > > device. Typically a USB stick is chosen, although in principle any > > block device will do. > > > > In most cases blockconsole is useful where netconsole is not, i.e. > > single machines without network access or without an accessable > > netconsole capture server. When using both blockconsole and > > netconsole, I have found netconsole to sometimes create a mess under > > high message load (sysrq-t, etc.) while blockconsole does not. > > > > Most importantly, a number of bugs were identified and fixed that > > would have been unexplained machine reboots without blockconsole. > > > > More highlights: > > * reasonably small and self-contained code, > > * some 100+ machine years of runtime, > > * nice tutorial with a 30-sec guide for the impatient. > > any thoughts on this? > > Blockconsole is very useful in certain situations and a bunch of people > are using it already and it would be nice if we could get it moving > towards upstream. > > So I'd appreciate it if you could take a look and maybe even pick it up > if there are no serious issues with it. FYI, blockconsole was already merged in linux-next tree. Takashi