From: Christoph Hellwig <hch@lst.de>
To: Mark Goodwin <markgw@sgi.com>
Cc: xfs@oss.sgi.com, hch@lst.de
Subject: Re: fw: [PATCH] fix instant oops with tracing enabled
Date: Tue, 14 Oct 2008 15:11:40 +0200 [thread overview]
Message-ID: <20081014131140.GB17351@lst.de> (raw)
In-Reply-To: <48F3EA6F.9000209@sgi.com>
On Tue, Oct 14, 2008 at 10:40:15AM +1000, Mark Goodwin wrote:
> Lachlan also saw some regressions after merging these patchsets :
> . replace the mount inode list with radix tree traversals
> . clean up sync code
What exactly? I saw some softlookup in 042, but when applying Dave's
xfs_sync_inodeS_ag fix (or the hal of it applying without the del inodes
tracking in the radix tree) it goes away.
> >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
3-6 are small bug fixes and should go in ASAP. I'd really like to see 1
and 2 and volunter to help sorting out any fallout. Not entirely sure
about the AIL patches - they seem ready but at least they don't have
much impact on everything else. So if you really want to reduce the
amount of patches those would be the ones.
next prev parent reply other threads:[~2008-10-14 13:10 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
2008-10-14 2:04 ` Dave Chinner
2008-10-14 13:11 ` Christoph Hellwig [this message]
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=20081014131140.GB17351@lst.de \
--to=hch@lst.de \
--cc=markgw@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