linux-kernel - Re: Ask for help, about the trivial patches.

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] [day] [month] [year] [list]

Date:	Mon, 16 Jul 2007 09:51:14 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	jimmy bahuleyan <knight.camelot@...il.com>
CC:	TripleX Chung <triplex@...kernel.org>,
	Jesper Juhl <jesper.juhl@...il.com>, trivial@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: Ask for help, about the trivial patches.

jimmy bahuleyan wrote:
> TripleX Chung wrote:
>> But I still have problems.
>> Trivial means "of little worth or importance". But some of the examples
>> in the rules are important, like "runtime fixes". Spell fixes must be
>> unimportant, but most of the runtime fixes like memory leaks or NULL
>> pointers must be important. I was still a little confused with them.
>>
> 
> Literally, yes. But look at it from a s/w engineering point of view.
> 
> A NULL pointer deref is important, but it is also a *very local* and
> very obvious fix (one that doesn't need extensive testing, one that
> doesn't have effects spread out over many modules that requires great
> amount of thought).
> 
> So such things are trivial bug-fixes.

Yes; it's more the /handling/ of the patch that is "trivial" in a strict
sense.  Bug fixes should usually go through maintainers.  But for fixes
which are obvious == easy to verify, trivial@...nel.org makes sense as a
central point for submitters to turn to, to lower the barrier for
submission.
-- 
Stefan Richter
-=====-=-=== -=== =----
http://arcgraph.de/sr/
-
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/