mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@mail.ru>
To: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: loading ipmi_watchdog causes tons of other watchdog modules to be loaded
Date: Thu, 09 Oct 2008 22:09:14 +0400	[thread overview]
Message-ID: <20081009180920.05888143D6F1@smtp02.mtu.ru> (raw)
In-Reply-To: <200810091922.24108.a.miskiewicz@gmail.com>

Arkadiusz Miskiewicz wrote:

> On Thursday 09 October 2008, Kay Sievers wrote:
>> On Thu, Oct 9, 2008 at 1:48 PM, Arkadiusz Miskiewicz
>>
>> <a.miskiewicz@gmail.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. 


  reply	other threads:[~2008-10-09 18:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-09 11:48 Arkadiusz Miskiewicz
2008-10-09 13:36 ` Kay Sievers
2008-10-09 17:22   ` Arkadiusz Miskiewicz
2008-10-09 18:09     ` Andrey Borzenkov [this message]
2008-10-09 18:58     ` Kay Sievers
2008-10-09 19:02       ` Arkadiusz Miskiewicz
2008-10-09 19:09         ` Kay Sievers
2008-10-09 20:18           ` Arkadiusz Miskiewicz
2008-10-09 21:37             ` Kay Sievers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081009180920.05888143D6F1@smtp02.mtu.ru \
    --to=arvidjaar@mail.ru \
    --cc=a.miskiewicz@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®