All of lore.kernel.org
 help / color / mirror / Atom feed
From: Der Herr Hofrat <der.herr@mail.hofr.at>
To: linux-mtd@lists.infradead.org
Subject: mtdram bug - module count incorect
Date: Thu, 9 Jan 2003 18:03:32 +0100 (CET)	[thread overview]
Message-ID: <200301091703.h09H3Wo00632@hofr.at> (raw)

Hi !

 here is how to reproduce the problem - It's due to a mistake I made, I 
 called mkfs.minix on the mounted filesystem - but mkfs.minix exits with
 the proper error still the usage count was increased...

Kernel is 2.4.19-rtl3.2-pre1

# lsmod
Module                  Size  Used by
de4x5                  41104   1  (autoclean)

# insmod mtdcore.o
# insmod mtdram.o total_size=4096 erase_size=128

# dmesg 
mtd: Giving out device 0 to mtdram test device

# lsmod
Module                  Size  Used by
mtdblock                4884   0  (unused)
mtdram                  2068   0  (unused)
mtdcore                 2052   1  [mtdblock mtdram]
de4x5                  41104   1  (autoclean)

# mkfs.minix /dev/mtdblock0
1376 inodes
4096 blocks
Firstdatazone=47 (47)
Zonesize=1024
Maxsize=268966912

# mount -t minix /dev/mtdblock0 /mnt
# df
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/mtdblock0            4049         1      4048   0% /mnt

# lsmod
Module                  Size  Used by
mtdblock                4884   1
mtdram                  2068   1
mtdcore                 2052   1  [mtdblock mtdram]
de4x5                  41104   1  (autoclean)

   I found my mistake in the command history, and it is well reproducable.

# mkfs.minix /dev/mtdblock0
mkfs.minix: %s is mounted; will not make a filesystem here!

# lsmod
Module                  Size  Used by
mtdblock                4884   1 
mtdram                  2068   2   
                              ^^^^
                              wrong module usage count after mkfs.
mtdcore                 2052   1  [mtdblock mtdram]
de4x5                  41104   1  (autoclean)


   The problem is that mkfs.minix on the mounted filesystem increaesed 
   the modules usage count - so I guess this means the MOD_INC_.. is 
   somewhere in the wrong place as it is done in a failure path (or 
   the MOD_DEC is missing...)

   If this is not a known problem I'll give it a try to trak it down.

thx !
hofrat

                 reply	other threads:[~2003-01-09 16:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200301091703.h09H3Wo00632@hofr.at \
    --to=der.herr@mail.hofr.at \
    --cc=linux-mtd@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.