| 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
| ||
|
Message-ID: <CAJtEV7ZsOd=c6_+A3W+NYBtrWAUPH7NrVEk-J+_+ZgoJQTBZVg@mail.gmail.com> Date: Tue, 12 Mar 2013 09:14:03 +0800 From: Andrew Cooks <acooks@...il.com> To: Jason Baron <jbaron@...hat.com> Cc: open list <linux-kernel@...r.kernel.org> Subject: Bug involving dynamic_debug and '-p' modifier Hi Jason When I specify a '-p' modifier in the dynamic debug options in the kernel command line, I get a kernel panic during boot. The panic happens after userspace starts doing graphical stuff, but I haven't been able to pinpoint exactly what. If I use '=_' instead of '-p', or boot to a recovery mode, or change the modifier after booting using debugfs, the panic doesn't occur. For example, booting to runlevel 3 with '=_', then flipping the same modifier to first to '+p' and then to '-p', before starting X does not result in a panic. Booting to runlevel 3 (or even 1!), with '-p' results in a panic, but 'rdshell' is OK. I also tried the Red Hat kernel (just because it's installed - I haven't figured out how to tell the package manager that I don't want a kernel). This also panics, but it says that '-p' is not supported. Please let me know if you need me to do any other tests. '-p', panic: http://pastebin.com/8yAcBQdY '-p', rdshell, no panic: http://pastebin.com/Hi2a7BZA -- a. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists