Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752300AbZJZPhY (ORCPT ); Mon, 26 Oct 2009 11:37:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752043AbZJZPhX (ORCPT ); Mon, 26 Oct 2009 11:37:23 -0400 Received: from ernst.netinsight.se ([194.16.221.21]:58168 "HELO ernst.netinsight.se" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751916AbZJZPhW (ORCPT ); Mon, 26 Oct 2009 11:37:22 -0400 Date: Mon, 26 Oct 2009 16:37:19 +0100 From: Simon Kagstrom To: "Shargorodsky Atal (EXT-Teleca/Helsinki)" Cc: Linus Torvalds , Ingo Molnar , Artem Bityutskiy , linux-mtd , David Woodhouse , Andrew Morton , LKML , "Koskinen Aaro (Nokia-D/Helsinki)" , Alan Cox Subject: Re: [PATCH v11 4/5] core: Add kernel message dumper to call on oopses and panics Message-ID: <20091026163719.4ab82a4e@marrow.netinsight.se> In-Reply-To: <1256570007.5822.58.camel@atal-desktop> References: <20091015093133.GF10546@elte.hu> <20091015161052.0752208e@marrow.netinsight.se> <20091015154640.GA11408@elte.hu> <20091016094601.4e2c2d3e@marrow.netinsight.se> <20091016080935.GA3895@elte.hu> <1255681467.32489.360.camel@localhost> <20091016112556.6902b2dc@marrow.netinsight.se> <20091016101045.GA3263@elte.hu> <20091016140918.3981cfa2@marrow.netinsight.se> <1255952922.32489.505.camel@localhost> <20091019125017.GA9030@elte.hu> <20091022082500.602f9a7d@marrow.netinsight.se> <1256313202.5824.60.camel@atal-desktop> <20091026084158.0644ea85@marrow.netinsight.se> <1256553393.5822.24.camel@atal-desktop> <20091026125316.0283e322@marrow.netinsight.se> <1256570007.5822.58.camel@atal-desktop> X-Mailer: Claws Mail 3.7.3 (GTK+ 2.16.1; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1090 Lines: 26 On Mon, 26 Oct 2009 17:13:27 +0200 "Shargorodsky Atal (EXT-Teleca/Helsinki)" wrote: > How about adding KMSG_DUMP_LAST_OOPS_BEFORE_PANIC or something to the > kmsg_dump_reason enum, and making the kmsg_dump look like > kmsg_dump(panic_on_oops ? KMSG_DUMP_LAST_OOPS_BEFORE_PANIC : KMSG_DUMP_OOPS); > in oops_exit. Then let the dumpers decide what they want to do about it. > Just a thought. It would also have to take in_interrupt() in account since that will also lead to a panic. > And since you have no objections about moving notifiers up, it looks > like the second issue will be resolved, I believe Artem > will take care of it. :) Well, I have no objections to it, but I also know very little of the reasoning to put it there in the first place, so don't count my vote for very much here :-) // Simon -- 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/