|
Size: 8342
Comment:
|
Size: 9567
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| '''Round 12''' is coming up soon. 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 intersted in applying. | '''Round 13''' will be coming up in a few months. 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 intersted in applying. |
| Line 7: | Line 7: |
| We are looking for round 11 [:OutreachySponsor:funding sponsors] and Linux kernel [:OutreachyMentor:mentors]. Please see the linked FAQ pages if you want to help out. | We are looking for round 13 [:OutreachySponsor:funding sponsors] and Linux kernel [:OutreachyMentor:mentors]. Please see the linked FAQ pages if you want to help out. |
| Line 12: | Line 12: |
| The application period for Outreachy Round 11 is September 29 to November 2. Please fill your [https://live.gnome.org/OutreachProgramForWomen#Application_Process application] by '''November 2''', and complete your kernel patch by '''November 2''' also (7pm UTC on both dates). 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. | The application period for Outreachy Round 12 is February 9 to March 22. Please fill your [https://live.gnome.org/OutreachProgramForWomen#Application_Process application] by '''March 22''', and complete your kernel patch by '''March 22''' 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 17: | Line 17: |
| * Join the #opw IRC channel on irc.gnome.org | * Join the #outreachy IRC channel on irc.gnome.org |
| Line 19: | Line 19: |
| * Read our [:OutreachyApply:instructions for applying], and apply by November 2. * Use our [:Outreachyfirstpatch:tutorial] to send in your first kernel patch by November 2. |
* Read our [:OutreachyApply:instructions for applying], and apply by March 22. * Use our [:Outreachyfirstpatch:tutorial] to send in your first kernel patch by March 22. |
| Line 27: | Line 27: |
| = Round 11 projects = Round 10 projects are available [:OutreachyRound10:here]. For each project, if you click on the proposer's name, you may find more information. |
= Round 12 projects = Previous projects, from round 11 projects are available [:OutreachyRound11:here]. For each project, if you click on the proposer's name, you may find more information. The following is a partial list of projects. More will come soon. |
| Line 30: | Line 30: |
| == ADXL377 Triple Axis Accelerometer IIO driver == ''Mentor:'': [:OctavianPurdila:Octavian Purdila], [:DanielBaluta:Daniel Baluta] |
== Update legacy workqueue creation interface users == ''Mentor:'': [:Tejun Heo:Tejun Heo] Workqueue is an asynchronous execution mechanism which is widely used across the kernel. A work item queued on a workqueue is asynchronously executed by a worker task (kworker/* in ps output). It's used for various purposes from simple context bouncing to hosting a persistent in-kernel service thread. Due to its development history, there currently are two sets of interfaces to create workqueues. * create[_singlethread|_freezable]_workqueue() * alloc[_ordered]_workqueue() The latter is the new interface which is superset of the former. While each create*_workqueue() can be directly mapped to an alloc*_workqueue() invocation, create*_workqueue() encodes much less information than alloc*_workqueue() making determining which exact flavor and attributes to use non-trivial. Each case should be examined to find out why a specific kind is used and then converted to an alloc*_workqueue() invocation which matches the requirements. There currently are around 280 users of the legacy interface. While the number seems daunting, there are common patterns that many of them follow. This project would involve understanding workqueue's various users to certain degree in addition to workqueue itself and can be a good opportunity to roam through and learn various parts of the kernel. See the small tasks for this project on the [:Tejun Heo: mentor's page]. == Coccinelle == ''Mentor:'': [:JuliaLawall:Julia Lawall] Coccinelle is a program matching and transformation tool that has been extensively used for finding bugs in the Linux kernel. Around 50 Coccinelle rules are currently part of the kernel source code, and are regularly run on all kernel code changes via the 0-day build testing service. Still, there is the potential for many more such rules. The goal of this project is to prepare existing semantic patches, such as those found at [https://github.com/coccinelle/coccinellery coccinellery] for inclusion in the kernel and to write some new ones. An optional part of the project could be to improve the coccinellery infrastructure, which is currently a 500 line bash script. Please indicate in your application whether you are interested in this part of the project, however, interest in this part of the project is not a prerequisite for being selected as an intern. More information about Coccinelle is available [http://coccinelle.lip6.fr/ here], including a [http://coccinelle.lip6.fr/papers/tutorial.pdf tutorial]. For some Coccinelle small tasks, click on the mentor name. == IIO driver == ''Mentor:'': [:DanielBaluta:Daniel Baluta] |
| Line 35: | Line 60: |
| The goal of this project is to write a driver for Analog Devices ADXL377 triple axis accelerometer using the Industrial I/O interface. In the first part of the project you will get familiar with the hardware and the IIO then implement raw readings from the device. After upstreaming the code we will enhance the driver with support for buffered readings, power management and interrupts. | The goal of this project is to write a driver for a sensor using the Industrial I/O interface. In the first part of the project you will get familiar with the hardware and the IIO subsystem then implement raw readings from the device. After upstreaming the code we will enhance the driver with support for buffered readings, power management and interrupts. The exact device will be decided when the internship starts. |
| Line 37: | Line 62: |
| We will provide you the hardware setup necessary to test the driver. If you are applying to this project please make sure to solve the [:IIO_tasks:IIO tasks]. == Staging driver cleanup == ''Mentor:'': [:GregKH:Greg Kroah-Hartman] This project will dive into a few specific drivers in the staging tree, doing more than just basic code formatting cleanup. The goal will be to help change the code to make it acceptable for merging into the "real" portion of the kernel. If possible, hardware will be provided for the code being worked on. |
We will provide you the hardware setup necessary to test the driver. If you are interested in this project please consider solving the [:IIO_tasks:IIO tasks]. |
| Line 49: | Line 69: |
| 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. |
|
| Line 51: | Line 77: |
| == Ceph-related kernel code cleanup == | == memory management latency tracing == ''Mentor:'' [:RikvanRiel:Rik van Riel] |
| Line 53: | Line 80: |
| ''Mentor:'': [:AlexElder:Alex Elder] | Every few months, some issue seems to pop up where users suffer from excessive latency at page fault and/or memory allocation time, usually (but not always) due to latency in the page reclaim code. Developers end up with some ad-hoc tracing to figure out the problem, because the kernel does not have a tool to discover the cause of these latencies on production systems. The goal of this project is to add the necessary tracepoints to the page fault, memory allocation, compaction, and reclaiming code, as well as some kind of script or tool in userspace that allows Linux users to obtain information on where time was spent when a memory allocation takes longer than a specified threshold. |
| Line 55: | Line 82: |
| The Ceph project implements a scalable and fault-tolerant network based storage system. Portions of Ceph reside in the Linux kernel, presenting either a block device or a file system interface backed by Ceph storage accessed over the network. | This project requires learning about the memory management code, as well as tracepoints, and tracing tools in userspace. |
| Line 57: | Line 84: |
| This project involves doing cleanup of the Ceph-related kernel code. The work will range from very easy fixes (like typo's and coding style) to more more substantive (refactoring functions and source files). Typically this kind of work identifies bugs as well, and if so those will be fixed (or at least documented). More information can be found [:OutreachyProjects/CephCleanup:here]. == y2038 cleanup in drivers == ''Mentor:'' [:ArndBergmann:Arnd Bergmann] The concept of 'time' in Linux is encoded in many different ways, but the most common one is based on the 'time_t' type that counts the number of seconds that have passed since Jan 1, 1970. This type is currently defined as 'long', which on 32-bit systems is a signed 32-bit number that will overflow on Jan 19 2038 and likely cause existing systems to stop working, see http://en.wikipedia.org/wiki/Year_2038_problem. On 64-bit systems, the problem is solved for the most part because 'long' is a 64-bit number that will not overflow for billions of years, but there are some important missing pieces such as file systems that store time in 32-bit quantities on disk as well support for 32-bit user space binaries running on 64-bit kernels. Solving this problem in general is a huge effort involving lots of changes in the kernel as well as in user space. This project focuses on the kernel side, can be nicely split up into many small subtasks and is a prerequisite for doing the user space changes. There are currently 2003 instances of 'time_t', 'struct timespec' and 'struct timeval' in the kernel, and we are going to replace all of them with other types. Any isolated in-kernel uses of these types can be replaced with 'ktime_t' or 'struct timespec64'. For any interface to user space (typically an ioctl command or a system call) that passes a data structure based on these types, we have to keep the existing interface working and introduce an alternative interface that can be used by newly built user space programs. [:y2038:] has a deeper introduction to the topic and will be updated with more detailed subtasks over time. |
See the small tasks for this project on the [:RikvanRiel: mentor's page]. |
| Line 86: | Line 97: |
| * Read our [:OutreachyApply:instructions for applying], and apply by November 2. * Use our [:Outreachyfirstpatch:tutorial] to send in your first kernel patch by November 2. |
* Read our [:OutreachyApply:instructions for applying], and apply by March 22. * Use our [:Outreachyfirstpatch:tutorial] to send in your first kernel patch by March 22. |
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.
Round 13 will be coming up in a few months. 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 intersted in applying.
We are looking for round 13 [: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 11 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.
How to apply
The application period for Outreachy Round 12 is February 9 to March 22. Please fill your [https://live.gnome.org/OutreachProgramForWomen#Application_Process application] by March 22, and complete your kernel patch by March 22 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 22.
Use our [:Outreachyfirstpatch:tutorial] to send in your first kernel patch by March 22.
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 12 projects
Previous projects, from round 11 projects are available [:OutreachyRound11:here]. For each project, if you click on the proposer's name, you may find more information. The following is a partial list of projects. More will come soon.
Update legacy workqueue creation interface users
Mentor:: [:Tejun Heo:Tejun Heo]
Workqueue is an asynchronous execution mechanism which is widely used across the kernel. A work item queued on a workqueue is asynchronously executed by a worker task (kworker/* in ps output). It's used for various purposes from simple context bouncing to hosting a persistent in-kernel service thread.
Due to its development history, there currently are two sets of interfaces to create workqueues.
- create[_singlethread|_freezable]_workqueue()
- alloc[_ordered]_workqueue()
The latter is the new interface which is superset of the former. While each create*_workqueue() can be directly mapped to an alloc*_workqueue() invocation, create*_workqueue() encodes much less information than alloc*_workqueue() making determining which exact flavor and attributes to use non-trivial. Each case should be examined to find out why a specific kind is used and then converted to an alloc*_workqueue() invocation which matches the requirements.
There currently are around 280 users of the legacy interface. While the number seems daunting, there are common patterns that many of them follow.
This project would involve understanding workqueue's various users to certain degree in addition to workqueue itself and can be a good opportunity to roam through and learn various parts of the kernel.
See the small tasks for this project on the [:Tejun Heo: mentor's page].
Coccinelle
Mentor:: [:JuliaLawall:Julia Lawall]
Coccinelle is a program matching and transformation tool that has been extensively used for finding bugs in the Linux kernel. Around 50 Coccinelle rules are currently part of the kernel source code, and are regularly run on all kernel code changes via the 0-day build testing service. Still, there is the potential for many more such rules. The goal of this project is to prepare existing semantic patches, such as those found at [https://github.com/coccinelle/coccinellery coccinellery] for inclusion in the kernel and to write some new ones. An optional part of the project could be to improve the coccinellery infrastructure, which is currently a 500 line bash script. Please indicate in your application whether you are interested in this part of the project, however, interest in this part of the project is not a prerequisite for being selected as an intern.
More information about Coccinelle is available [http://coccinelle.lip6.fr/ here], including a [http://coccinelle.lip6.fr/papers/tutorial.pdf tutorial]. For some Coccinelle small tasks, click on the mentor name.
IIO driver
Mentor:: [:DanielBaluta:Daniel Baluta]
A driver allows applications to communicate and control hardware devices. Each development cycle, driver changes account for more than a half of the total Linux kernel code changes.
The goal of this project is to write a driver for a sensor using the Industrial I/O interface. In the first part of the project you will get familiar with the hardware and the IIO subsystem then implement raw readings from the device. After upstreaming the code we will enhance the driver with support for buffered readings, power management and interrupts. The exact device will be decided when the internship starts.
We will provide you the hardware setup necessary to test the driver. If you are interested in this project please consider solving the [:IIO_tasks:IIO tasks].
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
memory management latency tracing
Mentor: [:RikvanRiel:Rik van Riel]
Every few months, some issue seems to pop up where users suffer from excessive latency at page fault and/or memory allocation time, usually (but not always) due to latency in the page reclaim code. Developers end up with some ad-hoc tracing to figure out the problem, because the kernel does not have a tool to discover the cause of these latencies on production systems. The goal of this project is to add the necessary tracepoints to the page fault, memory allocation, compaction, and reclaiming code, as well as some kind of script or tool in userspace that allows Linux users to obtain information on where time was spent when a memory allocation takes longer than a specified threshold.
This project requires learning about the memory management code, as well as tracepoints, and tracing tools in userspace.
See the small tasks for this project on the [:RikvanRiel: mentor's page].
Project
Mentor:: [:WikiName:Mentor names]
Brief project description.
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 #opw 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 22.
Use our [:Outreachyfirstpatch:tutorial] to send in your first kernel patch by March 22.
After you have sent several cleanup patches and at least one patchset, choose a [:OutreachyTasks:small task] to complete.