| 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: <20081009180920.05888143D6F1@smtp02.mtu.ru> Date: Thu, 09 Oct 2008 22:09:14 +0400 From: Andrey Borzenkov <arvidjaar@...l.ru> To: Arkadiusz Miskiewicz <a.miskiewicz@...il.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: loading ipmi_watchdog causes tons of other watchdog modules to be loaded Arkadiusz Miskiewicz wrote: > On Thursday 09 October 2008, Kay Sievers wrote: >> On Thu, Oct 9, 2008 at 1:48 PM, Arkadiusz Miskiewicz >> >> <a.miskiewicz@...il.com> wrote: >> > No udev on the system. kernel 2.6.25.18-1. >> > >> > After loading ipmi_watchdog and doing "cat /dev/watchdog" tons of >> > other, useles, watchdog modules is loaded. Any idea what introduced >> > such weird behaviour? >> >> I guess the /proc/sys/kernel/modprobe, which lets the kernel fork a >> modprobe process when you touch a "dangling" device node, which does >> not have corresponding driver. > > ... but that ipmi_watchdog is the correct driver that handles > /dev/watchdog, so this shouldn't be happening, correct? > That's true, but it declares itself as handler for this device entry very deep in some callback. It is quite possible that event that would have triggered this callback did not yet happen. -- 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