From: Fengguang Wu <fengguang.wu@intel.com>
To: Feng Tang <feng.tang@intel.com>
Cc: Christoph Lameter <cl@linux.com>,
Trond Myklebust <Trond.Myklebust@netapp.com>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev <netdev@vger.kernel.org>,
penberg@kernel.org, linux-mm@kvack.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
bfields@fieldses.org
Subject: Re: linux-next BUG: held lock freed!
Date: Mon, 2 Jul 2012 13:22:41 +0800 [thread overview]
Message-ID: <20120702052241.GA8476@localhost> (raw)
In-Reply-To: <20120702122858.029946db@feng-i7>
> --- a/mm/slab.c
> +++ b/mm/slab.c
> @@ -3890,7 +3890,7 @@ void kmem_cache_free(struct kmem_cache *cachep, void *objp)
> unsigned long flags;
>
> local_irq_save(flags);
> - debug_check_no_locks_freed(objp, cachep->size);
> + debug_check_no_locks_freed(objp, cachep->object_size);
> if (!(cachep->flags & SLAB_DEBUG_OBJECTS))
> debug_check_no_obj_freed(objp, cachep->object_size);
> __cache_free(cachep, objp, __builtin_return_address(0));
It works! No single error after a dozen reboots :-)
Tested-by: Fengguang Wu <wfg@linux.intel.com>
Thanks,
Fengguang
WARNING: multiple messages have this Message-ID (diff)
From: Fengguang Wu <fengguang.wu@intel.com>
To: Feng Tang <feng.tang@intel.com>
Cc: Christoph Lameter <cl@linux.com>,
Trond Myklebust <Trond.Myklebust@netapp.com>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev <netdev@vger.kernel.org>,
penberg@kernel.org, linux-mm@kvack.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
bfields@fieldses.org
Subject: Re: linux-next BUG: held lock freed!
Date: Mon, 2 Jul 2012 13:22:41 +0800 [thread overview]
Message-ID: <20120702052241.GA8476@localhost> (raw)
In-Reply-To: <20120702122858.029946db@feng-i7>
> --- a/mm/slab.c
> +++ b/mm/slab.c
> @@ -3890,7 +3890,7 @@ void kmem_cache_free(struct kmem_cache *cachep, void *objp)
> unsigned long flags;
>
> local_irq_save(flags);
> - debug_check_no_locks_freed(objp, cachep->size);
> + debug_check_no_locks_freed(objp, cachep->object_size);
> if (!(cachep->flags & SLAB_DEBUG_OBJECTS))
> debug_check_no_obj_freed(objp, cachep->object_size);
> __cache_free(cachep, objp, __builtin_return_address(0));
It works! No single error after a dozen reboots :-)
Tested-by: Fengguang Wu <wfg@linux.intel.com>
Thanks,
Fengguang
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-07-02 5:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 14:54 BUG: No init found on NFSROOT Fengguang Wu
2012-06-26 17:29 ` Fengguang Wu
2012-06-26 17:29 ` Fengguang Wu
2012-06-27 12:23 ` Fengguang Wu
2012-06-27 12:23 ` Fengguang Wu
2012-07-02 2:56 ` linux-next BUG: held lock freed! Fengguang Wu
2012-07-02 3:39 ` Fengguang Wu
2012-07-02 3:39 ` Fengguang Wu
2012-07-02 3:42 ` Fengguang Wu
2012-07-02 3:42 ` Fengguang Wu
[not found] ` <CA++bM2txX2f=SC3r3bwxLcB8CUCuELW-NhytrKW7-07kysfA2A@mail.gmail.com>
2012-07-02 4:28 ` Feng Tang
2012-07-02 4:28 ` Feng Tang
2012-07-02 5:22 ` Fengguang Wu [this message]
2012-07-02 5:22 ` Fengguang Wu
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=20120702052241.GA8476@localhost \
--to=fengguang.wu@intel.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=cl@linux.com \
--cc=feng.tang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=sfr@canb.auug.org.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 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.