linux-kernel - Re: Arm Compiler - Part 1 of Compiling Tests

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]

Date:	Mon, 07 Jul 2014 20:22:46 +0200
From:	Paul Bolle <pebolle@...cali.nl>
To:	Nick Krause <xerofoify@...il.com>
Cc:	Theodore Ts'o <tytso@....edu>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Arm Compiler - Part 1 of Compiling Tests

On Mon, 2014-07-07 at 13:35 -0400, Nick Krause wrote:
> On the other hand there seems to be too many FIXMEs in the main
> kernel for one person to fix.

A quick grep for FIXMEs (also including the "XXX" pattern, which
basically means the same thing) triggers over 7000 hits. Even with a
(rather optimistic) one hour per FIXME that's over three years of work
(assuming a sane working hours/year metric).

Moreover, you appear to misunderstand the meaning of these FIXMEs. It's
not a marker for something trivial that somehow never got done. It might
actually mean all kind of things. In many cases it points at a hard, or
time consuming, etc., problem that no one has yet found a way, or the
time, to fix properly.

I would not advise someone new to the kernel to grep for FIXMEs to see
if they could contribute something. There are many things those people
could do, but those FIXMEs seem an awkward place to start.

Paul Bolle

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