kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: john@jjdev.com (John de la Garza)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to prevent a module from unloading when in used
Date: Wed, 16 Jul 2014 09:09:20 -0400	[thread overview]
Message-ID: <20140716130919.GA16611@vega.jjdev.com> (raw)
In-Reply-To: <CAPrYoTFxYAmLybA6wVwkdnvELSkps9upz-SR=kQtfQRPwdKo2w@mail.gmail.com>

On Wed, Jul 16, 2014 at 04:00:18PM +0530, Chetan Nanda wrote:
> A depends on B, so B is automatically loaded when A is loaded.
> B module is also directly being used by the user side code via misc
> interface.
>.
> Now when I am unloading module A, via "modprobe -r A" it is also unloading
> the module B which is being used by the application and resulting in the
> kernel crash.

You said that A depends on B, right?  Why do you have A dependng on B?
If it A needs to have B then it makes sense that you can not remove A while
B is in use.  If A doesn't need B, why not remove the dependency.

  reply	other threads:[~2014-07-16 13:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAPrYoTHfEqU_8QRJKzY3gwF50JHB_b+QRc=u9MCM_A+mAsRw1A@mail.gmail.com>
2014-07-16 10:30 ` How to prevent a module from unloading when in used Chetan Nanda
2014-07-16 13:09   ` John de la Garza [this message]
     [not found]     ` <CAPrYoTHQFqqbskarb6RJjzZdcBiDCSFvc3uZwhOyzi5Y0a82NA@mail.gmail.com>
2014-07-16 15:27       ` Chetan Nanda
2014-07-16 16:21         ` Greg KH
2014-07-18  4:13           ` Chetan Nanda
2014-07-18  4:17             ` Greg KH
2014-07-18  6:29               ` Chetan Nanda
2014-07-21  3:39                 ` Chetan Nanda
2014-07-21  4:22                   ` Greg KH
2014-07-21  4:50                     ` Chetan Nanda
2014-07-21 18:42                       ` Greg KH
2014-07-16 17:10   ` Abhishek Sharma

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=20140716130919.GA16611@vega.jjdev.com \
    --to=john@jjdev.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).