The 2019 Linux Kernel Maintainers Summit and LF Interviews

-
The 2019 Linux Kernel Maintainers Summit
The 2019 version of the invitation-only Linux Kernel Maintainers Summit was held on September 12 2019, in Lisbon, Portugal. There, 31 kernel developers discussed a number of issues relating to the kernel development process and how it can be improved.
-
Defragmenting the kernel development process
The first session at the 2019 Linux Kernel Maintainers Summit was a last-minute addition to the schedule. Dmitry Vyukov's Linux Plumbers Conference session on the kernel development process (slides [PDF]) had inspired a number of discussions that, it was agreed, should carry over into the summit. The result was a wide-ranging conversation about the kernel's development tools and what could be done to improve them.
Ted Ts'o introduced the topic by noting that his employer, Google, has a group dedicated to the creation of development tools, and that a lot of good things have come from that. The kernel community also has a lot of tools aimed at making developers more productive, but rather than having a single group creating those tools, we have many competing groups. While competition is good, he said, it also diffuses the available development time and may not be, in the end, the best way to go. He then turned the session over to Vyukov.
-
Dealing with automated kernel bug reports
There is value in automatic testing systems, but they also present a problem of their own: how can one keep up with the high volume of bug reports that they generate? At the 2019 Linux Kernel Maintainers Summit, Shuah Khan ran a session dedicated to this issue. There was general agreement that the reports are hard to deal with, but not a lot of progress toward a solution.
Khan began by noting that one pervasive problem with these systems is classification: who should be responsible for a problem, what priority should it have, and is anybody working on it now? Turning to syzbot in particular, she said that getting the reproducer — the program that causes the reported problem to manifest itself — for any given report is a manual task, and that kernel developers tend to lose track of reproducers once the problem is fixed. It would be better, she said, to hang onto these reproducers and use them as regression tests going forward. She is looking into adding them to the kernel self-test infrastructure.
-
The stable-kernel process
The stable kernel process is a perennial topic of discussion at gatherings of kernel developers; the 2019 Linux Kernel Maintainers Summit was no exception. Sasha Levin ran a session there where developers could talk about the problems they have with stable kernels and ponder solutions.
Levin begin by saying that he has been working on the complaints he got the year before. One of those was that the automatic patch-selection system "goes nuts" and picks the wrong things. It has been retrained twice in the last year and has gotten better at only selecting fixes. About 50% of recent stable releases has been made up of patches explicitly tagged for stable updates; the other half has come from the automated system.
-
Linus Torvalds on the kernel development community
The Linux Kernel Maintainers Summit is all about the development process, so it is natural to spend some time on how that process is working at the top of the maintainer hierarchy. The "is Linus happy?" session during the 2019 summit revealed that things are working fairly well at that level, but that, as always, there are a few things that could be improved.
Torvalds initially turned the question around, saying that it should be about whether everybody else is happy about his work. But then he turned it back to his current pet peeve: developers who do not put changes into linux-next before pushing them into the mainline. There was one specific tree that he was unhappy about in the 5.3 merge window; others have been problematic in the past but have improved somewhat. But, it seems, there is always somebody. In general, about 10% of the patches that show up during the merge window did not first show up in linux-next.Dan Williams asked whether there should be a rule requiring any changes pushed upstream to be in linux-next for at least 24 hours. Torvalds responded that he doesn't even check for presence in linux-next early in the merge window; he is happy enough to get an early pull request that nothing more is required. As the merge window approaches its end, though, he does start checking, and absence from linux-next (earlier in the merge window) can result in pull requests not being acted upon.
-
Maintainers Summit topics: pull depth, hardware vulnerabilities, etc.
In the discussion prior to the summit, James Bottomley noted that a lot of subsystem trees are pulled directly into the mainline by Linus Torvalds. He wondered whether that is a good thing, or whether it might be better to have mid-level maintainers aggregating more pull requests to increase the "pull depth" of lower-level trees and decrease the load at the top. Bottomley was not at the summit itself, but his topic was discussed there; the answer was that things are mostly OK as they are. (For the curious, a graphic showing the pull paths for the 5.1 kernel can be found on this page.)
Torvalds responded to the question by saying that he loves to get large pull requests from maintainers he trusts implicitly; that way, he can get a lot of work into the mainline with little effort. There is just one little problem: there are few maintainers that he trusts to that degree. In the absence of that trust, he would prefer to get more, smaller requests that are easier to review and easier to refuse if there is something wrong. He mentioned some subsystems in particular that have been problematic in the past; bypassing the maintainer and getting more focused pull requests from lower-level maintainers has improved the situation. He is not happy about having to do that, but it is better than the alternative, he said.
He does not, however, feel overworked by the number of trees he is pulling now. He aims to act on about 25 pull requests per day during the merge window, normally spending about ten minutes on each of those.
There are advantages to having a maintainer hierarchy, though, that go beyond reducing the number of pull requests at the top. Dave Airlie pointed out that it is a good way to train others to manage the subsystem and know that others would be able to handle it. Torvalds said that, with many subsystems, he is not competent to review the patches himself; it is good to have a mid-level maintainer who understands the area looking at things.
-
Erik Nordmark Explains The Edge Virtualization Engine (EVE)
-
Highlights From The Open Networking Summit
-

- Login or register to post comments
Printer-friendly version- 1796 reads
PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
digiKam 7.7.0 is released
After three months of active maintenance and another bug triage, the digiKam team is proud to present version 7.7.0 of its open source digital photo manager. See below the list of most important features coming with this release.
|
Dilution and Misuse of the "Linux" Brand
|
Samsung, Red Hat to Work on Linux Drivers for Future Tech
The metaverse is expected to uproot system design as we know it, and Samsung is one of many hardware vendors re-imagining data center infrastructure in preparation for a parallel 3D world.
Samsung is working on new memory technologies that provide faster bandwidth inside hardware for data to travel between CPUs, storage and other computing resources. The company also announced it was partnering with Red Hat to ensure these technologies have Linux compatibility.
|
today's howtos
|








.svg_.png)
Content (where original) is available under CC-BY-SA, copyrighted by original author/s.

Recent comments
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago
1 year 11 weeks ago