From: Eric Sandeen <sandeen@sandeen.net>
To: xfs@oss.sgi.com
Cc: centos-devel@centos.org
Subject: New CentOS4/RHEL4-compatible xfs module rpms
Date: Sun, 19 Nov 2006 13:07:48 -0600 [thread overview]
Message-ID: <4560AB84.9060200@sandeen.net> (raw)
http://sandeen.net/rhel4_xfs/kernel-module-xfs-2.6.9-42.0.2.EL-0.2-1.src.rpm
rpmbuild --rebuild --target i686
kernel-module-xfs-2.6.9-42.0.2.EL-0.2-1.src.rpm
will build against the currently running kernel, or
rpmbuild --rebuild --target i686 --define "kernel_topdir
/lib/modules/2.6.9-42.0.2.EL/build"
kernel-module-xfs-2.6.9-42.0.2.EL-0.2-1.src.rpm
will build against what is defined in kernel_topdir
you need matching kernel & kernel-devel rpms installed to build.
Changelog: mostly pulling in fixes sgi sent for sles9, plus specfile
cleanups.
[root@sandeen rhel4_xfs]# rpm -qp --changelog
kernel-module-xfs-2.6.9-42.0.2.EL-0.2-1.src.rpm
* Mon Nov 13 2006 - sandeen-centos@sandeen.net
- removed xfs_direct_io_locking.patch, RHEL4U4 has the fix now.
- Update to xfs codebase from SLES9_SP3_BRANCH_20061107171129
- xfs-kern-26347a-fix-race-on-link: fix race on link
(191713, SGI:PV953287).
- xfs-kern-26040a-do-not-dirty-inode-being-freed:
Don't dirty the inode if it being freed in xfs_iunpin (179117,
SGI:PV952967).
- xfs-kern-25687a-sles9sp3-iunpin-reclaim-fix: Fix
an inode use-after-free during an unpin (SGI:PV946321, 142533).
- xfs-kern-930841-default_acl_enospc_fix:
Default acl ENOSPC fix (133990, SGI:PV930841).
- xfs-kern-25238a-quota-trans-diag: quota trans diag
(131262, SGI:PV931456).
- xfs-ftruncate-stale-data: XFS ftruncate() bug
could expose stale data (151055).
- xfs-log-diag: log_runout_diagnostics (131262,
SGI:PV947110).
- xfs-kern-202363a-fix-xfs_finish_reclaim_all-umount-deadlock:
fix xfs_finish_reclaim_all umount deadlock (132358,
SGI:PV943821).
- clean up specfile:
default to building against running kernel
try to match fedora conventions slightly better
re-enable debuginfo pkg building, module stripping
fix recognition of root on xfs, (grep -i XFS)
remove unused -source subpackage
-Eric
next reply other threads:[~2006-11-19 19:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-19 19:07 Eric Sandeen [this message]
2006-12-07 17:25 ` New CentOS4/RHEL4-compatible xfs module rpms Geir A. Myrestrand
2006-12-07 17:52 ` Eric Sandeen
2006-12-07 18:17 ` Geir A. Myrestrand
2006-12-07 23:26 ` David Chinner
2006-12-08 2:58 ` Geir A. Myrestrand
2006-12-07 18:19 ` Geir A. Myrestrand
2006-12-07 20:51 ` Geir A. Myrestrand
2006-12-07 21:11 ` Nathan Scott
2006-12-07 21:35 ` Geir A. Myrestrand
2006-12-07 21:40 ` Nathan Scott
2006-12-07 21:51 ` Geir A. Myrestrand
2006-12-07 22:06 ` Nathan Scott
2006-12-07 22:16 ` Geir A. Myrestrand
2006-12-07 22:18 ` Eric Sandeen
2006-12-07 22:25 ` Geir A. Myrestrand
2006-12-07 22:30 ` Eric Sandeen
2006-12-07 22:52 ` Geir A. Myrestrand
2006-12-07 22:53 ` Eric Sandeen
2006-12-07 23:08 ` Geir A. Myrestrand
2007-07-19 14:37 ` James Braid
2007-07-19 15:15 ` Eric Sandeen
2007-07-21 3:34 ` James Braid
2007-07-21 14:58 ` Eric Sandeen
2007-07-21 15:36 ` James Braid
-- strict thread matches above, loose matches on Subject: below --
2007-08-08 16:04 James Pearson
2007-08-08 16:09 ` Eric Sandeen
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=4560AB84.9060200@sandeen.net \
--to=sandeen@sandeen.net \
--cc=centos-devel@centos.org \
--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