From: Keith Owens <kaos@ocs.com.au>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'devfs@oss.sgi.com'" <devfs@oss.sgi.com>
Subject: Re: Inexplicable disk activity trying to load modules on devfs
Date: Thu, 27 Jun 2002 08:03:09 +1000 [thread overview]
Message-ID: <19231.1025128989@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Tue, 25 Jun 2002 23:38:48 -0400." <200206260338.g5Q3cmc19214@mobilix.ras.ucalgary.ca>
On Tue, 25 Jun 2002 23:38:48 -0400,
Richard Gooch <rgooch@ras.ucalgary.ca> wrote:
>Daniel Jacobowitz writes:
>> For the curious, the reason is that modprobe writes even failed
>> attempts to a log in /var/log/ksymoops, and calls fdatasync() on
>> that file afterwards. There is no way to disable this without
>> removing that directory, as a design decision. I don't personally
>> see the point in logging attempts which fail because there is no
>> driver...
>
>Sounds like the behaviour of modprobe needs to be fixed.
People wanted to know what was invoking modprobe and with what
parameters, especially for failed attempts. The call to fdatasync() is
to "ensure" that the log data hits the disk _before_ the module is
loaded, otherwise debugging data is lost if the module init routine
oopses.
next prev parent reply other threads:[~2002-06-26 22:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-17 6:59 Borsenkow Andrej
2002-06-17 15:01 ` Daniel Jacobowitz
2002-06-26 3:38 ` Richard Gooch
2002-06-26 22:03 ` Keith Owens [this message]
2002-07-19 0:22 ` Richard Gooch
2002-06-26 3:37 ` Richard Gooch
-- strict thread matches above, loose matches on Subject: below --
2002-06-15 22:22 Daniel Jacobowitz
2002-06-15 22:44 ` Andrew Morton
2002-06-15 23:04 ` Daniel Jacobowitz
2002-06-18 17:05 ` Rob Landley
2002-06-17 10:10 ` bert hubert
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=19231.1025128989@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=devfs@oss.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@ras.ucalgary.ca \
/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®