public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Lachlan McIlroy <lachlan@sgi.com>
To: Lachlan McIlroy <lachlan@sgi.com>, xfs@oss.sgi.com
Subject: Re: TAKE 988255 - fix instant oops with tracing enabled
Date: Tue, 14 Oct 2008 15:33:06 +1000	[thread overview]
Message-ID: <48F42F12.1010409@sgi.com> (raw)
In-Reply-To: <20081014020556.GH10716@disturbed>

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?

@@ -84,25 +84,12 @@ vn_ioerror(
 
 #ifdef	XFS_INODE_TRACE
 
-/*
- * Reference count of Linux inode if present, -1 if the xfs_inode
- * has no associated Linux inode.
- */
-static inline int xfs_icount(struct xfs_inode *ip)
-{
-	struct inode *inode = VFS_I(ip);
-
-	if (!inode)
-		return atomic_read(&inode->i_count);
-	return -1;
-}
-
 #define KTRACE_ENTER(ip, vk, s, line, ra)			\
 	ktrace_enter(	(ip)->i_trace,				\
 /*  0 */		(void *)(__psint_t)(vk),		\
 /*  1 */		(void *)(s),				\
 /*  2 */		(void *)(__psint_t) line,		\
-/*  3 */		(void *)(__psint_t)xfs_icount(ip),	\
+/*  3 */		(void *)(__psint_t)atomic_read(&VFS_I(ip)->i_count) \
 /*  4 */		(void *)(ra),				\
 /*  5 */		NULL,					\
 /*  6 */		(void *)(__psint_t)current_cpu(),	\

  reply	other threads:[~2008-10-14  4:32 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 [this message]
2008-10-14  5:41     ` Dave Chinner
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=48F42F12.1010409@sgi.com \
    --to=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