All of lore.kernel.org
 help / color / mirror / Atom feed
From: Logan Blyth <mrbojangles3@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: Require mentoring for picking up
Date: Wed, 03 Jul 2013 00:52:28 +0000	[thread overview]
Message-ID: <51D375CC.4060705@gmail.com> (raw)
In-Reply-To: <CANpOL-w=W47NUg04nHRtL4S+Fpgt7SbigCwigHCsda31woccvQ@mail.gmail.com>

I also would like help setting up a test box / getting started as a 
janitor.  Imtiyaz beat me to an email :)
On 07/02/2013 07:56 PM, Imtiyaz Hussain wrote:
> Hello list,
>
> I have set up my test-box with help from Kumar Amit Mehta. I would
> like to start kernel janitorial work and would like to take up the
> below task found in TODO link (
> http://kernelnewbies.org/KernelJanitors/Todo ):-
>
> "...From: Hans Grobler
> - audit ioctl functions to make sure there is no way a user can crash
> the machine or do sensitive stuff. For example, check for the
> necessary capabilities. Check that no userspace pointers are accessed
> directly. be careful with this... it takes a while to figure out which
> ioctls are covered by the parent ioctl function (these can be nested
> to great depths)..."
>
> I looked at the mailing lists and found no one is working on this.
> Please correct my understanding. I am new to kernel newbies, so this
> is what i think before starting:-
> 1. Contact Hans Grobler for starting up ?
> 2. Find files with ioctl functions already implemented and do the
> required assessment.
>
> Also, needed some advise on git branching to work on the kernel.
>
> Your advise will be helpful.
>
> Sincerely,
> Immi
> --
> To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2013-07-03  0:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-02 23:56 Require mentoring for picking up Imtiyaz Hussain
2013-07-03  0:52 ` Logan Blyth [this message]
2013-07-03  7:25 ` Dan Carpenter

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=51D375CC.4060705@gmail.com \
    --to=mrbojangles3@gmail.com \
    --cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.