mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Maneesh Soni <maneesh@in.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	axobe@in.ibm.com, Rusty <rusty@rustcorp.com.au>
Subject: Re: rd.o module refcount problem
Date: Thu, 29 May 2003 11:35:19 +0100	[thread overview]
Message-ID: <20030529113519.B18348@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030529102510.GA1251@in.ibm.com>; from maneesh@in.ibm.com on Thu, May 29, 2003 at 03:55:10PM +0530

On Thu, May 29, 2003 at 03:55:10PM +0530, Maneesh Soni wrote:
> The module ref count for rd.o module is not adjusted and remains 1 while
> doing the following things. 
> 
> [root@llm01 mod]# insmod /sdb/linux-2.5.70/drivers/block/rd.o
> [root@llm01 mod]# lsmod
> Module                  Size  Used by
> rd                      5568  0 - Live 0xf88b5000
> [root@llm01 mod]# mkfs -t ext2 /dev/ram0
> .
> .
> [root@llm01 mod]# lsmod
> Module                  Size  Used by
> rd                      5568  1 - Live 0xf88b5000
> 
> mount/umount of /dev/ram0 does not change the rd.o module ref count. 
> 
> So, who is supposed to release the rd.o module gracefully? 
> Also mount /dev/ram0 should hold a ref and umount should release the same.
> 
> Same test on 2.4.20 looks correct and mount increments the ref count and
> umount decrements the ref count.

I think you'll find you have to tell the ramdisk to invalidate its contents
before the module count drops.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


      reply	other threads:[~2003-05-29 10:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-29 10:25 Maneesh Soni
2003-05-29 10:35 ` Russell King [this message]

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=20030529113519.B18348@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=axobe@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maneesh@in.ibm.com \
    --cc=rusty@rustcorp.com.au \
    /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®