public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Julian Wollrath <jwollrath@web.de>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: Null pointer dereference and following traces on 3.9-rc1
Date: Fri, 15 Mar 2013 15:57:01 +0100	[thread overview]
Message-ID: <20130315155701.1423fb02@ilfaris> (raw)
In-Reply-To: <20130310225600.GL23616@dastard>

> If you can reproduce this, please run an event trace  gathering
> the xfs_swap_extent* trace points while xfs_fsr is running so I can
> determine if/why the swap extents code is corrupting inodes.
> 
> # trace-cmd record -e xfs_swap_extents\* xfs_fsr .....
> <crash>
> <kill xfs_fsr>
> # trace-cmd report > trace_report.txt
So fare I was not able to reproduce it but when I am able to reproduce
it, I will send you an event trace.


Best regards,
Julian

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

      reply	other threads:[~2013-03-15 14:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-10 14:49 Null pointer dereference and following traces on 3.9-rc1 Julian Wollrath
2013-03-10 22:56 ` Dave Chinner
2013-03-15 14:57   ` Julian Wollrath [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=20130315155701.1423fb02@ilfaris \
    --to=jwollrath@web.de \
    --cc=david@fromorbit.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