On Tue, Apr 30, 2019 at 12:05:09PM -0600, Keith Busch wrote: > On Tue, Apr 30, 2019 at 11:11:51AM -0500, Bjorn Helgaas wrote: > > > I'm not convinced a revert is the best call. > > > > I have very limited options at this stage of the release, but I'd be > > glad to hear suggestions. My concern is that if we release v5.1 > > as-is, we'll spend a lot of energy on those false positives. > > May be too late now if the revert is queued up, but I think this feature > should have been a default 'false' Kconfig bool rather than always on. Good idea, this would seem to be a less harsh solution than a revert. Enabling the feature by default for everyone was probably overly confident. I recall I did bring up in a review comment that all other port services have a Kconfig option. Alex replied that he's not using one because on device enumeration, downtraining is checked unconditionally as well. Bandwidth notification might be a feature that's not used by many operating systems. Such features don't get much real world exposure or aren't even validated by manufacturers. Inevitably, unpleasant side effects occur once Linux supports them. However if we keep the code and default to "N" in Kconfig, at least people get a chance to test and validate the functionality and hopefully this will lead to either better hardware or better driver support in the future. Thanks, Lukas
