lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180308174754.GA28545@kroah.com>
Date:   Thu, 8 Mar 2018 09:47:54 -0800
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Darren Hart <dvhart@...radead.org>
Cc:     Sasha Levin <Alexander.Levin@...rosoft.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>,
        Santeri Toivonen <santeri.toivonen@...sul.com>
Subject: Re: [PATCH AUTOSEL for 4.9 025/190] platform/x86: asus-nb-wmi: Add
 wapf4 quirk for the X302UA

On Thu, Mar 08, 2018 at 09:39:14AM -0800, Darren Hart wrote:
> On Thu, Mar 08, 2018 at 04:59:01AM +0000, Sasha Levin wrote:
> > From: Santeri Toivonen <santeri.toivonen@...sul.com>
> > 
> > [ Upstream commit f35823619db8bbaa2afea8705f239c3cecb9d22f ]
> > 
> > Asus laptop X302UA starts up with Wi-Fi disabled,
> > without a way to enable it. Set wapf=4 to fix the problem.
> > 
> > Signed-off-by: Santeri Toivonen <santeri.toivonen@...sul.com>
> > Signed-off-by: Darren Hart (VMware) <dvhart@...radead.org>
> > Signed-off-by: Sasha Levin <alexander.levin@...rosoft.com>
> 
> Hi Sasha,
> 
> I'm curious about this AUTOSEL tag, and what about this patch triggered
> its selection?

It's "magic"!  :)

Seriously, it's close to magic, there's a tool that Sasha is using that
takes "machine learning" to match patches that we have not applied in
stable kernels to ones that we have, and try to catch those that we
forgot to tag for the stable tree.  Not all subsystems mark stable
patches, so this is an attempt to catch those fixes that should be
getting backported but are not either because the developer/maintainer
forgot to mark it as such, or because they just never mark those types
of patches.

Sasha has a better write up about how this all works somewhere, and
given that this type of question keeps coming up every other week or so,
I think I need to add it to a FAQ somewhere to point people at to make
it more obvious what is happening.

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ