From: Rok Ruzic <rok.ruzic@hermes-softlab.com>
To: linux-kernel@vger.kernel.org
Subject: reading user. extended attributes from symlinks in 2.6 kernels
Date: Mon, 11 Feb 2008 17:38:09 +0100 [thread overview]
Message-ID: <20080211173809.4a2db13f@hermes-softlab.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
Hello,
I have an XFS filesystem containing files and symlinks with application-specific EAs in the user namespace. The files, symlinks and their EAs were created while running a 2.4 kernel.
In 2.6 kernels access to user EAs was prevented for symlinks. My problem is that i have to upgrade the kernel from 2.4 to 2.6 series and i have to have access to all the EAs after upgrade. Is there a way to read user EAs off of symlinks on an XFS filesystem on a 2.6 kernel either from userspace or from a filter driver sitting between VFS and XFS filesystem code?
I would appreciate it very much if somebody could point me towards a solution.
Rok
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2008-02-11 17:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 16:38 Rok Ruzic [this message]
2008-02-14 16:43 ` reading user. extended attributes from symlinks in 2.6 kernels Bill Davidsen
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=20080211173809.4a2db13f@hermes-softlab.com \
--to=rok.ruzic@hermes-softlab.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rokr@hermes-softlab.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.