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: <CALaQ_hqHwBKFBFPyantgr59SDpfZHwJFyWimLAZROdDsvA6rwQ@mail.gmail.com>
Date: Mon, 1 Apr 2024 15:46:52 -0500
From: Nathan Royce <nroycea+kernel@...il.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: LKML <linux-kernel@...r.kernel.org>
Subject: Re: Allmodconfig - logic_outb - Boot Panic

Yup. I just figured linux would gracefully handle these sorts of
issues (eg. notify the caller, for them to handle, or just do
nothing).
"ISAPNP" was one of the small handful of things I had to disable from
"allmodconfig" before I could get it to boot.
The latest (and last) was "DEBUG_TEST_DRIVER_REMOVE". I had to add
"dump_stack()" in "__kernfs_remove"" in "fs/kernfs/dir.c" because I
couldn't understand why I was getting other hardware panics for
hardware that DID exist.
So while I wanted "everything under the sun", which "allmodconfig"
delivered, it also delivered things that simply made booting
impossible.
One other requirement for "allmodconfig" is making sure the FS that
root exists on is enabled ('Y', not 'M') for it (common-sense mention
for anyone searching for "allmodconfig" issues).

On Fri, Mar 29, 2024 at 9:46 PM Andrew Morton <akpm@...ux-foundation.org> wrote:
> Could be that the logic_pio driver is crashing when the hardware isn't there.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ