From: Dave Chinner <david@fromorbit.com>
To: Alex Elder <aelder@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 2/3] libxlog: sync up with 2.6.38 kernel code
Date: Mon, 14 Feb 2011 16:31:22 +1100 [thread overview]
Message-ID: <20110214053122.GJ2559@dastard> (raw)
In-Reply-To: <20110214051005.GI2559@dastard>
On Mon, Feb 14, 2011 at 04:10:05PM +1100, Dave Chinner wrote:
> On Wed, Feb 09, 2011 at 03:49:03PM -0600, Alex Elder wrote:
> > On Mon, 2011-01-10 at 19:44 +1100, Dave Chinner wrote:
> > > From: Dave Chinner <dchinner@redhat.com>
> > >
> > > Update libxlog with the current 2.6.38 kernel code and well as
> > > updating the necessary parts of libxfs and variaous header files to
> > > ensure that it compiles correctly.
.....
> xfsprogs. As the code has changed, I'm sure there's bits that are
> now unused by userspace and should be cleaned up. We also need to
> make another pass over the kernel headers to refine what is in
> #idef__KERNEL__ regions as there is some problems in that area as
> well. That doesn't have to be done right now, though...
....
> > > diff --git a/libxfs/trans.c b/libxfs/trans.c
> > > index 1c60f38..c5dd2ca 100644
> > > --- a/libxfs/trans.c
> > > +++ b/libxfs/trans.c
> > > @@ -36,8 +36,7 @@ libxfs_trans_alloc(
> > > }
> > > ptr->t_mountp = mp;
> > > ptr->t_type = type;
> > > - ptr->t_items_free = XFS_LIC_NUM_SLOTS;
> >
> > t_items_free is removed from the xfs_trans structure
> > in "include/xfs_trans.h" but it remains in the version
> > of that structure defined in "include/libxfs.h".
> >
> > I believe the latter is the one we want to keep,
> > but if that's the case you'd better delete the
> > field definition there. (The compiler isn't
> > warning you that you neglected to initialize a
> > field.)
>
> Nor is it warning about a duplicate definition by the sound of it.
> I'll fix it up.
There are two declarations of struct xfs_trans in userspace but only
the one in libxfs.h is used because the one in include/xfs_trans.h
is surrounded bu #ifdef __KERNEL__. Just an example of the sort of
cleanup I mentioned above that is needed...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-02-14 5:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 8:44 [PATCH 0/3] xfsprogs: sync up with 2.6.38 kernel code V2 Dave Chinner
2011-01-10 8:44 ` [PATCH 1/3] libxfs: reintroduce old xfs_repair radix-tree code Dave Chinner
2011-01-24 8:58 ` Christoph Hellwig
2011-02-09 18:05 ` Alex Elder
2011-02-14 0:36 ` Dave Chinner
2011-01-10 8:44 ` [PATCH 2/3] libxlog: sync up with 2.6.38 kernel code Dave Chinner
2011-01-24 8:47 ` Christoph Hellwig
2011-01-24 23:47 ` Dave Chinner
2011-02-09 21:49 ` Alex Elder
2011-02-14 5:10 ` Dave Chinner
2011-02-14 5:31 ` Dave Chinner [this message]
2011-02-14 5:46 ` Dave Chinner
2011-01-10 8:44 ` [PATCH 3/3] libxfs: sync files " Dave Chinner
2011-01-24 8:57 ` Christoph Hellwig
2011-01-24 23:55 ` Dave Chinner
2011-02-10 19:02 ` Alex Elder
2011-02-14 6:30 ` [PATCH 0/3] xfsprogs: sync up with 2.6.38 kernel code V2 Dave Chinner
2011-02-22 20:45 ` Alex Elder
2011-03-07 18:14 ` Alex Elder
2011-03-07 18:24 ` Christoph Hellwig
2011-04-13 16:34 ` Alex Elder
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=20110214053122.GJ2559@dastard \
--to=david@fromorbit.com \
--cc=aelder@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