public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Tinguely <tinguely@sgi.com>
To: Dave Jones <davej@redhat.com>
Cc: CAI Qian <caiqian@redhat.com>, xfs@oss.sgi.com
Subject: Re: xfs_efi_item slab corruption. (v3.9-10936-g51a26ae)
Date: Tue, 07 May 2013 14:58:15 -0500	[thread overview]
Message-ID: <51895CD7.7040806@sgi.com> (raw)
In-Reply-To: <20130507193146.GA7539@redhat.com>

On 05/07/13 14:31, Dave Jones wrote:
> On Tue, May 07, 2013 at 02:24:14PM -0500, Mark Tinguely wrote:
>   >  On 05/07/13 14:07, Dave Jones wrote:
>   >  >  On Tue, May 07, 2013 at 02:04:05PM -0500, Mark Tinguely wrote:
>   >  >    >   On 05/07/13 08:37, Dave Jones wrote:
>   >  >    >   >      172.233570] Bytes b4 ffff8800aaac4e28: 07 a2 fd ff 00 00 00 00 5a 5a 5a 5a 5a 5a 5a 5a  ........ZZZZZZZZ
>   >  >    >   >   [  172.233573] Object ffff8800aaac4e38: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b  kkkkkkkkkkkkkkkk
>   >  >    >   >   [  172.233575] Object ffff8800aaac4e48: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b  kkkkkkkkkkkkkkkk
>   >  >    >   >   [  172.233577] Object ffff8800aaac4e58: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b  kkkkkkkkkkkkkkkk
>   >  >    >   >   [  172.233579] Object ffff8800aaac4e68: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b  kkkkkkkkkkkkkkkk
>   >  >    >   >   [  172.233581] Object ffff8800aaac4e78: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b  kkkkkkkkkkkkkkkk
>   >  >    >   >   [  172.233583] Object ffff8800aaac4e88: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b  kkkkkkkkkkkkkkkk
>   >  >    >   >   [  172.233586] Object ffff8800aaac4e98: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b  kkkkkkkkkkkkkkkk
>   >  >    >   >   [  172.233588] Object ffff8800aaac4ea8: 6a 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b  jkkkkkkkkkkkkkkk
>   >  >    >                                              ^^
>   >  >    >
>   >  >    >   xfs_efi_log_item.efi_refcount being decremented on the xfs_efi_release()
>   >  >    >   CAI Qian had the same thing in his May 6 "3.9.0: XFS rootfs corruption"
>   >  >    >   email.
>   >  >    >
>   >  >    >   I have not reproduced it yet.
>   >  >
>   >  >  I've hit it on two different machines today. The good news is that the
>   >  >  corruption never makes it onto disk. xfs_repair doesn't pick up anything.
>   >  >
>   >  >  	Dave
>   >  >
>   >  There was a new patch in the efi/efd code that must be misbehaving.
>   >  You are correct, this is not an on-disk value.
>   >
>   >  I now have poisoning on and I can see this doing a compile like you
>   >  suggested. I will ASSERT to see who is doing the decrement after free.
>
> I can hit this almost instantly with fsx. I'll do a bisect, though
> it sounds like you already have a suspect.
>
> 	Dave
>

If you want to try kmem debug of Linux 3.8 that would help.

--Mark.




_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-05-07 19:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-07 13:37 xfs_efi_item slab corruption. (v3.9-10936-g51a26ae) Dave Jones
2013-05-07 19:04 ` Mark Tinguely
2013-05-07 19:07   ` Dave Jones
2013-05-07 19:24     ` Mark Tinguely
2013-05-07 19:31       ` Dave Jones
2013-05-07 19:58         ` Mark Tinguely [this message]
2013-05-07 19:59           ` Dave Jones
2013-05-07 20:04             ` Mark Tinguely
2013-05-07 20:22               ` Dave Jones
2013-05-07 20:24                 ` Mark Tinguely
2013-05-07 22:22                   ` Dave Chinner
2013-05-07 22:45                     ` Mark Tinguely
2013-05-07 23:54                       ` Dave Chinner
2013-05-08  0:43                         ` Dave Jones
2013-05-08 13:24                         ` Mark Tinguely
2013-05-10  1:38                           ` Dave Chinner
2013-05-11 12:09 ` Dmitry Monakhov
2013-05-12  0:40   ` Dave Chinner

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=51895CD7.7040806@sgi.com \
    --to=tinguely@sgi.com \
    --cc=caiqian@redhat.com \
    --cc=davej@redhat.com \
    --cc=xfs@oss.sgi.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