From: Andreas Gruenbacher <agruen@suse.de>
To: Dave Kleikamp <shaggy@austin.ibm.com>
Cc: jfs-patches@www-124.southbury.usf.ibm.com, acl-devel@bestbits.at,
linux-fsdevel@vger.kernel.org
Subject: Re: JFS extended attributes and ACLs - New Patches
Date: Mon, 9 Sep 2002 17:02:54 +0200 [thread overview]
Message-ID: <200209091702.55163.agruen@suse.de> (raw)
In-Reply-To: <200209090958.40221.shaggy@austin.ibm.com>
On Monday 09 September 2002 16:58, Dave Kleikamp wrote:
> Andreas,
>
> Thanks for the test cases. I now have new patches that pass the ACL
> tests cleanly, and pass the extended attributes cases that are not
> ext2/3-specific.
>
> This code allows extended attributes to be set on symlinks. Should this
> be disallowed?
Extended user attributes should be allowed only for regular files and for
directories with the sticky bet cleared. Rationale: See the attr(5) manual
page.
> The patches are available here:
> http://www-124.ibm.com/developerworks/patch/?func=detailpatch&patch_id=351&
>group_id=35
> http://www-124.ibm.com/developerworks/patch/?func=detailpatch&patch_id=352&
>group_id=35
Are these links permanent?
--Andreas.
next prev parent reply other threads:[~2002-09-09 15:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33.0209061703200.26258-100000@wotan.suse.de>
[not found] ` <200209061718.59114.agruen@suse.de>
2002-09-09 14:58 ` JFS extended attributes and ACLs - New Patches Dave Kleikamp
2002-09-09 15:02 ` Andreas Gruenbacher [this message]
2002-09-09 15:28 ` Dave Kleikamp
2002-09-09 15:30 ` Dave Kleikamp
2002-09-10 7:40 Luka Renko
2002-09-12 15:13 ` Andreas Gruenbacher
2002-09-12 16:16 ` Dave Kleikamp
2002-09-12 17:04 ` Andreas Gruenbacher
2002-09-12 17:34 ` Dave Kleikamp
2002-09-13 5:06 ` Nathan Scott
2002-09-13 9:27 ` Andreas Gruenbacher
2002-09-13 12:18 ` Dave Kleikamp
2002-09-13 9:32 ` Andreas Gruenbacher
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=200209091702.55163.agruen@suse.de \
--to=agruen@suse.de \
--cc=acl-devel@bestbits.at \
--cc=jfs-patches@www-124.southbury.usf.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=shaggy@austin.ibm.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 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.