All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Leckie <pleckie@sgi.com>
To: Dave Chinner <david@fromorbit.com>, xfs@oss.sgi.com
Subject: Re: crash with latest code drop.
Date: Wed, 15 Oct 2008 17:51:32 +1000	[thread overview]
Message-ID: <48F5A104.5060506@sgi.com> (raw)
In-Reply-To: <20081015061917.GC25906@disturbed>

Dave Chinner wrote:
> On Wed, Oct 15, 2008 at 03:50:48PM +1000, Peter Leckie wrote:
>   
>> Dave Chinner wrote:
>>     
>>> Update below.
>>>
>>> Cheers,
>>>
>>> Dave.
>>>   
>>>       
>> The original patch appeared to fix the issue, however the latest one  
>> Oops as follows:
>>     
>
> Well, I think the problem dhould be obvious

Gee thanks Dave.
>  - it's the same as
> the first report - deferencing the linux inode without first having
> a refernce on it.
>   

Yes it resolves the issue.

Pete

  reply	other threads:[~2008-10-15  6:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-15  1:49 crash with latest code drop Peter Leckie
2008-10-15  1:18 ` Dave Chinner
2008-10-15  2:29   ` Christoph Hellwig
2008-10-15  3:16     ` Dave Chinner
2008-10-15  3:24       ` Christoph Hellwig
2008-10-15  3:51         ` Dave Chinner
2008-10-15  5:50           ` Peter Leckie
2008-10-15  6:19             ` Dave Chinner
2008-10-15  7:51               ` Peter Leckie [this message]
2008-10-16  2:43                 ` Peter Leckie
2008-10-16  5:55                   ` Dave Chinner
2008-10-16  9:00                   ` Christoph Hellwig
2008-10-17  1:01                     ` Lachlan McIlroy
2008-10-22  6:19               ` Dave Chinner
2008-10-23  4:23                 ` Peter Leckie
2008-10-23  5:39                   ` Dave Chinner
2008-10-15  3:47   ` Peter Leckie

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=48F5A104.5060506@sgi.com \
    --to=pleckie@sgi.com \
    --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 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.