public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com, Mark Tinguely <tinguely@sgi.com>,
	CAI Qian <caiqian@redhat.com>
Subject: Re: xfs_efi_item slab corruption. (v3.9-10936-g51a26ae)
Date: Tue, 7 May 2013 20:43:50 -0400	[thread overview]
Message-ID: <20130508004350.GA19136@redhat.com> (raw)
In-Reply-To: <20130507235458.GG24635@dastard>

On Wed, May 08, 2013 at 09:54:58AM +1000, Dave Chinner wrote:
 > Dave, the patch below should fix the problem.
 > 
 > xfs: Don't reference the EFI after it is freed
 > 
 > From: Dave Chinner <dchinner@redhat.com>
 > 
 > Checking the EFI for whether it is being released from recovery
 > after we've already released the known active reference is a mistake
 > worthy of a brown paper bag. Fix the (now) obvious use after free
 > that it can cause.

Yup, that works for me.

thanks,

	Dave

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

  reply	other threads:[~2013-05-08  0:44 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
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 [this message]
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=20130508004350.GA19136@redhat.com \
    --to=davej@redhat.com \
    --cc=caiqian@redhat.com \
    --cc=david@fromorbit.com \
    --cc=tinguely@sgi.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