On Wed, Oct 10, 2018 at 02:11:48PM -0400, Sasha Levin wrote: > On Wed, Oct 10, 2018 at 10:02:19AM -0700, Dmitry Torokhov wrote: > > On Wed, Oct 10, 2018 at 10:29:58AM -0400, Sasha Levin wrote: > > > On Mon, Oct 08, 2018 at 12:20:26PM -0700, Dmitry Torokhov wrote: > > > > Hi Michael, > > > > > > > > On Mon, Oct 8, 2018 at 12:09 PM Michael Schmitz <schmitzmic@xxxxxxxxx> wrote: > > > > > > > > > > Dmitry, > > > > > > > > > > someone on debian-68k reported the bug, which (to me) indicates that the > > > > > code is not just used by me. > > > > > > > > > > Whether or not a functioning Capslock is essential to have? You be the > > > > > judge of that. If you are OK with applying the keymap patch, why not > > > > > this one? > > > > > > > > I have exactly the same concerns about the keymap patch. This all has > > > > not been working correctly for many many years (and it was not broken > > > > in a subtly way as far as I understand, but rather quite obvious). > > > > Thus I do not understand why this belongs to stable release. It is not > > > > a [recent] regression, nor secutiry bug, nor even enabling of new > > > > hardware, that is why I myself did not mark it as stable. > > > > > > > > I still maintain that we pick up for stable too many patches for no > > > > clear benefit. This is similar to the patch for Atmel controllers that > > > > was picked to stable and I asked why, as it is not clear how many > > > > users might be affected (or if the problem the patch was solving was > > > > purely theoretical, or only affecting hardware that is not in > > > > circulation yet). > > > > > > If you belive that a certain piece of code has no actual users, why do > > > you keep it in the upstream kernel to begin with? > > > > Because obviously there are users. Maybe 5 of them, maybe 10. They do > > not follow upstream very closely (otherwise these fixes would have > > appeared in mainline long time ago) but they still exist. And it is not > > hard to keep the driver in if there are not many changes. > > It, similarily, not hard to backport these changes to stable tree > especially if they're in a self-contained driver such as this one. It is easy to backport, but that should not be a criteria. If we backport each end every one patch landing into mainline into stable then "backporting" is trivial. It does mean that it should be done. > > > > > > > I don't think it makes sense to keep something upstream because it might > > > have users, but not backport fixes because there might not have any > > > users. > > > > > > You haven't seen evidence of anyone using/caring about it for a few > > > years? Great! Remove the code and if someone complains we can always > > > revert. This is how all those orphaned archs got removed a few releases > > > back. I'll even submit the patch if you'd like. > > > > > > It doesn't make sense to have "second class citizens" like how you > > > suggested. > > > > Sure does. Look, one of roles of a mantainer is basically a release > > manager. We need to decide what goes into new release, what goes into > > maintenance release, what stays until later milestone. Each release has > > different criteria. With maintenance release you want to minimize the > > disruption while alleviating most recent and critical/high visibility > > issues, IOW you want to get the most bang for your buck. And these > > particular fixes do not give you any bang, none at all. > > > > Same goes for patches that deal with error handling in probe() functions > > that your AUTOSEL scripts like to pick. Yes, they are fixing bugs. But > > show me actually users affected by them? You encounter these issues with > > probe when you do initial device bringup, but once device is stabilized > > probes are expected to succeed. There won't be duplicate sysfs > > attributes, memory will be allocated, and so on. Fixes to remove() might > > be worthwhile if it is a hot-pluggable bus, but otherwise - no. Yes, the > > box may OOPS if someone manually unbind device through sysfs, but the > > solution is no to patch stable kernels, but simply tell user "dont to > > that [yet]". > > > > When selecting a patch for stable ask yourself: "if I do not pick this > > for stable will a distribution be willing to patch this into their > > kernel on their own"? If the answer is "no" it should be pretty strong > > indicator whether a patch belongs to stable or not. > > There is a big difference between distros and the stable trees. Distros > know who their users/customers are, OTOH we have no clue who the users > of stable trees are. > > I think Greg's last estimate was that about 1/3 of the kernels in the > wild are custom based on a kernel.org stable kernel, which means that we > have no visibility as to what they do with the kernel. If you don't know > who your users are, how can you prioritize some subsystems over others? You make a judgement call, based on the data you have. And I think if you want override maintainer decision you need a decent justification, better than "it is easy to backport" or "we do not know if someone might use it". > > I don't think we can do any of that because we don't know who uses the > kernel and what bugs they hit, or don't hit. They should file bugs, report on mailing lists, and so on. If they hit bugs and do not bother to report them anywhere, it is not our problem. They need to be part of community. > This is one of the reasons > we ask everyone to pick everything, if they don't use whatever code we > changed they won't be affected at all. Or there is unexpected behavior change and they are affected. What do you do if users of atakbd adjusted their userspace for the broken kernel map? From my POV it is OK-ish to change in new kernel release, but not in a middle of "stable" series. > > As a trivial example: we run a few kernels with custom configs in > Microsoft. Can you tell which drivers we use and how many machines use > them? Us not showing up in git log doesn't mean we don't use something, > it just means that the stable process works for us. I can tell you that you are not using atakbd ;) Look, if we are talking about Microsoft, what are criteria for changes that are going into "patch tuesday" releases? Is it any random junk that might land on top of the development tree? Or is it just a bit more disciplined? Like Release managers looking at the incoming problem report rates and make a judgement call as to whether pull the fix in or wait for bigger maintenance release? In ChromeOS land it is the latter. Thanks. -- Dmitry
