linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Dave Jones <davej@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Pekka Enberg <penberg@kernel.org>,
	Christoph Lameter <cl@linux.com>, linux-mm <linux-mm@kvack.org>
Subject: Re: slub error in fs/sysfs/bin.c related code
Date: Thu, 28 Feb 2013 08:27:35 -0800	[thread overview]
Message-ID: <20130228162735.GB26013@kroah.com> (raw)
In-Reply-To: <512F7FEE.2090803@oracle.com>

On Thu, Feb 28, 2013 at 11:03:58AM -0500, Sasha Levin wrote:
> Hi Greg,
> 
> While fuzzing with trinity inside a KVM tools guest, running latest -next kernel
> I got the following spew.
> 
> The open() and release() callbacks in the traces below point to fs/sysfs/bin.c.

Any hint as to which sysfs binary file you were accessing when this
happened?

> [  719.288925] =============================================================================
> [  719.290663] BUG kmalloc-4096 (Tainted: G        W   ): Redzone overwritten
> [  719.291764] -----------------------------------------------------------------------------
> [  719.291764]
> [  719.294527] Disabling lock debugging due to kernel taint
> [  719.294527] INFO: 0xffff88006d1a5520-0xffff88006d1a5520. First byte 0x0 instead of 0xcc
> [  719.294527] INFO: Allocated in open+0xb8/0x190 age=18922 cpu=1 pid=7095
> [  719.294527] 	__slab_alloc+0x622/0x6d0
> [  719.294527] 	kmem_cache_alloc_trace+0x123/0x2c0
> [  719.294527] 	open+0xb8/0x190
> [  719.294527] 	do_dentry_open+0x229/0x330
> [  719.294527] 	finish_open+0x54/0x70
> [  719.294527] 	do_last+0x56c/0x790
> [  719.294527] 	path_openat+0xbe/0x490
> [  719.294527] 	do_filp_open+0x44/0xa0
> [  719.294527] 	do_sys_open+0x133/0x1d0
> [  719.294527] 	sys_open+0x1c/0x20
> [  719.294527] 	tracesys+0xdd/0xe2
> [  719.294527] INFO: Freed in seq_release+0x18/0x30 age=18947 cpu=0 pid=31203
> [  719.294527] 	__slab_free+0x3c/0x590
> [  719.294527] 	kfree+0x2cb/0x2e0
> [  719.294527] 	seq_release+0x18/0x30
> [  719.294527] 	single_release+0x24/0x40
> [  719.294527] 	proc_reg_release+0xed/0x110
> [  719.294527] 	__fput+0x122/0x2d0
> [  719.294527] 	____fput+0x9/0x10
> [  719.294527] 	task_work_run+0xbe/0x100
> [  719.294527] 	do_notify_resume+0x7e/0xa0
> [  719.294527] 	int_signal+0x12/0x17
> [  719.294527] INFO: Slab 0xffffea0001b46800 objects=7 used=7 fp=0x          (null) flags=0x1ffc0000004081
> [  719.294527] INFO: Object 0xffff88006d1a4520 @offset=17696 fp=0x          (null)

Hm, where is sysfs in this traceback?  I don't see it mentioned anywhere
in this report, what am I missing?

thanks,

greg k-h

--
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>

  reply	other threads:[~2013-02-28 16:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-28 16:03 Sasha Levin
2013-02-28 16:27 ` Greg Kroah-Hartman [this message]
2013-02-28 17:00   ` Sasha Levin

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=20130228162735.GB26013@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=cl@linux.com \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=penberg@kernel.org \
    --cc=sasha.levin@oracle.com \
    /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