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: <20130227164610.GG5530@pd.tnic>
Date:	Wed, 27 Feb 2013 17:46:10 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Sedat Dilek <sedat.dilek@...il.com>
Cc:	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 05:14:04PM +0100, Sedat Dilek wrote:
> 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.

Ok, now this formulation reads much nicer. So if you really think this
is needed, simply talk to sfr and see what he has to say about it. But
please do it in a nice way.

I'd say, serious suggestions on how the workflow could be improved are
always welcome.

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/