February 2017 - openSUSE Kernel - openSUSE Mailing Lists

[opensuse-kernel] need dracut rescue shell howto?
by Felix Miata 18 Feb '17

18 Feb '17

I have TW 4.8.14 kernel that cannot be booted normally due to failure to mount / filesystem, even after multiple builds of initrd for it. systemctl status systemd-modules-load.service reports process 141 failed. I want to collect /run/initramfs/rdsosreport.txt, but apparently the initrd and kernel are too broken for the dracut shell to work with. Trying to mount FAT floppy I get unknown filesystem type VFAT. Trying to mount USB stick, there are no /dev/sdg devices that could be mounted. /dev/sdb exists, as do /dev/sda3 for all existing HD partitions, but no /dev/sdb#s. / filesystem label 2st11ostw is found on device ST3200822AS according to rdsosreport, but apparently there is no driver that understands this from kernel cmdline: root=LABEL=2st11ostw 4.8.14 kernel/initrd boots normally if root= is omitted from cmdline, or if root=/dev/sda11 is substituted. Prior and 4.9.9 kernels all boot normally with root=LABEL=2st11ostw on cmdline. Is there a dracut rescue shell HOWTO for openSUSE somewhere? I'm having no luck finding one. Nothing it shell's help command seems of any use here either. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

2 2

[opensuse-kernel] 42.2: panic @ [0.2.64013] with kernel-default-4.4.46-11.1
by Felix Miata 16 Feb '17

16 Feb '17

DWARF2 unwinder stuck at ret_from_fork+0x3f/0x70 Leftover inexact backtrace: ... Kernel panic - not syncing: Attempted to kill init! exitcode=0x00 I removed and reinstalled 4.4.46 twice after initial installation. Same result each time. The panic message can be discovered only by leaving vga=791 off cmdline. With it, screen stays black and reset button is required to recover. Kernels 4.4.27 & 4.4.36 still work as expected. Fresh kernel on 42.1 on same PC also works as expected. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/

2 4

[opensuse-kernel] [PATCH] rpm/find-requires: only do KMP dependency generation if there are KMPs
by Stefan Brüns 13 Feb '17

13 Feb '17

If *-kmp-modules does not exist, shortcut the dependency generation, and avoid spamming the buildlog. --- rpm/find-requires | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/rpm/find-requires b/rpm/find-requires index a656f2b4d0..2d6ac6166f 100644 --- a/rpm/find-requires +++ b/rpm/find-requires @@ -10,6 +10,14 @@ package_name=$1 version_release=$2 builddir=$3 +shopt -s nullglob + +kmpmodules="$builddir"/*-kmp-modules +if test -z $kmpmodules; then + cat | /usr/lib/rpm/find-requires "$package_name" + exit $? +fi + trap 'rm -f "$filelist"' EXIT filelist=$(mktemp -t ${0##*/}.XXXXXXXXXX) cat >"$filelist" -- 2.11.0 -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

3 3

[opensuse-kernel] Yama LSM
by Michael Hofmann 01 Feb '17

01 Feb '17

Hello, I've noticed that OpenSUSE currently doesn't enable the Yama security module. The ptrace_scope restriction provided by this module is a valuable security feature for most systems, so I'd like to propose to enable the Yama LSM in the future. This topic has already been discussed in 2014¹, but apparently without conclusive results. Not mentioned back then was that, since kernel 3.7, Yama stacks automatically with major security modules. In other words, coexistence with AppArmor should not be a problem in current versions - as shown by Ubuntu which uses both. Thoughts? ¹ http://lists.opensuse.org/opensuse-kernel/2014-07/msg00077.html -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org

1 0