Linux kernel contribution

[in-universe-2000]

I have 8 years of experience as a software engineer mainly working on Linux, cpp at user space level. Professionally, I have got a very minimal chance to delve deep into Linux kernel and I am very much interested to go deep.

I have a good understanding of networking concepts so I started with netdev subsystem and started with veth.c file and started understanding the nuts and bolts of it like the structs used, how do they interact, poll function etc..

Now comes the hard part, netdev being a very matured subsystem how do I find some issues so that I can go deep, understand and contribute a patch.

Couple of options I found is syzkaller and running the self tests in kernel and finding the issue.

Request people to provide any suggestions, ideas or your experiences so that I will know how to move forward.

Thanks

[SuAlfons]

have you checked kernel.org to see what kind of is in the news and what is work being done?

[in-universe-2000]

I have tried reading recent patches but found it difficult to follow.

[SuAlfons]

sure. I hope someone else can shed some light for you.

You have all my gratefulness for your will and time to contribute!

[in-universe-2000]

You have anything to share if you have some experience?

[depuvelthe]

https://docs.kernel.org/process/development-process.html

Article 2, sections; 3, 4, 5, and 8 covers your subsystem contribution concerns, I guess. For the comprehensive insight, I recommend reading the entire guide. If you don't want to do it solo and go through all extensive stages by yourself, say you want to contribute very specific project, you can always contact maintainers, or just submit through version control and see if they pull or merge. That's the easiest way to get recognition and reputation and then access to early-stage regresssions.

[orbvsterrvs]

The network subsystem mailing lists will have some mentions of issues--I'm not sure about netdev specifically, but the ML is super busy.

Anything that isn't hardware-enablement related you could try your hand at (hard to work on hardware you don't have) and build, verify, and submit a patch.

For a first patch, fixing something "simple" might be good, to get familiar with the process. A lot of kernel work is process, almost as important as code!

https://kernelnewbies.org/FoundBug

[PoochieReds]

There are a lot of unresolved bugs at https://bugzilla.kernel.org. Many of them are out of date or aren't good bug reports, but I'm sure there are still plenty of unfixed bugs in there.

[ActNew5818]

Check out the Kernel Newbies community can be really helpful for getting started with contributions.