On Mon, Aug 25, 2003 at 11:25:09AM -0500, Russell Cattelan wrote:
> On Mon, 2003-08-25 at 10:50, Axel Thimm wrote:
> > On Sun, Aug 24, 2003 at 11:27:05AM -0500, Eric Sandeen wrote:
> > > On Sun, 24 Aug 2003, Kai Leibrandt wrote:
> > > > Also, is there a howto or readme somewhere where I can find
> > > > out how to build my own .src.rpm kernel packages from the
> > > > redhat errata and the XFS patches?
> > >
> > > No docs... best documentation is probably the spec file itself.
> > > Which xfs patches, and which Red Hat kernel packages, do you
> > > want to combine?
> >
> > I played a bit with rawhide (which is still the same as severn's,
> > I think). Other than the _nolock patch the rest looked trivial. I
> > haven't got a complete build yet, but it looked quite promising
> > (I'm on vacation, so it will take me some time). Whoever cares to
> > look at the current bits can contact me in private.
> Try using this change from the 2.4.22 tree
> http://xfs.org:8090/linux-2.4+xfs/diffs/fs/xfs/linux/xfs_lrw.c@xxxxx?nav=index.html|src/|src/fs|src/fs/xfs|src/fs/xfs/linux|hist/fs/xfs/linux/xfs_lrw.c
Thanks, I'll look into it.
> I think the RH beta tree has do_generic_file_write at this point so
> you should be able to call it directly and drop the whole _nolock
> change all together.
The old patch was doing more (or less) than the new do_generic_*
stuff, e.g. it also did not call invalidate_inode_pages2. Have a look
at the rewritten _nolock patch I ended up for the rawhide kernel & XFS
1.3.0. Is this still needed or not?
> You might need to export do_generic_file_write ... can't remember
> off hand.
They are already exported. :)
> > I was told to better skip 1.3.0 and go straight for the CVS bits
> > for 2.4.22, but I wouldn't like to desync from the XFS release
> > points.
--
Axel.Thimm@xxxxxxxxxxxxxxxxxxx
linux-2.4.21-nolock_write-atrpms.patch
Description: Text document
pgpIBjhlxgAWv.pgp
Description: PGP signature
|