From: Andreas Dilger <adilger@sun.com>
To: Theodore Ts'o <tytso@mit.edu>,
linux-ext4@vger.kernel.org, mkoenig@suse.de, hvogel@suse.de
Cc: Girish Shilamkar <Girish.Shilamkar@Sun.COM>,
Eric Sandeen <esandeen@redhat.com>
Subject: Integrating patches in SLES10 e2fsprogs
Date: Thu, 24 Jan 2008 14:17:28 -0700 [thread overview]
Message-ID: <20080124211728.GA24900@webber.adilger.int> (raw)
I was looking through the SLES10 e2fsprogs patch set, and I wonder if some
of them could be integrated upstream, and if any effort had been made in
that direction in the past? In particular, the addition of et_list_lock()
and et_list_unlock() to libcom_err cause failures if e2fsprogs is updated
to a non-SLES10 derived RPM.
A list of patches and (my) descriptions are below:
libcom_err-no-static-buffer.patch - avoids static buffer returned to caller
by error_message() function
libcom_err-no-init_error_table.patch - removes init_error_table() function
(maybe because it isn't thread safe?),
but I think this could be made thread
safe by adding locking around use of
_et_dynamic_list, or maybe it is
obsoleted by add_error_table()?
libcom_err-no-e2fsck.static.patch - can't build e2fsck.static because of
-lpthread in libcom_err-mutex.patch, but
nothing uses e2fsck.static anymore?
libcom_err-mutex.patch - add et_list_{un,}lock() via pthread mutex
e2fsprogs-blkid.diff - Adds documentation of BLKID_FILE environment variable.
This is actually implemented directly in libblkid in
e2fsprogs-1.40.2 but no mention of it in the man pages.
e2fsprogs-mdraid.patch - allows skip of mdraid probing, not sure why?
e2fsprogs-probe_reiserfs-fpe.patch - fixes a legitimate bug in probe_reiserfs,
though it might be better to just return
an error if the blocksize is bad?
In addition to this, the SLES10 .spec file is completely different than that
shipped with upstream e2fsprogs, and I'd like to reconcile that if possible.
In particular it has libcom_err and libss in a separate RPM (libcom_err).
I understand that FC8 (not sure about RHEl5) has also split out some of the
libraries, but in a different way (e2fsprogs-libs) and that is a bit of a
headache. It might be possible to reconcile with suitable rpm-fu, but it
would be desirable that SLES pick up these changes in the future...
I don't want to spam the list with all of the patches yet, but if there is
interest in merging these upstream then I can provide versions of these
patches against the current e2fsprogs instead of 1.38 that is in SLES10.
Eric, I haven't looked at the FC8/9 e2fsprogs yet, but do they also have
a ton of patches (possibly in the -pu branch), or do they track upstream
more closely?
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next reply other threads:[~2008-01-24 21:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 21:17 Andreas Dilger [this message]
2008-01-24 21:27 ` Integrating patches in SLES10 e2fsprogs Eric Sandeen
2008-01-25 15:22 ` Matthias Koenig
2008-01-27 5:05 ` Theodore Tso
2008-01-27 15:06 ` Eric Sandeen
2008-01-27 20:27 ` Theodore Tso
2008-01-28 4:40 ` Eric Sandeen
2008-01-28 5:24 ` Theodore Tso
2008-01-28 5:43 ` Eric Sandeen
2008-01-28 16:01 ` Thierry Vignaud
2008-01-28 16:06 ` Thierry Vignaud
2008-01-28 17:03 ` Theodore Tso
2008-01-28 17:00 ` Theodore Tso
2008-01-28 15:26 ` Matthias Koenig
2008-01-28 15:38 ` Theodore Tso
2008-01-28 16:54 ` Eric Sandeen
2008-01-28 20:59 ` Andreas Dilger
2008-01-29 13:52 ` Matthias Koenig
2008-01-29 14:35 ` Theodore Tso
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=20080124211728.GA24900@webber.adilger.int \
--to=adilger@sun.com \
--cc=Girish.Shilamkar@Sun.COM \
--cc=esandeen@redhat.com \
--cc=hvogel@suse.de \
--cc=linux-ext4@vger.kernel.org \
--cc=mkoenig@suse.de \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.