From: Sasha Levin <levinsasha928@gmail.com>
To: tyhicks <tyhicks@canonical.com>,
"dustin.kirkland" <dustin.kirkland@gazzang.com>
Cc: ecryptfs <ecryptfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: ecryptfs: kernel BUG at fs/ecryptfs/miscdev.c:52
Date: Sat, 26 May 2012 21:39:21 +0200 [thread overview]
Message-ID: <1338061161.4284.16.camel@lappy> (raw)
Hi all,
During fuzzing with trinity inside a KVM guest, using latest linux-next kernel, I've stumbled on the following:
[ 175.995560] ------------[ cut here ]------------
[ 175.996026] kernel BUG at fs/ecryptfs/miscdev.c:52!
[ 175.996026] invalid opcode: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC
[ 175.996026] CPU 3
[ 175.996026] Pid: 7903, comm: trinity-child3 Tainted: G W 3.4.0-next-20120524-sasha #296 Bochs Bochs
[ 175.996026] RIP: 0010:[<ffffffff813e945a>] [<ffffffff813e945a>] ecryptfs_miscdev_poll+0x5a/0x150
[ 175.996026] RSP: 0018:ffff88002d4a3aa8 EFLAGS: 00010282
[ 175.996026] RAX: 00000000ffffffea RBX: ffff88002d4a3b98 RCX: ffff880019d3c348
[ 175.996026] RDX: ffffffff84444140 RSI: 000000000b32e681 RDI: ffff88002d4a3ab0
[ 175.996026] RBP: ffff88002d4a3ad8 R08: cbf7d334712ee681 R09: 0200000000000000
[ 175.996026] R10: 2000000000000000 R11: 3408000000000000 R12: ffff88003d53c000
[ 176.022035] R13: 000000000b32e681 R14: ffff88002d4b059c R15: ffff88003d53c000
165983 iteration[ 176.026020] FS: 00007f0abac73700(0000) GS:ffff880035a00000(0000) knlGS:0000000000000000
[ 176.026020] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
s.
[ 176.026020] CR2: 00000000011750d8 CR3: 0000000039722000 CR4: 00000000000407e0
[ 176.026020] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 176.026020] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 176.026020] Process trinity-child3 (pid: 7903, threadinfo ffff88002d4a2000, task ffff88002d503000)
[ 176.026020] Stack:
[ 176.026020] ffff88002d4b069c ffff880019d3c348 ffff88002d4b069c ffff88002d4b069c
[ 176.026020] ffff88002d4a3b44 ffff88002d4a3b98 ffff88002d4a3b78 ffffffff8124d9bc
[ 176.026020] ffff88002d503000 ffff88002d503000 01ffffff811f5afe 0000000000000000
[ 176.026020] Call Trace:
[ 176.026020] [<ffffffff8124d9bc>] do_poll+0x11c/0x2b0
[ 176.026020] [<ffffffff8124dcbf>] do_sys_poll+0x16f/0x240
[ 176.026020] [<ffffffff8114dfdd>] ? __lock_acquired+0x3d/0x2e0
[ 176.026020] [<ffffffff811fade6>] ? do_wp_page+0x5c6/0x800
[ 176.026020] [<ffffffff811faf73>] ? do_wp_page+0x753/0x800
197143 iteration[ 176.026020] [<ffffffff8197e060>] ? do_raw_spin_unlock+0xd0/0xe0
s.
[ 176.026020] [<ffffffff83249080>] ? _raw_spin_unlock+0x30/0x60
[ 176.026020] [<ffffffff811fafe8>] ? do_wp_page+0x7c8/0x800
[ 176.026020] [<ffffffff8114dfdd>] ? __lock_acquired+0x3d/0x2e0
[ 176.026020] [<ffffffff8198044d>] ? debug_object_activate+0x6d/0x1b0
[ 176.026020] [<ffffffff81980532>] ? debug_object_activate+0x152/0x1b0
[ 176.026020] [<ffffffff8197e060>] ? do_raw_spin_unlock+0xd0/0xe0
[ 176.026020] [<ffffffff8114b4cd>] ? trace_hardirqs_off+0xd/0x10
[ 176.026020] [<ffffffff83249144>] ? _raw_spin_unlock_irqrestore+0x94/0xc0
[ 176.026020] [<ffffffff81980532>] ? debug_object_activate+0x152/0x1b0
[ 176.026020] [<ffffffff819611ee>] ? rb_insert_color+0x9e/0x160
[ 176.026020] [<ffffffff8110c488>] ? __hrtimer_start_range_ns+0x448/0x490
[ 176.026020] [<ffffffff8197e060>] ? do_raw_spin_unlock+0xd0/0xe0
[ 176.026020] [<ffffffff8124df6c>] sys_poll+0x6c/0x100
[ 176.026020] [<ffffffff8324a1f9>] system_call_fastpath+0x16/0x1b
[ 176.026020] Code: 00 00 44 8b 68 24 e8 66 cc e5 01 48 8d 7d d8 48 c7 c2 40 41 44 84 44 89 ee e8 a3 ef ff ff 85 c0 75 09 48 8b 7d
d8 48 85 ff 75 0e <0f> 0b 0f 1f 40 00 eb fe 66 0f 1f 44 00 00 48 83 c7 28 31 f6 e8
[ 176.026020] RIP [<ffffffff813e945a>] ecryptfs_miscdev_poll+0x5a/0x150
[ 176.026020] RSP <ffff88002d4a3aa8>
[ 176.028658] ---[ end trace 8f6ca168297608bd ]---
next reply other threads:[~2012-05-26 19:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-26 19:39 Sasha Levin [this message]
2012-06-07 0:41 ` ecryptfs: kernel BUG at fs/ecryptfs/miscdev.c:52 Sasha Levin
2012-06-13 0:05 ` [PATCH 0/3] eCryptfs: Fix and simplify messaging code Tyler Hicks
2012-06-13 0:05 ` [PATCH 1/3] eCryptfs: Gracefully refuse miscdev file ops on inherited/passed files Tyler Hicks
2012-06-22 17:47 ` Sasha Levin
2012-06-22 17:58 ` Tyler Hicks
2012-06-13 0:05 ` [PATCH 2/3] eCryptfs: Remove unused messaging declarations and function Tyler Hicks
2012-06-13 0:05 ` [PATCH 3/3] eCryptfs: Make all miscdev functions use daemon ptr in file private_data Tyler Hicks
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=1338061161.4284.16.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=dustin.kirkland@gazzang.com \
--cc=ecryptfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tyhicks@canonical.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 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.