From: Sasha Levin <Alexander.Levin@microsoft.com> To: Willy Tarreau <w@1wt.eu> Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "ksummit-discuss@lists.linuxfoundation.org" <ksummit-discuss@lists.linuxfoundation.org>, Greg KH <gregkh@linuxfoundation.org> Subject: Re: [Ksummit-discuss] bug-introducing patches Date: Thu, 3 May 2018 17:29:29 +0000 [thread overview] Message-ID: <20180503172926.GQ18390@sasha-vm> (raw) In-Reply-To: <20180503163516.GJ23311@1wt.eu> On Thu, May 03, 2018 at 06:35:16PM +0200, Willy Tarreau wrote: >On Thu, May 03, 2018 at 04:14:57PM +0000, Sasha Levin wrote: >> I tried looking at a few commits that came in on -rc7, and I see quite a >> few cases where a commit was merged to Linus' tree in about 24 hours >> after it was authored. Or maintainers who just wrote it, pushed it in, >> and shipped in to Linus. >> >> I've attached the data I used. The columns are as follows: >> >> 1. Commit ID >> 2. When was it merged >> 3. How many days it spent in -next >> 4. What commit did it fix >> 5. When was that commit merged > >> b6cdbc85234b v4.16-rc7 5 ca254490c8df v4.3 >> 82dd0d2a9a76 v4.16-rc7 5 8f58336d3f78 v4.2 >> 5807b22c9164 v4.16-rc7 5 6c8702c60b88 v4.9 >> f97c3dc3c0e8 v4.16-rc7 5 4c4dbb4a7363 v4.15 >(...) > >I like this (not what was done but the analysis). > >I'd argue that a small part of them there are very likely valid reasons >(really obvious fix, security issue etc) but it seems there are quite a >large number of them here. > >Now I understand what makes me uneasy with what I'm seeing here. As I >mentioned, -rc is for people who want to see bugs before their users. >-rc7 will ensure almost everyone discovers the fix at the same time, >because the next version will be 4.16, the first of a stable release, >the one that users are expected to trust. > >So probably that we have to educate/encourage developers *not* to submit >fixes for old bugs that late in the cycle and to rather wait for the next >version so that it cooks in -rc for a while before hitting users, knowing >that these fixes will be backported to stable anyway once considered valid. > >Just like Greg has its "WTF" script to remind some developers that their >patch is not suited to -stable, I think you could, based on your work, >try to spot regressions introduced by late patches that fall in the >category you've filtered and emit such WTF messages to the original >patch's authors/committers. > >It's important to do it only when these patches cause breakage though, >because we don't want to needlessly delay fixes when they're considered >certain or well tested. Only when they cause trouble. I tried pulling all the fixes that went in 4.17 (so far) for bugs that were introduced as fixes in the v4.16 cycle, I got this list: d65026c6c62e v4.16-rc7 5 6b1e6cc7855b v4.7 d14d2b78090c 63489f8e8211 v4.16-rc6 13 045c7a3f53d9 v4.11-rc6 5df63c2a149a 5dcd8400884c v4.16-rc6 6 0759e552bce7 v4.7 bd28899dd34f 0ef58b0a05c1 v4.16-rc6 6 0cf737808ae7 v4.14 a56d99d71466 7992894c305e 2afc5d61a719 8936ef7604c1 v4.16-rc6 6 6c8702c60b88 v4.9 a957fa190aa9 bbc09e7842a5 v4.16-rc6 6 65a206c01e8e v4.13 3239534a79ee 6a2cf8d3663e v4.16-rc5 12 d64d6c5671db v4.15 6d6340672ba3 859d880cf544 v4.16-rc4 14 b68a68d3dcc1 v4.15 8420f71943ae e39a97353e53 v4.16-rc4 16 2a842acab109 v4.12 cbe095e2b584 a27fd7a8ed38 v4.16-rc4 19 f214f915e7db v4.13 bffd168c3fc5 0f9da844d877 v4.16-rc2 16 28128c61e08e v4.16-rc2 a95b37e20db9 7324f5399b06 v4.16-rc2 19 186b3c998c50 v4.14 51568d69407d e78c637127ee v4.16-rc3 25 187d7967a5ee v4.4 e988867fd774 ca9eee95a2de v4.16-rc3 25 d717f7352ec6 v4.12 e988867fd774 So out of 755 commits, 14 have been fixed, that's about 2% and we're not even done with 4.17. >For me the rule seems simple to understand, every submitter should >think like this late in the cycle : > > "you're sending a patch that is going to be part of a stable kernel > in no more than 2 weeks, possibly affecting all users upgrading to > that kernel if you did something wrong. Are you really certain you > want this patch merged now, that it got sufficient testing and that > it cannot wait for next -rc1 to get broader exposure first ?" > >I'm pretty sure that most of the time it will be "sure I want it now" >and there will be no problem, which is fine as it automatically reduces >the number of bugs in releases. Some may reconsider their submission. >Some may get caught by your automated script if a later commit fixes >an issue introduced by their patch. And there public shaming is the >only option (or maybe only the second time if you really want to be >nice). I'd much prefer to blame this on maintainers. Authors should be able to submit a patch whenever they feel like it, maintainers should only merge a patch in when it's right.
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin via Ksummit-discuss <ksummit-discuss@lists.linuxfoundation.org> To: Willy Tarreau <w@1wt.eu> Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "ksummit-discuss@lists.linuxfoundation.org" <ksummit-discuss@lists.linuxfoundation.org>, Greg KH <gregkh@linuxfoundation.org> Subject: Re: [Ksummit-discuss] bug-introducing patches Date: Thu, 3 May 2018 17:29:29 +0000 [thread overview] Message-ID: <20180503172926.GQ18390@sasha-vm> (raw) In-Reply-To: <20180503163516.GJ23311@1wt.eu> On Thu, May 03, 2018 at 06:35:16PM +0200, Willy Tarreau wrote: >On Thu, May 03, 2018 at 04:14:57PM +0000, Sasha Levin wrote: >> I tried looking at a few commits that came in on -rc7, and I see quite a >> few cases where a commit was merged to Linus' tree in about 24 hours >> after it was authored. Or maintainers who just wrote it, pushed it in, >> and shipped in to Linus. >> >> I've attached the data I used. The columns are as follows: >> >> 1. Commit ID >> 2. When was it merged >> 3. How many days it spent in -next >> 4. What commit did it fix >> 5. When was that commit merged > >> b6cdbc85234b v4.16-rc7 5 ca254490c8df v4.3 >> 82dd0d2a9a76 v4.16-rc7 5 8f58336d3f78 v4.2 >> 5807b22c9164 v4.16-rc7 5 6c8702c60b88 v4.9 >> f97c3dc3c0e8 v4.16-rc7 5 4c4dbb4a7363 v4.15 >(...) > >I like this (not what was done but the analysis). > >I'd argue that a small part of them there are very likely valid reasons >(really obvious fix, security issue etc) but it seems there are quite a >large number of them here. > >Now I understand what makes me uneasy with what I'm seeing here. As I >mentioned, -rc is for people who want to see bugs before their users. >-rc7 will ensure almost everyone discovers the fix at the same time, >because the next version will be 4.16, the first of a stable release, >the one that users are expected to trust. > >So probably that we have to educate/encourage developers *not* to submit >fixes for old bugs that late in the cycle and to rather wait for the next >version so that it cooks in -rc for a while before hitting users, knowing >that these fixes will be backported to stable anyway once considered valid. > >Just like Greg has its "WTF" script to remind some developers that their >patch is not suited to -stable, I think you could, based on your work, >try to spot regressions introduced by late patches that fall in the >category you've filtered and emit such WTF messages to the original >patch's authors/committers. > >It's important to do it only when these patches cause breakage though, >because we don't want to needlessly delay fixes when they're considered >certain or well tested. Only when they cause trouble. I tried pulling all the fixes that went in 4.17 (so far) for bugs that were introduced as fixes in the v4.16 cycle, I got this list: d65026c6c62e v4.16-rc7 5 6b1e6cc7855b v4.7 d14d2b78090c 63489f8e8211 v4.16-rc6 13 045c7a3f53d9 v4.11-rc6 5df63c2a149a 5dcd8400884c v4.16-rc6 6 0759e552bce7 v4.7 bd28899dd34f 0ef58b0a05c1 v4.16-rc6 6 0cf737808ae7 v4.14 a56d99d71466 7992894c305e 2afc5d61a719 8936ef7604c1 v4.16-rc6 6 6c8702c60b88 v4.9 a957fa190aa9 bbc09e7842a5 v4.16-rc6 6 65a206c01e8e v4.13 3239534a79ee 6a2cf8d3663e v4.16-rc5 12 d64d6c5671db v4.15 6d6340672ba3 859d880cf544 v4.16-rc4 14 b68a68d3dcc1 v4.15 8420f71943ae e39a97353e53 v4.16-rc4 16 2a842acab109 v4.12 cbe095e2b584 a27fd7a8ed38 v4.16-rc4 19 f214f915e7db v4.13 bffd168c3fc5 0f9da844d877 v4.16-rc2 16 28128c61e08e v4.16-rc2 a95b37e20db9 7324f5399b06 v4.16-rc2 19 186b3c998c50 v4.14 51568d69407d e78c637127ee v4.16-rc3 25 187d7967a5ee v4.4 e988867fd774 ca9eee95a2de v4.16-rc3 25 d717f7352ec6 v4.12 e988867fd774 So out of 755 commits, 14 have been fixed, that's about 2% and we're not even done with 4.17. >For me the rule seems simple to understand, every submitter should >think like this late in the cycle : > > "you're sending a patch that is going to be part of a stable kernel > in no more than 2 weeks, possibly affecting all users upgrading to > that kernel if you did something wrong. Are you really certain you > want this patch merged now, that it got sufficient testing and that > it cannot wait for next -rc1 to get broader exposure first ?" > >I'm pretty sure that most of the time it will be "sure I want it now" >and there will be no problem, which is fine as it automatically reduces >the number of bugs in releases. Some may reconsider their submission. >Some may get caught by your automated script if a later commit fixes >an issue introduced by their patch. And there public shaming is the >only option (or maybe only the second time if you really want to be >nice). I'd much prefer to blame this on maintainers. Authors should be able to submit a patch whenever they feel like it, maintainers should only merge a patch in when it's right. _______________________________________________ Ksummit-discuss mailing list Ksummit-discuss@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
next prev parent reply other threads:[~2018-05-03 17:29 UTC|newest] Thread overview: 289+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-05-01 16:38 bug-introducing patches Sasha Levin 2018-05-01 16:38 ` [Ksummit-discuss] " Sasha Levin 2018-05-01 19:44 ` Theodore Y. Ts'o 2018-05-01 19:44 ` Theodore Y. Ts'o 2018-05-01 20:00 ` Sasha Levin 2018-05-01 20:00 ` [Ksummit-discuss] " Sasha Levin 2018-05-01 20:33 ` Willy Tarreau 2018-05-01 20:48 ` [Ksummit-discuss] " Willy Tarreau 2018-05-01 20:42 ` Sasha Levin 2018-05-01 20:42 ` [Ksummit-discuss] " Sasha Levin 2018-05-01 20:54 ` Theodore Y. Ts'o 2018-05-01 20:54 ` Theodore Y. Ts'o 2018-05-01 21:15 ` Mark Brown 2018-05-01 21:15 ` Mark Brown 2018-05-02 8:11 ` Daniel Vetter 2018-05-02 8:11 ` Daniel Vetter 2018-05-02 19:46 ` Sasha Levin 2018-05-02 19:46 ` Sasha Levin via Ksummit-discuss 2018-05-03 2:05 ` Mark Brown 2018-05-03 2:05 ` Mark Brown via Ksummit-discuss 2018-05-03 3:10 ` Theodore Y. Ts'o 2018-05-03 3:10 ` Theodore Y. Ts'o 2018-05-03 3:52 ` Guenter Roeck 2018-05-03 3:52 ` Guenter Roeck 2018-05-03 12:03 ` Greg KH 2018-05-03 12:03 ` Greg KH 2018-05-03 22:42 ` Mark Brown 2018-05-03 22:42 ` Mark Brown 2018-05-03 23:09 ` Tony Lindgren 2018-05-03 23:09 ` Tony Lindgren 2018-05-04 14:21 ` Ulf Hansson 2018-05-04 14:21 ` Ulf Hansson 2018-05-09 8:44 ` Mark Brown 2018-05-09 8:44 ` Mark Brown 2018-05-09 8:47 ` Daniel Vetter 2018-05-09 8:47 ` Daniel Vetter 2018-05-09 8:51 ` Geert Uytterhoeven 2018-05-09 8:51 ` Geert Uytterhoeven 2018-05-09 9:03 ` Mark Brown 2018-05-09 9:03 ` Mark Brown 2018-05-09 10:47 ` Stephen Rothwell 2018-05-09 10:47 ` Stephen Rothwell 2018-05-09 10:55 ` Vinod Koul 2018-05-09 10:55 ` Vinod Koul 2018-05-09 12:43 ` Stephen Rothwell 2018-05-09 12:43 ` Stephen Rothwell 2018-05-09 12:47 ` Vinod Koul 2018-05-09 12:47 ` Vinod Koul 2018-05-15 10:42 ` Krzysztof Kozlowski 2018-05-15 10:42 ` Krzysztof Kozlowski 2018-05-15 11:54 ` Stephen Rothwell 2018-05-15 11:54 ` Stephen Rothwell 2018-05-09 14:05 ` Mark Brown 2018-05-09 14:05 ` Mark Brown 2018-05-09 22:09 ` Stephen Rothwell 2018-05-09 22:09 ` Stephen Rothwell 2018-05-10 13:36 ` Mark Brown 2018-05-10 13:36 ` Mark Brown 2018-05-10 22:01 ` Stephen Rothwell 2018-05-10 22:01 ` Stephen Rothwell 2018-05-09 15:57 ` Guenter Roeck 2018-05-09 15:57 ` Guenter Roeck 2018-05-09 21:45 ` Stephen Rothwell 2018-05-09 21:45 ` Stephen Rothwell 2018-05-09 16:04 ` Dan Williams 2018-05-09 16:04 ` Dan Williams 2018-05-09 16:04 ` Dan Williams 2018-05-09 21:51 ` Stephen Rothwell 2018-05-09 21:51 ` Stephen Rothwell 2018-05-09 21:51 ` Stephen Rothwell 2018-05-09 19:35 ` Boris Brezillon 2018-05-09 19:35 ` Boris Brezillon 2018-05-09 21:58 ` Stephen Rothwell 2018-05-09 21:58 ` Stephen Rothwell 2018-05-10 3:15 ` Sasha Levin 2018-05-10 3:15 ` Sasha Levin via Ksummit-discuss 2018-05-10 15:57 ` Tony Lindgren 2018-05-10 15:57 ` Tony Lindgren 2018-05-10 22:05 ` Stephen Rothwell 2018-05-10 22:05 ` Stephen Rothwell 2018-05-11 8:47 ` David Sterba 2018-05-11 8:49 ` David Sterba 2018-05-12 4:03 ` Stephen Rothwell 2018-05-12 4:03 ` Stephen Rothwell 2018-05-12 4:38 ` Stephen Rothwell 2018-05-12 4:38 ` Stephen Rothwell 2018-05-12 18:34 ` Guenter Roeck 2018-05-13 13:53 ` Andy Shevchenko 2018-05-13 13:53 ` Andy Shevchenko 2018-05-14 8:36 ` Ulf Hansson 2018-05-14 8:36 ` Ulf Hansson 2018-05-14 21:45 ` Stephen Rothwell 2018-05-14 21:45 ` Stephen Rothwell 2018-05-17 5:10 ` Mark Brown 2018-05-17 5:10 ` Mark Brown 2018-05-10 16:03 ` Jiri Kosina 2018-05-10 16:03 ` Jiri Kosina 2018-05-10 16:47 ` Sasha Levin 2018-05-10 16:47 ` Sasha Levin via Ksummit-discuss 2018-05-14 7:53 ` Geert Uytterhoeven 2018-05-14 7:53 ` Geert Uytterhoeven 2018-05-14 8:00 ` Geert Uytterhoeven 2018-05-14 8:00 ` Geert Uytterhoeven 2018-05-14 8:12 ` Boris Brezillon 2018-05-14 8:12 ` Boris Brezillon 2018-05-14 8:29 ` Geert Uytterhoeven 2018-05-14 8:29 ` Geert Uytterhoeven 2018-05-14 8:34 ` Boris Brezillon 2018-05-14 8:34 ` Boris Brezillon 2018-05-14 8:40 ` Geert Uytterhoeven 2018-05-14 8:40 ` Geert Uytterhoeven 2018-05-14 8:48 ` Boris Brezillon 2018-05-14 8:48 ` Boris Brezillon 2018-05-14 9:25 ` Fengguang Wu 2018-05-14 9:25 ` Fengguang Wu 2018-05-11 2:10 ` Mark Brown 2018-05-11 2:10 ` Mark Brown 2018-05-08 2:34 ` Sasha Levin 2018-05-08 2:34 ` Sasha Levin 2018-05-08 3:48 ` Theodore Y. Ts'o 2018-05-08 3:48 ` Theodore Y. Ts'o 2018-05-08 14:49 ` Tony Lindgren 2018-05-09 8:13 ` Mark Brown 2018-05-09 8:13 ` Mark Brown 2018-05-10 15:36 ` Tony Lindgren 2018-05-10 15:36 ` Tony Lindgren 2018-05-08 20:29 ` Sasha Levin 2018-05-08 20:29 ` Sasha Levin via Ksummit-discuss 2018-05-08 20:40 ` Matthew Wilcox 2018-05-08 20:40 ` Matthew Wilcox 2018-05-08 20:55 ` Sasha Levin 2018-05-08 20:55 ` Sasha Levin 2018-05-08 20:59 ` David Lang 2018-05-08 21:06 ` David Lang 2018-05-08 21:43 ` Sasha Levin 2018-05-08 21:43 ` Sasha Levin via Ksummit-discuss 2018-05-08 21:51 ` Dan Williams 2018-05-08 21:51 ` Dan Williams 2018-05-08 22:41 ` James Bottomley 2018-05-08 22:41 ` James Bottomley 2018-05-08 21:26 ` Justin Forbes 2018-05-08 21:26 ` Justin Forbes 2018-05-08 21:00 ` Ken Moffat 2018-05-08 21:08 ` Ken Moffat 2018-05-08 22:15 ` Theodore Y. Ts'o 2018-05-10 16:39 ` Sasha Levin 2018-05-09 4:47 ` Willy Tarreau 2018-05-09 4:47 ` Willy Tarreau 2018-05-08 13:58 ` Justin Forbes 2018-05-08 13:58 ` Justin Forbes 2018-05-08 2:39 ` Sasha Levin 2018-05-08 2:39 ` Sasha Levin via Ksummit-discuss 2018-05-01 22:02 ` Sasha Levin 2018-05-01 22:02 ` [Ksummit-discuss] " Sasha Levin 2018-05-02 4:30 ` Willy Tarreau 2018-05-02 4:30 ` [Ksummit-discuss] " Willy Tarreau 2018-05-02 19:42 ` Sasha Levin 2018-05-02 19:42 ` Sasha Levin 2018-05-02 20:02 ` Willy Tarreau 2018-05-02 20:02 ` [Ksummit-discuss] " Willy Tarreau 2018-07-14 17:38 ` Pavel Machek 2018-07-14 17:38 ` Pavel Machek 2018-07-14 18:37 ` [Ksummit-discuss] " Guenter Roeck 2018-07-14 18:37 ` Guenter Roeck 2018-07-14 19:47 ` Pavel Machek 2018-07-14 19:47 ` Pavel Machek 2018-07-14 20:40 ` Guenter Roeck 2018-07-14 20:40 ` Guenter Roeck 2018-07-14 21:09 ` Pavel Machek 2018-07-14 21:09 ` Pavel Machek 2018-07-15 5:57 ` Willy Tarreau 2018-07-15 5:57 ` Willy Tarreau 2018-07-15 8:54 ` Greg KH 2018-07-15 8:54 ` Greg KH 2018-07-15 14:50 ` [Ksummit-discuss] " Theodore Y. Ts'o 2018-07-15 14:50 ` Theodore Y. Ts'o 2018-07-15 20:15 ` [Ksummit-discuss] " Pavel Machek 2018-07-15 20:15 ` Pavel Machek 2018-05-03 11:08 ` [Ksummit-discuss] " Jani Nikula 2018-05-03 11:08 ` Jani Nikula 2018-05-03 14:33 ` James Bottomley 2018-05-03 14:33 ` James Bottomley 2018-05-03 14:48 ` Willy Tarreau 2018-05-03 14:49 ` Willy Tarreau 2018-05-03 15:06 ` Sasha Levin 2018-05-03 15:06 ` Sasha Levin via Ksummit-discuss 2018-05-03 15:27 ` James Bottomley 2018-05-03 15:27 ` James Bottomley 2018-05-03 15:43 ` Sasha Levin 2018-05-03 15:43 ` Sasha Levin via Ksummit-discuss 2018-05-03 17:17 ` Randy Dunlap 2018-05-03 17:17 ` Randy Dunlap 2018-05-03 17:39 ` Sasha Levin 2018-05-03 17:39 ` Sasha Levin via Ksummit-discuss 2018-05-03 18:10 ` James Bottomley 2018-05-03 18:10 ` James Bottomley 2018-05-03 15:56 ` Willy Tarreau 2018-05-03 15:57 ` Willy Tarreau 2018-05-03 18:58 ` Theodore Y. Ts'o 2018-05-03 18:58 ` Theodore Y. Ts'o 2018-05-01 23:28 ` Stephen Rothwell 2018-05-01 23:10 ` Stephen Rothwell 2018-05-02 15:32 ` Geert Uytterhoeven 2018-05-02 15:32 ` Geert Uytterhoeven 2018-05-02 19:51 ` Sasha Levin 2018-05-02 19:51 ` Sasha Levin via Ksummit-discuss 2018-05-02 20:41 ` Geert Uytterhoeven 2018-05-02 20:41 ` Geert Uytterhoeven 2018-05-03 0:06 ` [Ksummit-discuss] " Theodore Y. Ts'o 2018-05-03 0:06 ` Theodore Y. Ts'o 2018-05-03 0:38 ` Guenter Roeck 2018-05-03 0:38 ` Guenter Roeck 2018-05-03 2:30 ` Willy Tarreau 2018-05-03 2:30 ` Willy Tarreau 2018-05-03 14:55 ` Sasha Levin 2018-05-03 14:55 ` Sasha Levin 2018-05-03 15:49 ` Guenter Roeck 2018-05-03 15:49 ` Guenter Roeck 2018-05-03 16:02 ` Sasha Levin 2018-05-03 16:02 ` Sasha Levin via Ksummit-discuss 2018-05-03 16:50 ` Justin Forbes 2018-05-03 16:50 ` Justin Forbes 2018-05-03 17:09 ` Guenter Roeck 2018-05-03 17:09 ` Guenter Roeck 2018-05-03 11:48 ` Al Viro 2018-05-03 14:46 ` Sasha Levin 2018-05-03 14:46 ` Sasha Levin via Ksummit-discuss 2018-05-03 14:52 ` Willy Tarreau 2018-05-03 14:52 ` Willy Tarreau 2018-05-03 15:01 ` Sasha Levin 2018-05-03 15:01 ` Sasha Levin via Ksummit-discuss 2018-05-03 16:00 ` Willy Tarreau 2018-05-03 16:01 ` Willy Tarreau 2018-05-03 16:14 ` Sasha Levin 2018-05-03 16:15 ` Sasha Levin 2018-05-03 16:35 ` Willy Tarreau 2018-05-03 16:35 ` Willy Tarreau 2018-05-03 17:29 ` Sasha Levin [this message] 2018-05-03 17:29 ` Sasha Levin via Ksummit-discuss 2018-05-03 17:57 ` Willy Tarreau 2018-05-03 17:57 ` Willy Tarreau 2018-05-03 18:12 ` Sasha Levin 2018-05-03 18:12 ` Sasha Levin 2018-05-03 18:46 ` Guenter Roeck 2018-05-03 18:46 ` Guenter Roeck 2018-05-03 19:03 ` Willy Tarreau 2018-05-03 19:03 ` Willy Tarreau 2018-05-03 16:54 ` Al Viro 2018-05-03 16:54 ` Al Viro 2018-05-03 17:34 ` Sasha Levin 2018-05-03 17:34 ` Sasha Levin via Ksummit-discuss 2018-05-03 18:20 ` Al Viro 2018-05-03 18:20 ` Al Viro 2018-05-03 18:55 ` Greg KH 2018-05-03 18:55 ` Greg KH 2018-05-03 19:14 ` Willy Tarreau 2018-05-03 19:14 ` Willy Tarreau 2018-05-03 19:17 ` Sasha Levin 2018-05-03 19:17 ` Sasha Levin via Ksummit-discuss 2018-05-03 19:04 ` Sasha Levin 2018-05-03 19:04 ` Sasha Levin 2018-05-04 9:57 ` David Howells 2018-05-04 9:57 ` David Howells 2018-05-04 12:31 ` Jani Nikula 2018-05-04 12:31 ` Jani Nikula 2018-05-04 13:09 ` Theodore Y. Ts'o 2018-05-04 13:09 ` Theodore Y. Ts'o 2018-05-04 17:40 ` Greg KH 2018-05-04 17:40 ` Greg KH 2018-05-04 21:13 ` Theodore Y. Ts'o 2018-05-04 21:13 ` Theodore Y. Ts'o 2018-05-04 21:38 ` James Bottomley 2018-05-04 21:38 ` James Bottomley 2018-05-04 21:51 ` Sasha Levin 2018-05-04 21:51 ` Sasha Levin 2018-05-04 23:35 ` Theodore Y. Ts'o 2018-05-04 23:35 ` Theodore Y. Ts'o 2018-05-05 4:23 ` Willy Tarreau 2018-05-05 4:24 ` Willy Tarreau 2018-05-05 5:02 ` Eric W. Biederman 2018-05-05 5:02 ` Eric W. Biederman 2018-05-05 16:37 ` Greg KH 2018-05-05 16:37 ` Greg KH 2018-05-05 5:27 ` Sasha Levin 2018-05-05 5:27 ` Sasha Levin via Ksummit-discuss 2018-05-03 11:43 ` Al Viro 2018-05-03 11:43 ` Al Viro 2018-05-02 15:32 ` Geert Uytterhoeven 2018-05-02 15:32 ` Geert Uytterhoeven
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20180503172926.GQ18390@sasha-vm \ --to=alexander.levin@microsoft.com \ --cc=gregkh@linuxfoundation.org \ --cc=ksummit-discuss@lists.linuxfoundation.org \ --cc=linux-kernel@vger.kernel.org \ --cc=w@1wt.eu \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.