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]
Date:   Fri, 27 Nov 2020 11:16:01 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     Marc Kleine-Budde <mkl@...gutronix.de>
Cc:     netdev@...r.kernel.org, davem@...emloft.net,
        linux-can@...r.kernel.org, kernel@...gutronix.de
Subject: Re: pull-request: can 2020-11-27

On Fri, 27 Nov 2020 11:02:55 +0100 Marc Kleine-Budde wrote:
> The first patch is by me and target the gs_usb driver and fixes the endianess
> problem with candleLight firmware.
> 
> Another patch by me for the mcp251xfd driver add sanity checking to bail out if
> no IRQ is configured.
> 
> The next three patches target the m_can driver. A patch by me removes the
> hardcoded IRQF_TRIGGER_FALLING from the request_threaded_irq() as this clashes
> with the trigger level specified in the DT. Further a patch by me fixes the
> nominal bitiming tseg2 min value for modern m_can cores. Pankaj Sharma's patch
> add support for cores version 3.3.x.
> 
> The last patch by Oliver Hartkopp is for af_can and converts a WARN() into a
> pr_warn(), which is triggered by the syzkaller. It was able to create a
> situation where the closing of a socket runs simultaneously to the notifier
> call chain for removing the CAN network device in use.

Pulled, thanks!

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ