linux-kernel - [RFC PATCH 0/3] mips: ralink: mt7621: fix too-early kzalloc

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-next>] [day] [month] [year] [list]

Message-Id: <20221103050538.1930758-1-git@johnthomson.fastmail.com.au>
Date:   Thu,  3 Nov 2022 15:05:35 +1000
From:   John Thomson <git@...nthomson.fastmail.com.au>
To:     Sergio Paracuellos <sergio.paracuellos@...il.com>,
        Arınç ÜNAL <arinc.unal@...nc9.com>,
        John Crispin <john@...ozen.org>,
        Thomas Bogendoerfer <tsbogend@...ha.franken.de>
Cc:     linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [RFC PATCH 0/3] mips: ralink: mt7621: fix too-early kzalloc

ralink mt7621 attempts to use kzalloc before normal memory management is
available.
Before v6.1-rc1, mt7621.c soc_dev_init silently failed to kzalloc and
returned in soc_dev_init, but continued to boot without the soc device
registered.
After, kernel crashes before it outputs any console messages

This was bisected to an mm/slub change (detailed in patch 3)

RFC due to
- probably a (much) better way to do this
- do not have mt7621 device with PCIe to test
  drivers/phy/ralink/phy-mt7621-pci.c
- should this reference a commit as Fixes?