From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Banerjee, Debabrata" <dbanerje@akamai.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"dbavatar@gmail.com" <dbavatar@gmail.com>
Subject: Re: kernel BUG at fs/dcache.c:2105 (__d_rehash(): BUG_ON(!d_unhashed(entry)))
Date: Tue, 18 Sep 2012 16:04:08 -0400 [thread overview]
Message-ID: <20120918200408.GC15575@fieldses.org> (raw)
In-Reply-To: <CC7D221C.9882%dbanerje@akamai.com>
On Mon, Sep 17, 2012 at 06:53:16PM -0400, Banerjee, Debabrata wrote:
> Hello, we're seeing this bug quite often (50 per day over 1500 machines,
> however the parent process executes in a few seconds every 4 hours). The
> process should be merging a freshly untar'd directory with ~8500 files in
> it via rename, where most of the files stay the same (but are clobbered by
> rename), on ext2. I'm attempting to isolate the problem in a clean
> environment.
>
> [229978.861098] ------------[ cut here ]------------
> [229978.862013] kernel BUG at fs/dcache.c:2105!
> [229978.862013] invalid opcode: 0000 [#1] SMP
> [229978.873082] CPU 1
>
> [229978.873082]
> [229978.873082] Pid: 11817, comm: xxxxxxxx. Not tainted 3.0.30-3.0.1-amd64
What's 3.0.30-3.0.1? Is this reproduceable with an upstream kernel?
--b.
> #1
> [229978.873082] RIP: 0010:[<ffffffff81139ab2>] [<ffffffff81139ab2>]
> __d_rehash+0x52/0x60
> [229978.873082] RSP: 0018:ffff8800f743dce8 EFLAGS: 00010286
> [229978.873082] RAX: 018721dffc2c27d2 RBX: ffff8800f48ac6c0 RCX:
> 0000000000000013
> [229978.873082] RDX: 000013f61bc3e0c4 RSI: ffffc900002fa850 RDI:
> ffff8800f48ac6c0
> [229978.873082] RBP: ffff8800f743dce8 R08: ffffea0002438868 R09:
> ffffea0002438868
> [229978.873082] R10: ffff8800e39f6fec R11: 0000000000000246 R12:
> ffff8800234e3500
> [229978.873082] R13: ffff8800234e3590 R14: ffff8800f48ac750 R15:
> ffff880076557408
> [229978.873082] FS: 00007fdd33ef96d0(0000) GS:ffff88007fd00000(0063)
> knlGS:00000000f75588c0
> [229978.873082] CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
> [229978.873082] CR2: 00000000f72ed000 CR3: 000000007b884000 CR4:
> 00000000000006e0
> [229978.873082] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
> 0000000000000000
> [229978.873082] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
> 0000000000000400
> [229978.873082] Process xxxxxxxx. (pid: 11817, threadinfo
> ffff8800f743c000, task ffff8800f2bda8c0)
> [229978.873082] Stack:
> [229978.873082] ffff8800f743dd18 ffffffff8113aa6b ffff8800234e3500
> ffff8800f48ac6c0
> [229978.873082] ffff8800f48ac6c0 ffff8800641bda28 ffff8800f743dd38
> ffffffff8113ac3a
> [229978.873082] ffff8800234e3500 0000000000000000 ffff8800f743ddb8
> ffffffff8113224b
> [229978.873082] Call Trace:
> [229978.873082] [<ffffffff8113aa6b>] __d_move+0xbb/0x250
> [229978.873082] [<ffffffff8113ac3a>] d_move+0x3a/0x60
> [229978.873082] [<ffffffff8113224b>] vfs_rename+0x3cb/0x3e0
> [229978.873082] [<ffffffff81130119>] ? __lookup_hash+0xd9/0x160
> [229978.873082] [<ffffffff811345a3>] sys_renameat+0x243/0x260
> [229978.873082] [<ffffffff81169ceb>] ? compat_filldir64+0xab/0xe0
> [229978.873082] [<ffffffff811a72b8>] ? ext2_readdir+0x228/0x2e0
> [229978.873082] [<ffffffff81169c40>] ? compat_filldir+0x100/0x100
> [229978.873082] [<ffffffff81169c40>] ? compat_filldir+0x100/0x100
> [229978.873082] [<ffffffff81136f0a>] ? vfs_readdir+0x9a/0xd0
> [229978.873082] [<ffffffff811345db>] sys_rename+0x1b/0x20
> [229978.873082] [<ffffffff814bd42c>] cstar_dispatch+0x7/0x32
> [229978.873082] Code: e0 fe 48 85 c0 48 89 47 08 74 04 48 89 50 08 48 89
> 72 08 48 83 ca 01 48 89 16 0f ba 36 00 c9 c3 f3 90 48 8b 06 a8 01 75 f7 eb
> be <0f> 0b eb fe 66 2e 0f 1f 84 00 00 00 00 00
> 55 48 89 e5 66 66 66
> [229978.873082] RIP [<ffffffff81139ab2>] __d_rehash+0x52/0x60
> [229978.873082] RSP <ffff8800f743dce8>
> [229979.157156] ---[ end trace f2460e13ceb17f51 ]---
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-09-18 20:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 22:53 kernel BUG at fs/dcache.c:2105 (__d_rehash(): BUG_ON(!d_unhashed(entry))) Banerjee, Debabrata
2012-09-18 20:04 ` J. Bruce Fields [this message]
2012-09-18 20:58 ` Banerjee, Debabrata
2012-09-18 21:23 ` J. Bruce Fields
2012-09-18 22:17 ` Banerjee, Debabrata
2012-09-19 14:07 ` J. Bruce Fields
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=20120918200408.GC15575@fieldses.org \
--to=bfields@fieldses.org \
--cc=dbanerje@akamai.com \
--cc=dbavatar@gmail.com \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).