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] [day] [month] [year] [list]
Message-ID: <20200504101328.GC1551@shell.armlinux.org.uk>
Date:   Mon, 4 May 2020 11:13:28 +0100
From:   Russell King - ARM Linux admin <linux@...linux.org.uk>
To:     Greg KH <greg@...ah.com>
Cc:     Miguel Borges de Freitas <miguelborgesdefreitas@...il.com>,
        stable@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [Patch include request] ARM: dts: imx6qdl-sr-som-ti: indicate
 powering off wifi is safe

On Mon, May 04, 2020 at 11:58:32AM +0200, Greg KH wrote:
> On Fri, May 01, 2020 at 09:23:49PM +0100, Miguel Borges de Freitas wrote:
> > Dear all,
> > 
> > This is a request to backport b7dc7205b2ae6b6c9d9cfc3e47d6f08da8647b10
> > (Arm: dts:  imx6qdl-sr-som-ti: indicate powering off wifi is safe),
> > already in Linus tree
> > (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm/boot/dts/imx6qdl-sr-som-ti.dtsi?h=v5.7-rc3&id=b7dc7205b2ae6b6c9d9cfc3e47d6f08da8647b10)
> > to LTS kernel 5.4 and to stable 5.6.8.
> > 
> > Reasoning:
> > 
> > Changes to the wlcore driver during Kernel 5.x development, made the
> > Cubox-i with the IMX SOM v1.5 (which includes.a TI Wilink 8 wifi
> > chipset) not power the wireless interface on boot leaving it
> > completely unusable. This happens since at least kernel 5.3 (older one
> > I tested) and affects the current stable and LTS latest kernels. The
> > linked commit, already in linux mainline, restores the wifi
> > functionality.
> > 
> > Thanks in advance,
> 
> Now queued up, thanks.

Just be aware that there's a good reason the patch was never marked
with a Fixes: tag - that is because no one seems to know exactly which
commit broke it, and hence it hasn't been clear which stable kernels
it should be backported to.

So, it's good that someone has put up this backport request.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 10.2Mbps down 587kbps up

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ