From mboxrd@z Thu Jan 1 00:00:00 1970 From: Borislav Petkov Subject: Re: [next-20130227] kernel NULL pointer dereference [ watchdog | perf related ? ] Date: Wed, 27 Feb 2013 17:08:33 +0100 Message-ID: <20130227160833.GF5530@pd.tnic> References: <20130227122302.GA5678@pd.tnic> <20130227150733.GB22383@htj.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Received: from mail.skyhub.de ([78.46.96.112]:40900 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750784Ab3B0QIk (ORCPT ); Wed, 27 Feb 2013 11:08:40 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-next-owner@vger.kernel.org List-ID: To: Sedat Dilek Cc: Tejun Heo , Wim Van Sebroeck , Ingo Molnar , Steven Rostedt , linux-watchdog@vger.kernel.org, x86@kernel.org, LKML , linux-next , Stephen Rothwell , Andrew Morton 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'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 :-) Thanks. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. --