public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Goodwin <markgw@sgi.com>
To: xfs@oss.sgi.com, hch@lst.de
Subject: Re: fw: [PATCH] fix instant oops with tracing enabled
Date: Tue, 14 Oct 2008 10:40:15 +1000	[thread overview]
Message-ID: <48F3EA6F.9000209@sgi.com> (raw)
In-Reply-To: <20081013223932.GE10716@disturbed>



Dave Chinner wrote:
> 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.

Lachlan also saw some regressions after merging these patchsets :
. replace the mount inode list with radix tree traversals
. clean up sync code

> If that
> series is going to be included in the current round of checkins
> then this patch probably isn't needed.

The agreed plan for 2.6.28 still has the following patchsets to go in:

. Combine the XFS and Linux inode structures V2
. Track reclaimable inodes in inode cache
. AIL cleanup and bug fixes
. Account for allocated blocks when expanding directories
. Check for valid transaction headers in recovery
. fix remount rw with unrecognized options

It's starting to look like a pretty aggressive merge and QA schedule.
Dave, is it worth doing any testing until these are *all* merged?

Thanks
-- Mark

  reply	other threads:[~2008-10-13 23:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-13 22:39 fw: [PATCH] fix instant oops with tracing enabled Dave Chinner
2008-10-14  0:40 ` Mark Goodwin [this message]
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=48F3EA6F.9000209@sgi.com \
    --to=markgw@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox