public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Henrik Austad <henrik@austad.us>
To: "Gideon D'souza" <gidisrael@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	kernel-mentors-owner@selenic.com
Subject: Re: Is there any list for newbie bugs?
Date: Tue, 4 Mar 2014 11:08:04 +0100	[thread overview]
Message-ID: <20140304100804.GC18178@austad.us> (raw)
In-Reply-To: <CAPNrq4xd-fdStjz+BPT4z8FMCsiBH51CpozJjwDrY3x4F6qHgw@mail.gmail.com>

On Tue, Mar 04, 2014 at 03:10:54PM +0530, Gideon D'souza wrote:
> Hey All,
> 
> In my quest for work in the linux kernel I was looking at bugs.
> 
> While I have a general idea of the kernel (including KDB) most of the
> bugs I've seen (under process management and drivers) are very
> contrived to me.
> 
> I was wondering if there is anything like a good_first_bug or
> newbie_bug list anywhere?
> 
> If not, anyone out there know any bugs a kernel toddler can try and attack?

As with anything, the simple bugs tend to be removed quite quickly, I don't 
think many kernelhackers leave the easy bugs "just to be nice to newbies" -
whenever a bug is discovered they are fixed.

However, I discovered http://eudyptula-challenge.org/ a little while ago.
Be warned, I haven't tested it, not sure what the challenge is like, but 
might as well be a good place to start.

Good luck!

-- 
Henrik Austad

      reply	other threads:[~2014-03-04 10:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04  9:40 Is there any list for newbie bugs? Gideon D'souza
2014-03-04 10:08 ` Henrik Austad [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140304100804.GC18178@austad.us \
    --to=henrik@austad.us \
    --cc=gidisrael@gmail.com \
    --cc=kernel-mentors-owner@selenic.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox