[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: chown32() weirdness

To: Wessel Dankers <wsl@fruit.eu.org>
Subject: Re: chown32() weirdness
From: Eric Sandeen <sandeen@sgi.com>
Date: Mon, 18 Feb 2002 10:40:52 -0600 (CST)
Cc: <linux-xfs@oss.sgi.com>
In-reply-to: <20020218145718.N22191@fruit.eu.org>
Sender: owner-linux-xfs@oss.sgi.com

Hm, we used to call inode_change_ok() in linvfs_setattr - which
would not have allowed this - but it was recently removed as "unneeded"
since xfs has it's own internal checks... let me go look at those internal
checks.

-Eric

On Mon, 18 Feb 2002, Wessel Dankers wrote:

> It seems XFS is suprisingly "empowering" these days :)
> Below is a transcript which shows a problem with recent CVS kernels.
> It's the CVS version from today (see the uname output).

Follow-Ups:
- Re: chown32() weirdness
  - From: Eric Sandeen <sandeen@sgi.com>

References:
- chown32() weirdness
  - From: Wessel Dankers <wsl@fruit.eu.org>

Prev by Date: chown32() weirdness
Next by Date: Re: chown32() weirdness
Previous by thread: chown32() weirdness
Next by thread: Re: chown32() weirdness
Index(es):
- Date
- Thread