diff options
| author | Bryan Wu <bryan.wu@analog.com> | 2007-06-05 11:02:01 +0800 |
|---|---|---|
| committer | Linus Torvalds <torvalds@woody.linux-foundation.org> | 2007-06-07 17:11:13 -0700 |
| commit | 85f6038f2170e3335dda09c3dfb0f83110e87019 (patch) | |
| tree | b756deeb0873f18ad8711db7dba948ca8d698d6f /crypto/hash.c | |
| parent | c8d8170feb824875baf68f8aaecb181a6500ce81 (diff) | |
RAMFS NOMMU: missed POSIX UID/GID inode attribute checking
This bug was caught by LTP testcase fchmod06 on Blackfin platform.
In the manpage of fchmod, "EPERM: The effective UID does not match the
owner of the file, and the process is not privileged (Linux: it does not
have the CAP_FOWNER capability)."
But the ramfs nommu code missed the inode_change_ok POSIX UID/GID
verification. This patch fixed this.
Signed-off-by: Bryan Wu <bryan.wu@analog.com>
Cc: David Howells <dhowells@redhat.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'crypto/hash.c')
0 files changed, 0 insertions, 0 deletions