|
Size: 7113
Comment:
|
Size: 5873
Comment: add nftables description
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = FOSS Outreach Program for Women (OPW) and Project Ascend Alumni = Please see the [https://wiki.gnome.org/OutreachProgramForWomen FOSS Outreach Program for Women homepage] for an introduction to the program. |
## page was renamed from OPWIntro = Outreachy (formerly FOSS Outreach Program for Women (OPW) and Project Ascend Alumni) = Please see the [https://www.gnome.org/outreachy/ Outreachy homepage] for an introduction to the program. |
| Line 4: | Line 5: |
| We are looking for round 9 [:OPWSponsor:funding sponsors] and Linux kernel [:OPWMentor:mentors]. Please see the linked FAQ pages if you want to help out. | The application period for '''Round 14''' will start on February 16, 2016. It's too early to send patches to the outreachy kernel mailing list, but please consider working through the other parts of the tutorial if you are interested in applying. |
| Line 6: | Line 7: |
| Welcome OPW applicants! Our [:OPWSponsor:round 9 sponsors] have generiously donated funds for internships for women, genderqueer, genderfluid, or genderfree people, and alumni from the [http://ascendproject.org/ Ascend Project] to work on the Linux kernel. The kernel is the most basic layer of the Linux operating system. It encompasses many things: hardware drivers, filesystems, security, task scheduling, and much more. | We are looking for round 14 [:OutreachySponsor:funding sponsors] and Linux kernel [:OutreachyMentor:mentors]. Please see the linked FAQ pages if you want to help out. Welcome Outreachy applicants! Our [:OutreachySponsor:round 14 sponsors] have generiously donated funds for internships for women, genderqueer, genderfluid, or genderfree people, and residents and nationals of the United States of any gender who are Black/African American, Hispanic/Latino, American Indian, Alaska Native, Native Hawaiian, or Pacific Islander to work on the Linux kernel. The kernel is the most basic layer of the Linux operating system. It encompasses many things: hardware drivers, filesystems, security, task scheduling, and much more. '''News''' This year, we ask that you send all patches to the appropriate staging driver maintainers, as well as to the outreachy mailing list. See [:FirstKernelPatch#submit_a_patch:Submit a patch] for more information. |
| Line 9: | Line 14: |
| The application period for OPW Round 8 is September 12 to October 31. Most OPW organizations have an application deadline of October 22, however, the Linux kernel application period will be put on temporary hold from October 10 to October 20. Most kernel mentors will be attending conferences (LinuxCon Europe, Linux Plumbers Conf, and Embedded Linux Conference Europe) during that time. During the hold period, no new kernel application patches will be accepted or reviewed, and mentors may not be available on the IRC channel. Therefore, it is important to start sending patches early in the application period. We suggest that you tackle a medium-sized advanced project during that week, rather than preparing to send many small clean up patches after the hold period is finished. Please fill our your [https://live.gnome.org/OutreachProgramForWomen#Application_Process initial application] by October 22nd, and complete your initial kernel patch by October 31. Applicants that do not complete the first patch will not be considered for an internship. Please take a look at our [:OPWApply:application FAQ] for more info on how to fill our your initial application. Applicants will be notified on November 12 if they have been accepted. |
The application period for Outreachy Round 14 is February 16 to March 30. Please fill your [https://live.gnome.org/OutreachProgramForWomen#Application_Process application] by '''March 30''', and complete your kernel patch by '''March 30''' also (7pm UTC in both cases). Applicants that do not complete the first patch will not be considered for an internship. Please take a look at our [:OutreachyApply:application FAQ] for more info on how to fill out your application. |
| Line 15: | Line 18: |
| * Join the [https://groups.google.com/forum/#!forum/opw-kernel opw-kernel mailing list] * Join the #opw IRC channel on irc.gnome.org * Join the #kernel-opw IRC channel on irc.oftc.net * Read our [:OPWApply:instructions for applying], and apply by October 31. * Use our [:OPWfirstpatch:tutorial] to send in your first kernel patch by October 31. |
* Join the [https://groups.google.com/forum/#!forum/outreachy-kernel outreachy-kernel mailing list] * Join the #outreachy IRC channel on irc.gnome.org * Join the #kernel-outreachy IRC channel on irc.oftc.net * Read our [:OutreachyApply:instructions for applying], and apply by March 30. * Use our [:Outreachyfirstpatch:tutorial] to send in your first kernel patch by March 30. |
| Line 24: | Line 27: |
| Some projects will have small tasks that OPW applicants can complete. In order to ensure applicants aren't working on the same task, we need your help in coordinating who is working on what task. Please see the OPWTasks page for details before starting on a task! | Some projects may have small tasks you can complete as part of the application process. '''Do not''' start on these tasks until after you complete the [:Outreachyfirstpatch:first patch tutorial] and Greg Kroah-Hartman has accepted at least ten of your cleanup patches and two of your patchsets. In order to ensure applicants aren't working on the same task, we need your help in coordinating who is working on what task. Please see the [:OutreachyTasks:Outreachy tasks page] for details before starting on a task! |
| Line 26: | Line 29: |
| = Round 9 projects = | = Round 14 projects = Previous projects, from round 13 projects are available [:OutreachyRound13:here]. For each project, if you click on the proposer's name, you may find more information. |
| Line 28: | Line 32: |
| Each project may have some small tasks you can complete as part of the application process. Only '''after''' several of your staging drivers cleanup patches and patchsets have been accepted should you move onto those small tasks. Make sure to coordinate which tasks you are working on by editing the [:OPWTasks:OPW tasks page]. | == Finding and fixing resource release bugs == ''Mentor:'': [:JuliaLawall:Julia Lawall] |
| Line 30: | Line 35: |
| == Kernel tinification == | Hector is a tool for finding missing resource release operations (kfree, etc). This project will involve analyzing the reports produced by Hector on Linux kernel code and submitting patches to fix those that are found to be true bugs. |
| Line 32: | Line 37: |
| ''Mentor:'': Josh Triplett | == Using an IDR to replace the process ID allocator == ''Mentor:'': [:MatthewWilcox:Matthew Wilcox] |
| Line 34: | Line 40: |
| Over time, the Linux kernel has grown far more featureful, but it has also grown significantly larger, even with all the optional features turned off. I'd like to reverse that trend, making the kernel much smaller, to enable ridiculously small embedded applications and other fun uses. | Process IDs are currently allocated using a custom allocator. This project would try to replace that allocator with the IDR. |
| Line 36: | Line 42: |
| In this project, you'll start from "make allnoconfig", and then try to shrink the kernel even further. You'll learn how to work with the kernel configuration system, Kconfig, and use scripts/bloat-o-meter to measure the size impact of a change. | == Project == ''Mentor:'': [:WikiName:Mentor names] |
| Line 38: | Line 45: |
| This is a highly incremental project: each feature you make optional or kernel component you shrink will mostly stand alone, and you can develop and submit each change independently. | Brief project description. |
| Line 40: | Line 47: |
| Some of these tinification goals will work well during the application period; others will require a substantial time investment, and will primarily make sense during the full internship. | == nftables == ''Mentor:'': [:pablo:Pablo Neira Ayuso] |
| Line 42: | Line 50: |
| Before working on any of these, especially during the application period, you should send a quick note to the OPW kernel mailing list to coordinate, and avoid duplicated effort. | nftables provides a replacement for the very popular {ip,ip6,arp,eb}tables tools. nftables reuses most of the Netfilter components such as the existing hooks, connection tracking system, NAT, userspace queueing, logging among many other features. So we have only replaced the packet classification framework. nftables comes with a new userspace utility ''nft'' and the low-level userspace library ''libnftnl''. The goal will be to help finish the translation layer software that converts from the iptables syntax to nftables, complete some simple missing features and fixing bugs whenever possible. |
| Line 44: | Line 52: |
| Please see https://tiny.wiki.kernel.org/ for more details on this effort. See https://tiny.wiki.kernel.org/projects for a list of possible projects. The projects listed as "small" can potentially be done during the application period, or by an intern accepted to work on this project. The projects listed as "large" should wait until the internship. | If you are interested in this project please consider solving any of the following tasks: |
| Line 46: | Line 54: |
| (Note to mentors and prospective applicants: Josh plans to present the tinification effort and list of projects at Linux Kernel Summit, and may add, remove, or edit items on this list based on feedback obtained there.) | * Request an account for the wiki.nftables.org page and help us improve the content. * Provide an iptables to nft translation via the iptables-translate utility. You can give a try to the following extensions: icmp, icmp6, rt. * Try to fix any of the existing nft bugs in bugzilla.netfilter.org. |
| Line 48: | Line 58: |
| == Coccinelle == [http://coccinelle.lip6.fr Coccinelle] is a program matching and transformation tool for C code that has been used extensively in contributing to the Linux kernel, for both code evolutions and bug fixes. Coccinelle is driven by specifications, known as semantic patches, that use a notation based on C code, and are this fairly easy to develop. Around 40 semantic patches are included with the Linux kernel source code, in scripts/coccinelle, and are used in the continuous testing service provided by Intel. Recently, we have used Coccinelle in an extensive study of [http://hal.archives-ouvertes.fr/docs/01/02/27/04/PDF/faults-in-linux-2.6-tocs.pdf faults in Linux 2.6]. The goal of this project is to extend the results to more recent versions of Linux, and to facilitate the extension of the work to subsequent versions. This will entail: 1. Running the Coccinelle scripts that have been developed to collect data. 1. Evaluating the resulting reports to identify real bugs and false positives. 1. Submitting patches to the Linux kernel to fix the identified real bugs that are still present in the kernel. 1. Updating a database with the results. 1. Creating graphs to summarize the results. ''Mentor:'' [http://kernelnewbies.org/JuliaLawall Julia Lawall] |
For more information on nftables, please check: http://wiki.nftables.org |
| Line 66: | Line 63: |
| * Join the [https://groups.google.com/forum/#!forum/opw-kernel opw-kernel mailing list] * Join the #opw IRC channel on irc.gnome.org * Join the #kernel-opw IRC channel on irc.oftc.net * Read our [:OPWApply:instructions for applying], and apply by October 22. * Use our [:OPWfirstpatch:tutorial] to send in your first kernel patch by October 31. * After you have sent several cleanup patches and at least one patchset, choose a [:OPWTasks:small task] to complete. |
* Join the [https://groups.google.com/forum/#!forum/outreachy-kernel outreachy-kernel mailing list] * Join the #outreachy IRC channel on irc.gnome.org * Join the #kernel-outreachy IRC channel on irc.oftc.net * Read our [:OutreachyApply:instructions for applying], and apply by March 30. * Use our [:Outreachyfirstpatch:tutorial] to send in your first kernel patch by March 30. * After you have 10 cleanup patches and at least two patchsets, choose some [:OutreachyTasks:small tasks] to complete. |
Outreachy (formerly FOSS Outreach Program for Women (OPW) and Project Ascend Alumni)
Please see the [https://www.gnome.org/outreachy/ Outreachy homepage] for an introduction to the program.
The application period for Round 14 will start on February 16, 2016. It's too early to send patches to the outreachy kernel mailing list, but please consider working through the other parts of the tutorial if you are interested in applying.
We are looking for round 14 [:OutreachySponsor:funding sponsors] and Linux kernel [:OutreachyMentor:mentors]. Please see the linked FAQ pages if you want to help out.
Welcome Outreachy applicants! Our [:OutreachySponsor:round 14 sponsors] have generiously donated funds for internships for women, genderqueer, genderfluid, or genderfree people, and residents and nationals of the United States of any gender who are Black/African American, Hispanic/Latino, American Indian, Alaska Native, Native Hawaiian, or Pacific Islander to work on the Linux kernel. The kernel is the most basic layer of the Linux operating system. It encompasses many things: hardware drivers, filesystems, security, task scheduling, and much more.
News This year, we ask that you send all patches to the appropriate staging driver maintainers, as well as to the outreachy mailing list. See [:FirstKernelPatch#submit_a_patch:Submit a patch] for more information.
How to apply
The application period for Outreachy Round 14 is February 16 to March 30. Please fill your [https://live.gnome.org/OutreachProgramForWomen#Application_Process application] by March 30, and complete your kernel patch by March 30 also (7pm UTC in both cases). Applicants that do not complete the first patch will not be considered for an internship. Please take a look at our [:OutreachyApply:application FAQ] for more info on how to fill out your application.
If you are interested in being a Linux kernel intern, please:
Join the [https://groups.google.com/forum/#!forum/outreachy-kernel outreachy-kernel mailing list]
- Join the #outreachy IRC channel on irc.gnome.org
- Join the #kernel-outreachy IRC channel on irc.oftc.net
Read our [:OutreachyApply:instructions for applying], and apply by March 30.
Use our [:Outreachyfirstpatch:tutorial] to send in your first kernel patch by March 30.
Participating Linux kernel projects
Applicants for all projects should have basic experience with C or C++ and boolean algebra. Optionally, we would love it if you have basic operating system knowledge, know your way around a Linux/UNIX command line, and/or know the revision system called git. Please note that these three skills can be learned during the internship.
Some projects may have small tasks you can complete as part of the application process. Do not start on these tasks until after you complete the [:Outreachyfirstpatch:first patch tutorial] and Greg Kroah-Hartman has accepted at least ten of your cleanup patches and two of your patchsets. In order to ensure applicants aren't working on the same task, we need your help in coordinating who is working on what task. Please see the [:OutreachyTasks:Outreachy tasks page] for details before starting on a task!
Round 14 projects
Previous projects, from round 13 projects are available [:OutreachyRound13:here]. For each project, if you click on the proposer's name, you may find more information.
Finding and fixing resource release bugs
Mentor:: [:JuliaLawall:Julia Lawall]
Hector is a tool for finding missing resource release operations (kfree, etc). This project will involve analyzing the reports produced by Hector on Linux kernel code and submitting patches to fix those that are found to be true bugs.
Using an IDR to replace the process ID allocator
Mentor:: [:MatthewWilcox:Matthew Wilcox]
Process IDs are currently allocated using a custom allocator. This project would try to replace that allocator with the IDR.
Project
Mentor:: [:WikiName:Mentor names]
Brief project description.
nftables
Mentor:: [:pablo:Pablo Neira Ayuso]
nftables provides a replacement for the very popular {ip,ip6,arp,eb}tables tools. nftables reuses most of the Netfilter components such as the existing hooks, connection tracking system, NAT, userspace queueing, logging among many other features. So we have only replaced the packet classification framework. nftables comes with a new userspace utility nft and the low-level userspace library libnftnl. The goal will be to help finish the translation layer software that converts from the iptables syntax to nftables, complete some simple missing features and fixing bugs whenever possible.
If you are interested in this project please consider solving any of the following tasks:
- Request an account for the wiki.nftables.org page and help us improve the content.
- Provide an iptables to nft translation via the iptables-translate utility. You can give a try to the following extensions: icmp, icmp6, rt.
- Try to fix any of the existing nft bugs in bugzilla.netfilter.org.
For more information on nftables, please check: http://wiki.nftables.org
Yeah, that sounds cool!
If you are interested in being a Linux kernel intern, please:
Join the [https://groups.google.com/forum/#!forum/outreachy-kernel outreachy-kernel mailing list]
- Join the #outreachy IRC channel on irc.gnome.org
- Join the #kernel-outreachy IRC channel on irc.oftc.net
Read our [:OutreachyApply:instructions for applying], and apply by March 30.
Use our [:Outreachyfirstpatch:tutorial] to send in your first kernel patch by March 30.
After you have 10 cleanup patches and at least two patchsets, choose some [:OutreachyTasks:small tasks] to complete.