rsbac June 2026

rsbac@rsbac.org

2 participants
4 discussions

Re: Errors on kernel boot
by GOMEZ, Terence 19 Jun '26

19 Jun '26

Hi, This works much better now ! I have been able to correctly boot and log into the system on both machines. However, on some occasions, the login process doesn't start (the logind service times out), so the boot ends with a blinking cursor on a black screen. Of course, there still are the warnings caused by the devtmpfs. Also, how to properly reply to a message on the mailing list ? I tried to use the Reply button but that doesn't help. Terence Gomez Hello again, > > I just pushed some more fixes to 6.18 git. This one should fix the NULL > deref: > commit f78b2c59e54a86b17127523e5a8a22a6e80beaea > aci_data_structures: check for non-null device_p before using it > for FD cache > > The warning traces are harmless, but I will soon look into them again. > Some kernel file systems do not get registered in RSBAC correctly, this > should be located and fixed. > > Your help is appreciated. :) > > Amon. >

3 3

RSBAC Git Web access moved to Github
by Amon Ott 14 Jun '26

14 Jun '26

Due to permanent overload of the rsbac.org server with local Gitweb, I have created shadow repositories at Github. All accesses to https://git.rsbac.org get redirected to the corresponding Github URLs. The Git server at git.rsbac.org remains available and is still the main resource for the latest code. Amon. -- https://www.rsbac.org GnuPG: E25D2F7B0C561382570DB487DC2A69DA870FE7FF 2018-03-20

1 0

Re: Errors on kernel boot
by GOMEZ, Terence 12 Jun '26

12 Jun '26

Hi, Well, now I've got a lot of Oopses with kernel NULL pointer dereferences, which leads to CPU stalls. After a minute, there is a final Oops with a Kernel panic (not appearing in the logs), effectively stopping the boot. Note this is still the config without MAC. Terence Gomez Le ven. 12 juin 2026 à 11:27, Amon Ott via rsbac <rsbac(a)rsbac.org> a écrit : > Hi, > > just pushed a set of fixes to 6.18, the last one adds extra checks to > do_add_mount() and might help. > > Thanks again! > > Amon. > > Am 09.06.26 um 15:35 schrieb GOMEZ, Terence: > > Sure, > > > > I took the same config as before, only disabling CONFIG_RSBAC_MAC in > > the menuconfig. > > I have similar results on the 2 machines : a kernel NULL pointer > > dereference comes up, with a Oops, which then seems to cause a > > deadlock. > > Here are the boot logs. > > > > Le mer. 27 mai 2026 à 16:15, Amon Ott via rsbac <rsbac(a)rsbac.org > > <mailto:rsbac@rsbac.org>> a écrit : > > > > > > Hi Terence, > > > > > > I started looking into this problem, but have not found the reason > yet. > > > Since it seems to crash in the mostly obsolete MAC module code, could > > > you please try without MAC? > > > > > > Amon. > > > > > > Am 22.05.26 um 15:02 schrieb GOMEZ, Terence: > > > > > > > Hi, > > > > > > > > With Jean-Marc Lacroix, we have been trying to enable more options > > than the > > > > default ones for the RSBAC kernel configuration. However, the > > > > configuration we > > > > have come up with does not always boot correctly depending on the > > machine we > > > > install the kernel on. All machines are based on Debian 13, and the > > > > kernels were > > > > launched in softmode, version 6.18.7. > > > > > > > > On the first machine, a Mac Book Pro 2011 (CPU : Intel Core > i5-2415M) > > > > with SysV > > > > init and XFCE, the system comes up properly. > > > > On the second one, a HP Z240 (CPU : Intel Xeon E3-1225) with > > systemd, we > > > > have > > > > first tried the kernel on a Gnome install, where the boot ends up > > with a > > > > "kernel > > > > NULL pointer dereference" and a kernel panic. On the same machine, > > where we > > > > reinstalled a non graphical system, the same kernel configuration > still > > > > produces > > > > the dereference with multiple kernel oops. > > > > On the third one, a Lenovo ThinkStation P520c (CPU : Intel Xeon > > W-2102) with > > > > systemd and no desktop environment, there also is a "kernel NULL > > pointer > > > > dereference" that stops the boot (and is not in the logs), but no > > kernel > > > > panic > > > > is displayed. > > > > > > > > I've appended the config file along with the boot logs. > > > > > > > > Do you have any idea as to why these problems occur ? > > > > > > > > Regards, > > > > > > > > Terence Gomez > > > > > > > > > Amon. > > > > Terence Gomez > > > Amon.

2 1

Errors on kernel boot
by GOMEZ, Terence 12 Jun '26

12 Jun '26

Sure, I took the same config as before, only disabling CONFIG_RSBAC_MAC in the menuconfig. I have similar results on the 2 machines : a kernel NULL pointer dereference comes up, with a Oops, which then seems to cause a deadlock. Here are the boot logs. Le mer. 27 mai 2026 à 16:15, Amon Ott via rsbac <rsbac(a)rsbac.org> a écrit : > Hi Terence, > > I started looking into this problem, but have not found the reason yet. > Since it seems to crash in the mostly obsolete MAC module code, could > you please try without MAC? > > Amon. > > Am 22.05.26 um 15:02 schrieb GOMEZ, Terence: > > > Hi, > > > > With Jean-Marc Lacroix, we have been trying to enable more options than the > > default ones for the RSBAC kernel configuration. However, the > > configuration we > > have come up with does not always boot correctly depending on the machine we > > install the kernel on. All machines are based on Debian 13, and the > > kernels were > > launched in softmode, version 6.18.7. > > > > On the first machine, a Mac Book Pro 2011 (CPU : Intel Core i5-2415M) > > with SysV > > init and XFCE, the system comes up properly. > > On the second one, a HP Z240 (CPU : Intel Xeon E3-1225) with systemd, we > > have > > first tried the kernel on a Gnome install, where the boot ends up with a > > "kernel > > NULL pointer dereference" and a kernel panic. On the same machine, where we > > reinstalled a non graphical system, the same kernel configuration still > > produces > > the dereference with multiple kernel oops. > > On the third one, a Lenovo ThinkStation P520c (CPU : Intel Xeon W-2102) with > > systemd and no desktop environment, there also is a "kernel NULL pointer > > dereference" that stops the boot (and is not in the logs), but no kernel > > panic > > is displayed. > > > > I've appended the config file along with the boot logs. > > > > Do you have any idea as to why these problems occur ? > > > > Regards, > > > > Terence Gomez > > > Amon. Terence Gomez

2 1

2026

2025

2024

2023

rsbac June 2026