From: Dave Chinner <david@fromorbit.com>
To: Niv Sardi <xaiki@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: TAKE 976035 - streamline init/exit path
Date: Fri, 27 Jun 2008 09:54:41 +1000 [thread overview]
Message-ID: <20080626235441.GU29319@disturbed> (raw)
In-Reply-To: <20080625030057.973173A5D1@itchy>
On Wed, Jun 25, 2008 at 01:00:57PM +1000, Niv Sardi wrote:
> streamline init/exit path
>
> Currently the xfs module init/exit code is a mess. It's farmed out
> over a lot of function with very little error checking. This patch
> makes sure we propagate all initialization failures properly and clean
> up after them. Various runtime initializations are replaced with
> compile-time initializations where possible to make this easier. The
> exit path is similarly consolidated.
>
> There's now split out function to create/destroy the kmem zones and
> alloc/free the trace buffers. I've also changed the ktrace
> allocations to KM_MAYFAIL and handled errors resulting from that.
>
> And yes, we really should replace the XFS_*_TRACE ifdefs with a single
> XFS_TRACE..
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> Signed-off-by: Niv Sardi <xaiki@sgi.com>
Niv, can you now do another checkin that fixes the compilation
error when CONFIG_PROCFS=N in fs/xfs/linux-2.6/xfs_stats.h that
was reported on linux-next (i.e. fix the bug that led up to
everyone discovering the busted commit)?
BTW, your script is still busted - look at the wacky cc list
on the take message. Please be a little more careful...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2008-06-26 23:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 3:00 TAKE 976035 - streamline init/exit path Niv Sardi
2008-06-25 13:57 ` Christoph Hellwig
2008-06-26 0:56 ` Niv Sardi
2008-06-26 23:54 ` Dave Chinner [this message]
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=20080626235441.GU29319@disturbed \
--to=david@fromorbit.com \
--cc=xaiki@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