public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Lachlan McIlroy <lachlan@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: TAKE 988255 - fix instant oops with tracing enabled
Date: Tue, 14 Oct 2008 16:41:03 +1100	[thread overview]
Message-ID: <20081014054103.GK10716@disturbed> (raw)
In-Reply-To: <48F42F12.1010409@sgi.com>

On Tue, Oct 14, 2008 at 03:33:06PM +1000, Lachlan McIlroy wrote:
> Dave Chinner wrote:
>> On Tue, Oct 14, 2008 at 12:17:47PM +1100, Lachlan McIlroy wrote:
>>> fix instant oops with tracing enabled
>>>
>>> We can only read inode->i_count if the inode is actually there and not
>>> a NULL pointer.  This was introduced in one of the recent sync patches.
>>>
>>> Signed-off-by: Christoph Hellwig <hch@lst.de>
>>
>> BTW, this now means that other pending patches won't apply cleanly....
>>
>
> Yeah this patch hunk didn't apply but was easy to hand merge.  It also
> didn't compile because of a missing comma from the 4th last line.  Can
> you please make sure each of your patch series compile on their own?

I do make sure every patch compiles given the config options a
mainline kernel allows. However, the CONFIG_XFS_TRACE option is not
present in mainline-derived kernels so it's not obvious when
problems occur inside code that isn't easily configurable on
such a kernel....

As it is, I haven't done a CONFIG_XFS_TRACE build for several months
because I've found that I haven't needed tracing to find problems
esoteric problems. Using watchpoints, breakpoints and single
stepping catches problems as they occur rather than needing tracing
to try to work out what went wrong after a problem has occurred.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2008-10-14  5:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-14  1:17 TAKE 988255 - fix instant oops with tracing enabled Lachlan McIlroy
2008-10-14  2:05 ` Dave Chinner
2008-10-14  5:33   ` Lachlan McIlroy
2008-10-14  5:41     ` Dave Chinner [this message]
2008-10-14  6:12       ` Timothy Shimmin
2008-10-14  6:50         ` Dave Chinner
2008-10-14 12:56         ` Christoph Hellwig

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=20081014054103.GK10716@disturbed \
    --to=david@fromorbit.com \
    --cc=lachlan@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