linux-kernel - Re: CFD: linux-wanking@...r.kernel.org (was [PATCH] Standard indentation of arguments)

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 for Android: free password hash cracker in your pocket

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

Message-ID: <87d4nf2ljv.fsf@saeurebad.de>
Date:	Thu, 22 May 2008 03:07:48 +0200
From:	Johannes Weiner <hannes@...urebad.de>
To:	"Jesper Juhl" <jesper.juhl@...il.com>
Cc:	"Jonathan Corbet" <corbet@....net>,
	"Cyrill Gorcunov" <gorcunov@...il.com>, rdunlap@...otime.net,
	tytso@....edu, hch@...radead.org, viro@...iv.linux.org.uk,
	linux-kernel@...r.kernel.org, davem@...emloft.net,
	"Andrew Morton" <akpm@...ux-foundation.org>
Subject: Re: CFD: linux-wanking@...r.kernel.org (was [PATCH] Standard indentation of arguments)

Hi,

"Jesper Juhl" <jesper.juhl@...il.com> writes:

> 2. How to find things to work on as a beginner
> ---
>
> Many people new to kernel development have a hard time finding
> projects to start out with. The kernel is a large project and it's not
> surprising that some people find it hard to work out where to begin.
>
> A good way to start is by trying to fix some bugs.
>
> There are plenty of bugs to go around and fixing bugs is a great way
> to learn since you need to understand (and thus learn) the code
> surrounding the bug in order to fix it properly, so it usually teaches
> a lot.  Submitting small bug fixes is also a great way to get
> comfortable with the patch submission process.
>
> Finding bugs to fix is easy. Here are some ways to find useful work to
> do:
>
  - Run a recent development kernel.  If you already know an area that
    might interest you, use the tree of that subsystem.  Otherwise
    Linus' tree.  Or the -mm tree.

> - Build a bunch of 'randconfig' kernels and log the output from the
> build. Building some 10-20 randconfig kernels usually exposes plenty
> of warnings and/or errors during the build. Fixing some of those
> should keep you busy for a while.
>
> - Grep the kernel source for "FIXME", "XXX" and similar comments. They
> often describe areas of the code that has known bugs, could be
> optimized, needs review etc. Lots of work to do can be found that way.
>
> - Look through the Kernel Janitors TODO list
> (http://kernelnewbies.org/KernelJanitors/Todo) for items of interest,
> then try to fix some of the issues on the list.
>
> - Go through the kernel Bugzilla (http://bugzilla.kernel.org/) and see
> if you can fix any of the many bugs filed in it. There's a metric
> butload of bugs filed in there that need attention.

  - Read the mailing list.  Again, if you are interested in a specific
    area, there are also subsystem-related mailing lists, check
    http://vger.kernel.org/vger-lists.html.

Probably needs some rephrasing...

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