linux-kernel - Re: [PATCH] allow kernel module exclusion on load

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID:  <1216096.ezegMODXOY@yoush.homelinux.org>
Date:	Sun, 13 May 2007 21:05:34 +0400
From:	"Nikita V. Youshchenko" <yoush@...ian.org>
To:	linux-kernel@...r.kernel.org
Subject:  Re: [PATCH] allow kernel module exclusion on load

> On Sun, 13 May 2007 16:25:17 +0300
> Dan Aloni <da-x@...atomic.org> wrote:
> 
>> Kernel developers might find it useful for quickly getting out from some
>> rough debugging scenarios.
>> 
>> Signed-off-by: Dan Aloni <da-x@...atomic.org>
>> 
> 
> There is already the modprobe blacklist ability in user space.

I guess the patch being discussed could still save some time for people who
try or debug a new kernel and find that certain module crashes it. Yes it
is possible to boot to old kernel, then blacklist something, then
regenerate initramfs, etc etc, and then undo all that.

Compared to that, adding a boot arg to kernel being debugged is *much* more
convinient.

Just my 2c.

-
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/