Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] stable kernel process automation and improvement

Mark Brown
2019-07-08T15:27:45Z

[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]

On Mon, Jul 08, 2019 at 05:06:41PM +0200, Greg KH wrote:
> On Mon, Jul 08, 2019 at 03:50:45PM +0100, Mark Brown wrote:
> > On Mon, Jul 08, 2019 at 07:05:44AM -0700, Guenter Roeck wrote:

> > > I for my part will most definitely report any such problems, since each
> > > regression in stable releases is used as argument against merging
> > > stable releases (even if the regression rate is negligible), and I am
> > > very interested in getting that regression rate as close to zero as
> > > possible. Reporting each and every regression is an essential part
> > > of that.

> > Me too - but I'm pretty sure for example most of the product
> > teams I've worked with at consumer electronics companies would
> > never even consider it.

> Sweet, want me to come into those teams and give a presentation like I
> did a few months ago for one major company entitled "all the ways your
> kernel is insecure and trivial to break"?

Go wild! Note that this isn't a case of people not taking
updates, it's often a combination of a general confidentiality
mindset and the fact that if you're taking updates from multiple
sources (eg, LTS and one or more chip vendors) as well as making
your own changes it can be more trouble than it's worth to figure
out where to report anything.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]