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  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]
Date:	Sat, 4 Jan 2014 21:36:54 +0100
From:	Bruno Prémont <bonbons@...ux-vserver.org>
To:	"Gideon D'souza" <gidisrael@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: How does a newbie find work?

Hi Gideon,

On Sat, 04 January 2014 "Gideon D'souza" <gidisrael@...il.com> wrote:
> I've been looking to hacking at the kernel for a long time now.
> 
> I've managed to have a good setup, build the latest stable kernel and
> boot from it. I've read some of the docs, Coding Styles etc and
> watched GregKH's talks on youtube. I'm also reading Robert Love's
> Linux Kernel Development.
> 
> 
> Id like now to get my hands dirty but I can't seem to find something
> simple to do. I posted to kernel janitors and kernel mentors, but no
> dice. The bugs list looks thoroughly contrived.
> 
> I've made small contributions to other OSS projects before but now I'm
> at a loss for how to study the kernel code base, what to try to
> break/change to study how the kernel works.
> 
> Is there some simple work a newbie like me can take up? Any maintainer
> need some grunt work done? Or perhaps someone could suggest a pet
> project I could try to understand things better? (Should I be learning
> how to write device drivers?)
> 
> Things that are very interesting to me so far are the KVM and the Scheduler.

Starting with writing some driver (or improving existing drivers) is one
option, though that wont get you doing work in relation with the scheduler
(maybe there is some minor driver-like work for KVM though, don't know).

A better start, and at least as useful is to read and review patches
flowing by that affect your areas of interest, test them and provide
feedback about possible bugs or improvements (proposing patches to fix
those if applicable or even just providing performance data [what
workloads benefit or suffer from given feature-patches and by how much]
for things like scheduler changes).

This way you will get to know the development process, maintainers
and the internals of the kernel in those areas - don't forget to subscribe
to the specific mailing lists!

Regards,
Bruno

> Regards,
> Gideon
--
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/

Powered by blists - more mailing lists