From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Cc: hch@lst.de
Subject: fw: [PATCH] fix instant oops with tracing enabled
Date: Tue, 14 Oct 2008 09:39:32 +1100 [thread overview]
Message-ID: <20081013223932.GE10716@disturbed> (raw)
SGI folks,
Looks like Christoph is having problems posting to the list;
the spam filter is dropping all his mail. In the mean time,
here's a fix for an oops in the tracing code as a result of
the last check ins. I didn't see this because the "combine
inodes" patches removes xfs_icount altogether. If that
series is going to be included in the current round of checkins
then this patch probably isn't needed.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
From: Christoph Hellwig <hch@lst.de>
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>
Index: linux-2.6-xfs/fs/xfs/linux-2.6/xfs_vnode.c
===================================================================
--- linux-2.6-xfs.orig/fs/xfs/linux-2.6/xfs_vnode.c 2008-10-13 12:07:38.000000000 -0400
+++ linux-2.6-xfs/fs/xfs/linux-2.6/xfs_vnode.c 2008-10-13 12:07:47.000000000 -0400
@@ -92,7 +92,7 @@ static inline int xfs_icount(struct xfs_
{
struct inode *inode = VFS_I(ip);
- if (!inode)
+ if (inode)
return atomic_read(&inode->i_count);
return -1;
}
next reply other threads:[~2008-10-13 22:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 22:39 Dave Chinner [this message]
2008-10-14 0:40 ` fw: [PATCH] fix instant oops with tracing enabled Mark Goodwin
2008-10-14 2:04 ` Dave Chinner
2008-10-14 13:11 ` Christoph Hellwig
2008-10-15 1:27 ` Lachlan McIlroy
2008-10-15 0:54 ` Dave Chinner
2008-10-15 2:28 ` Lachlan McIlroy
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=20081013223932.GE10716@disturbed \
--to=david@fromorbit.com \
--cc=hch@lst.de \
--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.