From: Jonathan Walsh <jwalsh@atl.lmco.com>
To: linux-c-programming@vger.kernel.org
Subject: Autoloading modules after socket calls.
Date: Mon, 15 Jan 2007 10:01:26 -0500 [thread overview]
Message-ID: <45AB9746.3040503@atl.lmco.com> (raw)
I am not sure how used this list is, but it seemed like a good place to
ask this sort of question. I was wondering if there is a way to have
the kernel autoload a module on a failed call to something that requires
it. For example if I have sctp compiled as a module, but not inserted,
and I make a call to socket() requesting a IPPROTO_SCTP socket it will
fail with EPROTONOSUPPORT. Is there a way in some sort of kernel
configuration of specifying that the sctp module should be swapped in at
this point? I could write code to pick up this error and insert the
module myself, but I was hoping for a way for the kernel to
automatically do it for me.
Thanks,
Jonathan Walsh
Associate Member Engineering Staff
Lockheed Martin Advanced Technology Laboratories
next reply other threads:[~2007-01-15 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-15 15:01 Jonathan Walsh [this message]
2007-01-15 15:43 ` Autoloading modules after socket calls Steve Graegert
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=45AB9746.3040503@atl.lmco.com \
--to=jwalsh@atl.lmco.com \
--cc=linux-c-programming@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;
as well as URLs for NNTP newsgroup(s).