From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to prevent a module from unloading when in used
Date: Mon, 21 Jul 2014 11:42:45 -0700 [thread overview]
Message-ID: <20140721184245.GC572@kroah.com> (raw)
In-Reply-To: <CAPrYoTFuOx6vi1LWqjyENYwmETffRM0y0Q=Kd3trNS4xR6P_qQ@mail.gmail.com>
On Mon, Jul 21, 2014 at 10:20:48AM +0530, Chetan Nanda wrote:
> On Mon, Jul 21, 2014 at 9:52 AM, Greg KH <greg@kroah.com> wrote:
>
> > On Mon, Jul 21, 2014 at 09:09:02AM +0530, Chetan Nanda wrote:
> > > I try to debug the hang when unloading of driver. I am using kernel v3.10
> > > and it hangs in 'wait_for_zero_refcount'.
> > > I checked that this function has been removed in kernel 3.13.
> > > But I am not able to find the patch for this change.
> > >
> > > Is there an easy way to find the patch which cause removal of wait from
> > > module unloading in v3.13.
> >
> > You have the full git tree, it should be very easy to find, you don't
> > need help from me.
> >
> > Hi Greg,
>
> Thanks for your mail,
>
> I have found a thread with the discussion and a patch for removing the
> wait_for_zero_refcount from module unloading, But not able to find this
> patch being merged on v3.13. (have checked all patches between 3.12 and
> 3.13)
> http://www.gossamer-threads.com/lists/linux/kernel/1783584?do=post_view_threaded#1783584
This email tells you the exact name of the patch to search for, and the
files in which it modifies, making it even easier to search for it.
How are you searching the git log that you are not seeing this patch,
which ended up being in the 3.13-rc1 kernel release?
Finding the git commit id is an exercise left for the reader...
greg k-h
next prev parent reply other threads:[~2014-07-21 18:42 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
[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 [this message]
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=20140721184245.GC572@kroah.com \
--to=greg@kroah.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).