linux-kernel - Re: [next-20130227] kernel NULL pointer dereference [ watchdog

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+icZUVhfYHu_EtC=itTR04OGq_yOq902_ZMb9_Jy=1pZfU_FA@mail.gmail.com>
Date:	Wed, 27 Feb 2013 17:14:04 +0100
From:	Sedat Dilek <sedat.dilek@...il.com>
To:	Borislav Petkov <bp@...en8.de>,
	Sedat Dilek <sedat.dilek@...il.com>, Tejun Heo <tj@...nel.org>,
	Wim Van Sebroeck <wim@...ana.be>,
	Ingo Molnar <mingo@...hat.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	linux-watchdog@...r.kernel.org, x86@...nel.org,
	LKML <linux-kernel@...r.kernel.org>,
	linux-next <linux-next@...r.kernel.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [next-20130227] kernel NULL pointer dereference [ watchdog | perf
 related ? ]

On Wed, Feb 27, 2013 at 5:08 PM, Borislav Petkov <bp@...en8.de> 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.
> --
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/