kernel.kexec_load_disabled = 1 ## Disable core dump kernel.core_pattern = |/bin/false ## Disable io_uring ## https://lore.kernel.org/lkml/20230629132711.1712536-1-matteorizzo@google.com/T/ ## https://security.googleblog.com/2023/06/learnings-from-kctf-vrps-42-linux.html kernel.io...
/Linux[root@localhost ~]# ls /etc/init #(inittab切割为多个*.conf文件;事件驱动)control-alt-delete.conf plymouth-shutdown.conf rc.conf rcS-sulogin.conf readahead-disable-services.conf start-ttys.conf init-system-dbus.conf prefdm.conf rcS.conf readahead-collector.conf serial.conf tty.conf kexec...
we were reporting that utimensat() / 320 was skipped as non-existent on x86, when actually the syscall number 320 is kexec_file_load() on x86 . The problem was that syscall NRs are looked up (and correctly passed to libseccomp) as native syscall NRs. But we forgot that when we tried...
+++ b/src/hooks/abrt_harvest_vmcore.py.in @@ -47,10 +47,17 @@ def parse_kdump(): This function parses /etc/kdump.conf to get a path to kdump's dump directory. """ + # default + dump_path = '/var/crash' # filesystem types that can be used by kdump for dumping fs_types...
I've had a version which used syslog module instead of writing to stderr but I've replaced it as the rest of the code uses stderr and I'll be fixing this everywhere due to rhbz#1001139. The question is where should these scripts log by default - to stderr or ...
+ sys.stderr.write("/etc/kdump.conf not readable, using " + "default path '%s'\n" % dump_path) + return dump_path + - please factor out the logging functions from abrt-action-analyze-core script and use it in both scripts