From: Christoph Hellwig <hch@infradead.org>
To: Andreas Gruenbacher <agruen@suse.de>,
Nathan Scott <nathans@debian.org>,
xfs@oss.sgi.com
Subject: new acl tarball release?
Date: Fri, 26 Dec 2008 14:55:06 -0500 [thread overview]
Message-ID: <20081226195506.GA4173@infradead.org> (raw)
The current acl 2.2.47 release has a quite nasty bug about following
symlinks, which is already fixes in the current ptools/cvs/git tree:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499076
http://oss.sgi.com/bugzilla/show_bug.cgi?id=790
Any chance we can put out a 2.2.48 release with that fix so that the
broken version doesn't end up in distros?
The oss bugzilla also has another patch that needs reviewing.
AFAICS the same problems symlink walking code is also used in attr,
so it could use an update, too.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2008-12-26 19:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-26 19:55 Christoph Hellwig [this message]
2008-12-30 16:55 ` new acl tarball release? 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=20081226195506.GA4173@infradead.org \
--to=hch@infradead.org \
--cc=agruen@suse.de \
--cc=nathans@debian.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