From: Chandan Rajendra <chandan@linux.vnet.ibm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-xfs@vger.kernel.org, "Darrick J . Wong" <darrick.wong@oracle.com>
Subject: Re: slab corruption in generic/388
Date: Thu, 21 Sep 2017 18:55:13 +0530 [thread overview]
Message-ID: <2217708.1p8Y42FqGG@localhost.localdomain> (raw)
In-Reply-To: <20170920145740.GA9685@infradead.org>
On Wednesday, September 20, 2017 8:27:40 PM IST Christoph Hellwig wrote:
> Recently I've a few of these warnings in generic/388 with a 4k
> filesystem on x86_64, v5 file system with reflink and rmap
> enabled but otherwise defaults. If someones got and idea where
> this might be from I'm curious, otherwise I'll add it to my TODO list.
I am able to recreate it on my ppc64 box as well. I will root cause the issue
and fix it.
=============================================================================
BUG xfs_rui_item (Tainted: G B ): Poison overwritten
-----------------------------------------------------------------------------
INFO: 0xc000000105d15f0b-0xc000000105d15f0b. First byte 0x6a instead of 0x6b
INFO: Allocated in .kmem_zone_alloc+0xcc/0x180 age=64 cpu=0 pid=2189
.__slab_alloc+0x24/0x50
.kmem_cache_alloc+0x124/0x350
.kmem_zone_alloc+0xcc/0x180
.xfs_rui_init+0x3c/0xe0
.xfs_rmap_update_create_intent+0x34/0x120
.xfs_defer_intake_work+0x64/0x1d0
.xfs_defer_finish+0xa4/0x5b0
.xfs_iomap_write_allocate+0x1cc/0x420
.xfs_map_blocks+0x2c4/0x490
.xfs_do_writepage+0x408/0x830
.write_cache_pages+0x270/0x5f0
.xfs_vm_writepages+0xe8/0x140
.do_writepages+0x44/0xd0
.__writeback_single_inode+0x5c/0x550
.writeback_sb_inodes+0x2b8/0x580
.__writeback_inodes_wb+0xd4/0x140
INFO: Freed in .xfs_rui_item_free+0x28/0x60 age=64 cpu=0 pid=2189
.kmem_cache_free+0x118/0x2a0
.xfs_rui_item_free+0x28/0x60
.xfs_trans_free_items+0xd4/0x160
.__xfs_trans_commit+0xc8/0x350
.xfs_trans_roll+0x44/0x80
.xfs_defer_trans_roll+0x6c/0x240
.xfs_defer_finish+0xb0/0x5b0
.xfs_iomap_write_allocate+0x1cc/0x420
.xfs_map_blocks+0x2c4/0x490
.xfs_do_writepage+0x408/0x830
.write_cache_pages+0x270/0x5f0
.xfs_vm_writepages+0xe8/0x140
.do_writepages+0x44/0xd0
.__writeback_single_inode+0x5c/0x550
.writeback_sb_inodes+0x2b8/0x580
.__writeback_inodes_wb+0xd4/0x140
INFO: Slab 0xf000000000417440 objects=65 used=65 fp=0x (null) flags=0x3ffff800000100
INFO: Object 0xc000000105d15e88 @offset=24200 fp=0xc000000105d19998
Redzone c000000105d15e80: bb bb bb bb bb bb bb bb ........
Object c000000105d15e88: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk
Object c000000105d15e98: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk
Object c000000105d15ea8: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk
Object c000000105d15eb8: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b kkkkkkkkkkkkkkkk
--
chandan
prev parent reply other threads:[~2017-09-21 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 14:57 slab corruption in generic/388 Christoph Hellwig
2017-09-20 19:37 ` Darrick J. Wong
2017-09-21 13:25 ` Chandan Rajendra [this message]
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=2217708.1p8Y42FqGG@localhost.localdomain \
--to=chandan@linux.vnet.ibm.com \
--cc=darrick.wong@oracle.com \
--cc=hch@infradead.org \
--cc=linux-xfs@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 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.