netdev - Re: flexcan introduced a DIV/0 in kernel

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: <YHBWKzZyuUhMr0fj@kroah.com>
Date:   Fri, 9 Apr 2021 15:27:07 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Marc Kleine-Budde <mkl@...gutronix.de>
Cc:     Koen Vandeputte <koen.vandeputte@...ymesh.com>,
        linux-can@...r.kernel.org, wg@...ndegger.com,
        netdev@...r.kernel.org, qiangqing.zhang@....com
Subject: Re: flexcan introduced a DIV/0 in kernel

On Fri, Apr 09, 2021 at 03:10:01PM +0200, Marc Kleine-Budde wrote:
> On 09.04.2021 14:55:59, Koen Vandeputte wrote:
> > 
> > On 09.04.21 13:21, Marc Kleine-Budde wrote:
> > > On 4/9/21 12:18 PM, Koen Vandeputte wrote:
> > > > Hi All,
> > > > 
> > > > I just updated kernel 4.14 within OpenWRT from 4.14.224 to 4.14.229
> > > > Booting it shows the splat below on each run. [1]
> > > > 
> > > > 
> > > > It seems there are 2 patches regarding flexcan which were introduced in
> > > > 4.14.226
> > > > 
> > > > --> ce59ffca5c49 ("can: flexcan: enable RX FIFO after FRZ/HALT valid")
> > > > --> bb7c9039a396 ("can: flexcan: assert FRZ bit in flexcan_chip_freeze()")
> > > > 
> > > > Reverting these fixes the splat.
> > > This patch should fix the problem:
> > > 
> > > 47c5e474bc1e can: flexcan: flexcan_chip_freeze(): fix chip freeze for missing
> > > bitrate
> > > 
> > > Greg, can you pick this up for v4.14?
> > > 
> > > regards,
> > > Marc
> > > 
> > Checking kernels 4.4 & 4.9 shows that this fix is also missing over there.
> > 
> > Marc,
> > Can you confirm that it's also required for these?
> 
> ACK, the fix is needed for v4.4.265 and v4.9.265.

Now queued up there too, thanks!

greg k-h