All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: SLUB cifs_request: kmem_cache_destroy called for cache that still has objects.
Date: Tue, 15 May 2012 20:46:42 -0400	[thread overview]
Message-ID: <20120515204642.1a5bedee@corrin.poochiereds.net> (raw)

I saw this today when unplugging cifs.ko in a stock -rc7 kernel. I
never mounted any cifs mounts, so this is entirely due to module
initialization as far as I can tell:

[  464.776843] SLUB cifs_request: kmem_cache_destroy called for cache that still has objects.
[  464.779071] Pid: 4738, comm: rmmod Not tainted 3.4.0-0.rc7.git0.1.fc18.x86_64 #1
[  464.780243] Call Trace:
[  464.780433]  [<ffffffff8116b53a>] kmem_cache_destroy+0x2ba/0x360
[  464.780870]  [<ffffffffa00d6469>] cifs_destroy_request_bufs+0x21/0x3b [cifs]
[  464.781397]  [<ffffffffa00d66a6>] exit_cifs+0x30/0x98a [cifs]
[  464.781944]  [<ffffffff810b4a3e>] sys_delete_module+0x16e/0x2d0
[  464.782482]  [<ffffffff8117c186>] ? filp_close+0x66/0xa0
[  464.782903]  [<ffffffff81603769>] system_call_fastpath+0x16/0x1b

...any ideas?
-- 
Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

             reply	other threads:[~2012-05-16  0:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16  0:46 Jeff Layton [this message]
     [not found] ` <20120515204642.1a5bedee-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2012-05-16  4:00   ` SLUB cifs_request: kmem_cache_destroy called for cache that still has objects Steve French
     [not found]     ` <CAH2r5muoDPbWv5jpK7hkyVAV_EOGoAVUccz86nZsxPy6WyahpQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-05-16  6:11       ` Suresh Jayaraman
     [not found]         ` <4FB3451B.5020704-IBi9RG/b67k@public.gmane.org>
2012-05-16 11:02           ` Jeff Layton

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=20120515204642.1a5bedee@corrin.poochiereds.net \
    --to=jlayton-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.