public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: rokr@hermes-softlab.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: reading user. extended attributes from symlinks in 2.6 kernels
Date: Thu, 14 Feb 2008 11:43:17 -0500	[thread overview]
Message-ID: <47B46FA5.7070002@tmr.com> (raw)
In-Reply-To: <20080211173809.4a2db13f@hermes-softlab.com>

Rok Ruzic wrote:
> 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.
> 
If you want to do it at user code level, you could note the symlink, 
follow it to the "real" name, and read the EA there. I don't see any 
easy way to force the kernel to follow the symlink.


-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

      reply	other threads:[~2008-02-14 16:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-11 16:38 reading user. extended attributes from symlinks in 2.6 kernels Rok Ruzic
2008-02-14 16:43 ` Bill Davidsen [this message]

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=47B46FA5.7070002@tmr.com \
    --to=davidsen@tmr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox