Re: xfs_quota project + symlinks

[Timothy Shimmin <tes@xxxxxxx>]

Okay, thanks, Nathan,

So does that mean we need a way for FSGETXATTR and FSSETXATTR ioctls to
work on the symlink inode? Is this (symlink ioctls) done elsewhere? :)

One for Donald :)

--Tim

--On 31 October 2006 9:24:03 AM +1100 Nathan Scott <nscott@xxxxxxxxxx> wrote:

> On Mon, 2006-10-30 at 15:39 +1000, Timothy Shimmin wrote:
> > Hi,
> >
> > > If path is a symlink, then the project id is applied to a file
> > > potentially on another filesystem. Wouldn't it be better to
> > > add O_NOFOLLOW here ?
> >
> > You want it to error out if it is a symlink.
> Thats not ideal.  But some way to stay on the symlink's filesystem
> is probably needed here, from the sound of it.
>
> > I'm not that familiar with quotas (Nathan?, Donald?), but I would presume
> > that since symlinks take up space depending on the symlink path, that they 
> > should
> > have quota control on the space they take up.
> If they require space to be allocated (i.e the symlink target is not
> stored in the inode literal area), then that space allocation will be
> subject to quota IIRC.
>
> > In which case, one would actually not want to follow the symlink but rather
> > apply a limit to that actual symlink inode.
> *nod*
>
> > But I agree, I doubt one wants to follow the symlinks - it would get rather
> > confusing.
> *nod*
>
> cheers.
>
> --
> Nathan