From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760010Ab3B0QOL (ORCPT ); Wed, 27 Feb 2013 11:14:11 -0500 Received: from mail-we0-f169.google.com ([74.125.82.169]:63687 "EHLO mail-we0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757421Ab3B0QOG (ORCPT ); Wed, 27 Feb 2013 11:14:06 -0500 MIME-Version: 1.0 Reply-To: sedat.dilek@gmail.com In-Reply-To: <20130227160833.GF5530@pd.tnic> References: <20130227122302.GA5678@pd.tnic> <20130227150733.GB22383@htj.dyndns.org> <20130227160833.GF5530@pd.tnic> Date: Wed, 27 Feb 2013 17:14:04 +0100 Message-ID: Subject: Re: [next-20130227] kernel NULL pointer dereference [ watchdog | perf related ? ] From: Sedat Dilek To: Borislav Petkov , Sedat Dilek , Tejun Heo , Wim Van Sebroeck , Ingo Molnar , Steven Rostedt , linux-watchdog@vger.kernel.org, x86@kernel.org, LKML , linux-next , Stephen Rothwell , Andrew Morton Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 27, 2013 at 5:08 PM, Borislav Petkov wrote: > On Wed, Feb 27, 2013 at 04:56:27PM +0100, Sedat Dilek wrote: >> Hmm, I am not very amused to read all this, really. >> >> If such fixes are around why aren't they applied quickly? > > Sedat, you need to relax a little. You're testing a linux next tree > right during the merge window where patches are flying back and forth. > Things like that can happen and you, if you're really willing to test > such bleeding edge kernels, also would have to accept the fact that > fixes don't magically appear where they have to in no time. > > I debugged an issue which apparently got fixed already but I'm not > complaining. People are trying their best and screaming at them is not > constructive. At all. > I am not screaming or whining... people should reflect a bit on the patch workflow process? Also, I am sure a patchwork-service especially for -next is helpful. /me forgot to add a "call trace" to my 1st kernel checks. $ dmesg | egrep -i 'error|fail|warn|conflict|terminated|killed|call trace' That's why I have overseen it. > I'd suggest simply reporting the issue, maybe trying to debug it > yourself and patiently waiting. I'm sure you can find anything else to > do in the meantime :-) > Yupp, I had a coffee and two pieces of cake :-). > Thanks. > > -- > Regards/Gruss, > Boris. > > Sent from a fat crate under my desk. Formatting is fine. > --