From: Dave Jones <davej@redhat.com>
To: jack@suse.cz, Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: fanotify use after free.
Date: Wed, 22 Jan 2014 11:43:11 -0500 [thread overview]
Message-ID: <20140122164311.GA26523@redhat.com> (raw)
In-Reply-To: <20140122062730.GA25601@redhat.com>
On Wed, Jan 22, 2014 at 01:27:30AM -0500, Dave Jones wrote:
> Jan,
>
> since yesterdays changes, on boot I see a flood of messages from slub debug during boot..
>
> =============================================================================
> BUG fanotify_event_info (Not tainted): Poison overwritten
> -----------------------------------------------------------------------------
>
> Disabling lock debugging due to kernel taint
> INFO: 0xffff880247e45bc8-0xffff880247e45bcb. First byte 0x0 instead of 0x6b
> INFO: Allocated in fanotify_handle_event+0x136/0x390 age=0 cpu=0 pid=293
> __slab_alloc+0x456/0x565
> kmem_cache_alloc+0x1fe/0x260
> fanotify_handle_event+0x136/0x390
> send_to_group+0xd3/0x1c0
> fsnotify+0x1c8/0x340
> open_exec+0xe2/0x120
> load_elf_binary+0x7b7/0x18e0
> search_binary_handler+0x94/0x1b0
> do_execve_common.isra.26+0x5d7/0x7d0
> SyS_execve+0x36/0x50
> stub_execve+0x69/0xa0
> INFO: Freed in fanotify_free_event+0x2e/0x40 age=0 cpu=3 pid=290
> __slab_free+0x4a/0x382
> kmem_cache_free+0x1c9/0x210
> fanotify_free_event+0x2e/0x40
> fsnotify_destroy_event+0x21/0x30
> fanotify_read+0x39e/0x5e0
> vfs_read+0x9b/0x160
> SyS_read+0x58/0xb0
> tracesys+0xdd/0xe2
> INFO: Slab 0xffffea00091f9100 objects=20 used=20 fp=0x (null) flags=0x20000000004080
Reverting 7053aee26a3548ebaba046ae2e52396ccf56ac6c makes this go away.
Dave
next prev parent reply other threads:[~2014-01-22 16:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 6:27 Dave Jones
2014-01-22 16:43 ` Dave Jones [this message]
2014-01-22 18:20 ` Linus Torvalds
2014-01-22 23:36 ` Jan Kara
2014-01-23 0:08 ` Linus Torvalds
2014-01-23 0:32 ` Dave Jones
2014-01-23 15:05 ` Jan Kara
2014-01-23 10:23 ` Jiri Kosina
2014-01-23 15:05 ` Jan Kara
2014-01-23 15:07 ` Jiri Kosina
2014-01-23 23:55 ` Jan Kara
2014-01-24 7:26 ` Jiri Kosina
2014-01-27 23:40 ` Jan Kara
2014-01-28 6:10 ` Dave Jones
2014-01-28 8:02 ` Jan Kara
2014-01-28 11:07 ` Jiri Kosina
2014-01-28 14:53 ` Jan Kara
2014-01-28 15:24 ` Dave Jones
2014-01-28 10:53 ` Jiri Kosina
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=20140122164311.GA26523@redhat.com \
--to=davej@redhat.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome