Re: [next-20130227] kernel NULL pointer dereference [ watchdog | perf related ? ]

From: Borislav Petkov <bp@alien8.de>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Tejun Heo <tj@kernel.org>, Wim Van Sebroeck <wim@iguana.be>,
	Ingo Molnar <mingo@redhat.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	linux-watchdog@vger.kernel.org, x86@kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	linux-next <linux-next@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [next-20130227] kernel NULL pointer dereference [ watchdog | perf related ? ]
Date: Wed, 27 Feb 2013 17:08:33 +0100	[thread overview]
Message-ID: <20130227160833.GF5530@pd.tnic> (raw)
In-Reply-To: <CA+icZUUFCOPJ=TAE-5=suUqPy0NjA+BSToiZxX=Xm7u=30GdOA@mail.gmail.com>

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.
--