Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759548AbYJINgT (ORCPT ); Thu, 9 Oct 2008 09:36:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758114AbYJINgJ (ORCPT ); Thu, 9 Oct 2008 09:36:09 -0400 Received: from ey-out-2122.google.com ([74.125.78.25]:7404 "EHLO ey-out-2122.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758103AbYJINgJ (ORCPT ); Thu, 9 Oct 2008 09:36:09 -0400 Message-ID: Date: Thu, 9 Oct 2008 15:36:07 +0200 From: "Kay Sievers" To: "Arkadiusz Miskiewicz" Subject: Re: loading ipmi_watchdog causes tons of other watchdog modules to be loaded Cc: linux-kernel@vger.kernel.org In-Reply-To: <200810091348.19828.a.miskiewicz@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200810091348.19828.a.miskiewicz@gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 715 Lines: 19 On Thu, Oct 9, 2008 at 1:48 PM, Arkadiusz Miskiewicz 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. Kay -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/