LWN: Comments on "Some numbers and thoughts on the stable kernels" https://lwn.net/Articles/402512/ This is a special feed containing comments posted to the individual LWN article titled "Some numbers and thoughts on the stable kernels". en-us Fri, 05 Sep 2025 12:36:46 +0000 Fri, 05 Sep 2025 12:36:46 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net Some numbers and thoughts on the stable kernels https://lwn.net/Articles/511696/ https://lwn.net/Articles/511696/ gvy <div class="FormattedComment"> For the record, that bugfix has been discussed and accepted within two weeks of moving the bugreport to LKML and within something like 8 hours of wall clock. A lil' more patience ;-)<br> </div> Thu, 16 Aug 2012 13:20:17 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/404545/ https://lwn.net/Articles/404545/ gvy <div class="FormattedComment"> <font class="QuotedText">&gt; "volunteers are still our leading source of fixes"</font><br> Well, I tried to get the patch for deadlock issue our folks have nailed down and fixed (it was rather worked around upstream) along at least into 2.6.27.y since this summer, and so far rather failed to bring attention to the issue:<br> <p> <a rel="nofollow" href="https://bugzilla.kernel.org/show_bug.cgi?id=15658">https://bugzilla.kernel.org/show_bug.cgi?id=15658</a><br> <p> Tried to forward the message with brief explanation to LKML on Aug 28 but seems like it didn't pass through (at least not to lkml.org archive).<br> <p> I've re-read all of tux.org/lkml just in case, but still need advice on *how* volunteers should pass the fixes for such non-obvious issues?<br> <p> Thanks anyone who might find some time to aid with this one.<br> </div> Sat, 11 Sep 2010 11:01:17 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/403633/ https://lwn.net/Articles/403633/ lacostej <div class="FormattedComment"> Any reason why Adrian has 'left' the community?<br> <p> I loved to see his dedication. Has someone taken his role?<br> </div> Mon, 06 Sep 2010 09:29:36 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/403039/ https://lwn.net/Articles/403039/ hingo I've been playing with the idea of producing similar stats for MySQL/MariaDB development, to benchmark it against Linux and other similar projects. This is an excellent idea to add to the analysis! Thanks. Tue, 31 Aug 2010 21:16:17 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402963/ https://lwn.net/Articles/402963/ bfields If I read lwn at work, am I shirking? If I read it after hours, am I bringing my work home with me? Help! Tue, 31 Aug 2010 16:00:08 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402934/ https://lwn.net/Articles/402934/ macson_g <div class="FormattedComment"> Yep: <a href="http://lwn.net/Articles/402327/">http://lwn.net/Articles/402327/</a><br> </div> Tue, 31 Aug 2010 12:17:36 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402932/ https://lwn.net/Articles/402932/ njd27 <div class="FormattedComment"> Are there any signs of him going crazy yet?<br> </div> Tue, 31 Aug 2010 12:00:27 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402895/ https://lwn.net/Articles/402895/ bfields <blockquote>Hm, a simple "Signed-off-by:" should suffice.</blockquote> <p>Yeah. Here's a <a href="http://thread.gmane.org/gmane.linux.kernel/205867">previous discussion</a>, where Linus says: <blockquote>So when you save a patch from oblivion by passing it on to the right person, and get it submitted when it was originally dropped by some reason, you're actually doing a fundamentally important job. Maybe it's just one small piece of the puzzle, but hey, you'd only get one small line in the changeset, so the credit (or blame ;) really is appropriate.</blockquote> Mon, 30 Aug 2010 22:32:02 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402861/ https://lwn.net/Articles/402861/ ironiridis <div class="FormattedComment"> With regard to "never" seeing someone call GKH a dickhead, you might have comments from Hknr filtered on LWN.<br> </div> Mon, 30 Aug 2010 16:57:36 +0000 Filtering ENABLED https://lwn.net/Articles/402820/ https://lwn.net/Articles/402820/ mebrown <div class="FormattedComment"> Nice! Thanks!<br> </div> Mon, 30 Aug 2010 14:49:12 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402791/ https://lwn.net/Articles/402791/ spaetz <div class="FormattedComment"> <font class="QuotedText">&gt;Who is ever really off the clock in this field? </font><br> <p> As a side note, I have seen some research on commit patterns across projects and it was really entertaining to see some projects following strict Mo-Fri 9-5 patterns while others (also including commercial developers) committed all over the place including weekends, nights etc.<br> <p> I would love to see that research across a wide range<br> </div> Mon, 30 Aug 2010 08:04:22 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402747/ https://lwn.net/Articles/402747/ eduard.munteanu <div class="FormattedComment"> Hm, a simple "Signed-off-by:" should suffice. It's already standard practice for people who maintain their own tree and relay stuff upstream, and usually those trees are rebased often. So it might make sense to use that for singular cases as well (even if they're not merges).<br> <p> This...<br> <p> Signed-off-by: &lt;original author&gt;<br> Signed-off-by: &lt;maintainer&gt;<br> Signed-off-by: Linus Torvalds<br> <p> Could turn into this...<br> <p> Signed-off-by: &lt;original author&gt;<br> Signed-off-by: &lt;spotter&gt;<br> Signed-off-by: Greg KH<br> <p> Possibly with some variation, such as whether or not you keep the maintainer in the Signed-off-by chain.<br> <p> </div> Sun, 29 Aug 2010 14:44:31 +0000 Filtering https://lwn.net/Articles/402743/ https://lwn.net/Articles/402743/ zooko <div class="FormattedComment"> Hey thanks, it works nicely!<br> </div> Sun, 29 Aug 2010 14:03:10 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402742/ https://lwn.net/Articles/402742/ maks <div class="FormattedComment"> Thanks josh for clearing up and your nice comment. :)<br> <p> As one can see on aboves authorship table Ben Hutchings is doing an incredible great job in the last year.<br> </div> Sun, 29 Aug 2010 13:05:36 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402741/ https://lwn.net/Articles/402741/ maks <div class="FormattedComment"> linux-base is used for the UUID transition. In Ubuntu it was the udev package that renamed the fstab and some bootloaders. afais linux-base is in experimental. When installing from exp one needs to tell apt to do so with ``-t'' switch aka:<br> apt-get install linux-image-2.6.35-trunk-amd64 -t experimental<br> <p> Hope that helps otherwise please ask on debian-kernel mailinglist.<br> <p> <p> </div> Sun, 29 Aug 2010 13:00:17 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402738/ https://lwn.net/Articles/402738/ maks <div class="FormattedComment"> Ok thanks for the explanations.<br> <p> Got confused by the title of the table "Most active stable contributors" and thought it was about the ones that notify stable. Could then be renamed to "Most active stable authors".<br> <p> Indeed there is currently no possibility to easily see who forwarded the patches to gregkh.<br> </div> Sun, 29 Aug 2010 12:56:03 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402731/ https://lwn.net/Articles/402731/ erwbgy Well, that may be true, but he is definitely a more useful dickhead than you are. Sun, 29 Aug 2010 09:36:53 +0000 Filtering https://lwn.net/Articles/402723/ https://lwn.net/Articles/402723/ corbet It's in the <a rel="nofollow" href="http://lwn.net/MyAccount/">My Account area</a>. Sun, 29 Aug 2010 03:44:16 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402722/ https://lwn.net/Articles/402722/ zooko <div class="FormattedComment"> Hey where is that tool for filtering the comments of certain posters out of your view of LWN?<br> </div> Sun, 29 Aug 2010 02:56:44 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402712/ https://lwn.net/Articles/402712/ hmh <div class="FormattedComment"> Yes, that would be nice.<br> <p> Also, when there is no "spotted-by:" but there is a "cc: stable", it likely means that the patch author noticed it should go into stable.<br> <p> That said, I think "stable-proposal-by" would be a better tag.<br> </div> Sun, 29 Aug 2010 00:46:12 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402702/ https://lwn.net/Articles/402702/ ncm <div class="FormattedComment"> Yes, thanks Maks! I just loaded linux-image-2.6.35-1~experimental.2 on a Dell Latitude D430 sid and it fixed the suspend/resume problems. (Q though: why does it depend on a linux-base that doesn't exist?)<br> </div> Sat, 28 Aug 2010 23:44:39 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402700/ https://lwn.net/Articles/402700/ ncm <div class="FormattedComment"> Now I know where to send Hknr messages.<br> </div> Sat, 28 Aug 2010 20:56:24 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402699/ https://lwn.net/Articles/402699/ corbet I agree it would be nice to credit people who do that kind of work. There is really no information trail at the moment which would make that possible, though. Maybe we need a Spotted-by: tag to mark patches directed to stable by people other than their author? Sat, 28 Aug 2010 19:57:33 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402696/ https://lwn.net/Articles/402696/ josh <div class="FormattedComment"> I think maks (AKA maximilian attems, one of the Debian kernel maintainers) is suggesting that in addition to crediting the author of the patch, for stable patches it seems appropriate to note the person who dug up a patch from mainline that fixed a particular bug and passed it along to stable@ for inclusion in a stable kernel, even if they didn't *write* the mainline patch. And I'd agree with that; while not the same metric as counting authors, it seems a useful metric for stable kernels.<br> <p> On that note, thanks to maks and the other Debian kernel maintainers for doing an awesome job. :)<br> </div> Sat, 28 Aug 2010 19:46:54 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402691/ https://lwn.net/Articles/402691/ corbet I simply look at the author of each patch as is shown in the stable git repository. <p> A quick look through 2.6.32.y shows you CC'd on a number of patches, but you are not the author of them in stable or mainline. Am I missing something? Sat, 28 Aug 2010 19:16:06 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402689/ https://lwn.net/Articles/402689/ maks <div class="FormattedComment"> Your stats concerning the personal contribution to stable seem at first look pretty screwed:<br> <p> First of all it is not easy to find the one that forwarded a particular patch to stable.<br> Secondly most in all times this random person gets gets showed into the Cc: of the stable patch and thus is not distinguisable from usual Cc's that happen to be listed there.<br> <p> A quick grep in the stable queue 2.6.32 releases showed 47 contributions of mine, but I'm 100% sure not to be the top contributor of it. But that forwarded patch number is certainly a lower bound.<br> <p> Please explain how you generated the stats concerning the most active contributor. Thanks.<br> </div> Sat, 28 Aug 2010 19:01:05 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402664/ https://lwn.net/Articles/402664/ BenHutchings <div class="FormattedComment"> We discussed this at the LPC last year. If I remember correctly, Greg's answer was that:<br> 1. Distributions need to let him know which stable releases they want to keep going.<br> 2. They need to help in gathering updates, and potentially to take over maintenance.<br> <p> </div> Sat, 28 Aug 2010 15:00:33 +0000 unpolite, unrespectful, uninformative and subjective https://lwn.net/Articles/402661/ https://lwn.net/Articles/402661/ dmk <div class="FormattedComment"> From the LWN Comment editor:<br> &lt;quote&gt;Please try to be polite, respectful, and informative, and to provide a useful subject line.&lt;/quote&gt;<br> <p> </div> Sat, 28 Aug 2010 13:07:15 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402650/ https://lwn.net/Articles/402650/ dambacher <div class="FormattedComment"> What I miss in the figures is the duration (e.g. in weeks) a kernel was maintained -&gt; wich was a long time kernel and wich one was really rotten<br> </div> Sat, 28 Aug 2010 07:44:36 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402648/ https://lwn.net/Articles/402648/ Hknr <div class="FormattedComment"> Well, Greg KH *is* a dickhead, no question about it.<br> He's one of the few kernel guys whose messages go straight<br> to /dev/null in my LKML filter. This also lowers the<br> traffic by a considerable amount as you no longer see<br> his endless "stable preview" threads.<br> </div> Sat, 28 Aug 2010 07:17:33 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402622/ https://lwn.net/Articles/402622/ dlang <div class="FormattedComment"> this is where it gets interesting.<br> <p> it can be that someone just volunteers to maintain it after Greg finishes with it, it can be that one (or more in the case of ) major distros base their release kernel off of it, and as a result someone takes on the maintenance of the kernel after it would finish the normal process.<br> <p> about the only criteria is an elimination criteria. Namely that the kernel in question must not have a disastrous amount of regressions discovered in the normal -stable period.<br> </div> Sat, 28 Aug 2010 01:17:14 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402617/ https://lwn.net/Articles/402617/ mpr22 People almost never call <em>anyone</em> a dickhead on LWN :) Sat, 28 Aug 2010 00:04:33 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402609/ https://lwn.net/Articles/402609/ nicooo <div class="FormattedComment"> What are the criteria for deciding which kernels will be supported? (e.g. what makes 2.6.27 different from .26 or .28)<br> </div> Fri, 27 Aug 2010 23:42:44 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402592/ https://lwn.net/Articles/402592/ corbet Who is ever really off the clock in this field? <p> A patch posted from a company email address is assumed to be posted with that company's blessing. Anybody who doesn't have that blessing is probably violating all kinds of rules. In short: when somebody posts a patch, in the absence of information to the contrary, we attribute it to their employer. The results are necessarily approximate, but I'm not sure how to do them better. Fri, 27 Aug 2010 21:59:58 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402591/ https://lwn.net/Articles/402591/ corbet Is there some context in which Adrian should have been mentioned? I didn't talk about 2.6.16, really...and he hasn't really been present in the kernel community for a while now. Fri, 27 Aug 2010 21:57:06 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402589/ https://lwn.net/Articles/402589/ drag <div class="FormattedComment"> The amount of contributions, by lines of code or by patches, does not translate directly to bug fixes. Most of them are probably features and drivers.<br> </div> Fri, 27 Aug 2010 21:55:42 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402587/ https://lwn.net/Articles/402587/ spender <div class="FormattedComment"> Third question: is there a reason why there is no mention of Adrian Bunk in the article?<br> <p> -Brad<br> </div> Fri, 27 Aug 2010 21:44:17 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402586/ https://lwn.net/Articles/402586/ jspaleta <div class="FormattedComment"> I wouldn't make the assumption about how corporate involvement is ascertained. I believe the author can go into detail as to how that is done if you need it clarified. <br> <p> -jef<br> </div> Fri, 27 Aug 2010 21:42:35 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402578/ https://lwn.net/Articles/402578/ spender <div class="FormattedComment"> "volunteers are still our leading source of fixes"<br> <p> Though volunteers beat out any other single company source of fixes, if I'm interpreting the chart correctly for 2.6.32, (100% - 15.3%) = 84.7% are coming from companies.<br> <p> That said, I can imagine a good amount of the patches being submitted from company email addresses (which is what I assume the stats are generated off of) are done when the employee is "off the clock."<br> <p> So my question: do we (and how do we) actually know how much of the kernel development is really a volunteer effort?<br> <p> BTW, I've never seen anyone on this site call Greg a "dickhead" or anything close to it (I did a search to check, feel free to do your own). Some people, myself included, disagree with how security is conveyed and sometimes handled, but it's a gross mischaracterization to equate that with childish ad-hominem attacks that were never uttered.<br> <p> I appreciate the effort Greg puts into the stable releases -- it's certainly a lot of work. As for the major "enterprise" distributions that benefit from Greg's work, do we know what else they could be doing in addition to contributing fixes to lessen the burden?<br> <p> -Brad<br> </div> Fri, 27 Aug 2010 21:21:25 +0000 Some numbers and thoughts on the stable kernels https://lwn.net/Articles/402575/ https://lwn.net/Articles/402575/ flewellyn <div class="FormattedComment"> Linus was certainly right about one thing: there are indeed people who claim that Greg KH is a dickhead and worse, on a weekly basis. Such comments are as productive as one might expect.<br> </div> Fri, 27 Aug 2010 20:38:45 +0000