All of lore.kernel.org
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: I dont know where to start
Date: Fri, 24 Jul 2015 12:48:22 -0700	[thread overview]
Message-ID: <20150724194822.GB21913@kroah.com> (raw)
In-Reply-To: <CAAGnT3ZvbCDxO9sL25aA1PGXCT342=m0GUQuaN28eMhfVrC0EQ@mail.gmail.com>

On Fri, Jul 24, 2015 at 09:20:48PM +0200, Ahmed Soliman wrote:
> hi
> first of all I want to thank you with your real help but
> currently I started to get lost
> I can build my own kernel write patches but cannot contribute to the
> linux kernel
> because I don't know where to start learning
> I am really interested in the linux security module (although I know
> nothing about it ) but I always loved computer security and reverse
> engineering
> I started by searching for TODO as was referred by Konrad Zapa?owicz
> here <https://www.linux.com/news/software/linux-kernel/804403-three-ways-for-beginners-to-contribute-to-the-linux-kernel>
> and I found this one
> TODO: add support for apparmorfs_null and apparmorfs_mnt
> in linux/security/apparmor.c
> my first reaction was to look at the header files included and try to
> understand what was this C file supposed to do and before I even try
> to understand what is apparmorfs_null and apparmorfs_mnt but I found
> really large number of dependencies that would take ages to read and
> understand and each dependency have its own dependency  !!
> at that moment I started to feel that I am doing something wrong and I
> am not following the right approach so what do you suggest ?

That is correct, it's a lot of dependencies and knowledge to try to add
new security module features, you are on the right track, this is not an
easy task.

good luck!

greg k-h

  reply	other threads:[~2015-07-24 19:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-24 19:20 I dont know where to start Ahmed Soliman
2015-07-24 19:48 ` Greg KH [this message]
2015-07-24 19:51 ` Laurent Navet

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=20150724194822.GB21913@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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.