mirror of
https://github.com/RGBCube/serenity
synced 2025-07-25 04:57:44 +00:00
Kernel: Pass a FileDescription to File::chmod() and File::chown()
We're going to make use of it in the next commit. But the idea is we want to know how this File (more specifically, InodeFile) was opened in order to decide how chown()/chmod() should behave, in particular whether it should be allowed or not. Note that many other File operations, such as read(), write(), and ioctl(), already require the caller to pass a FileDescription.
This commit is contained in:
parent
67cbc015d5
commit
a9946a99f2
6 changed files with 14 additions and 12 deletions
|
@ -82,8 +82,8 @@ public:
|
|||
virtual String absolute_path(const FileDescription&) const = 0;
|
||||
|
||||
virtual KResult truncate(u64) { return KResult(-EINVAL); }
|
||||
virtual KResult chown(uid_t, gid_t) { return KResult(-EBADF); }
|
||||
virtual KResult chmod(mode_t) { return KResult(-EBADF); }
|
||||
virtual KResult chown(FileDescription&, uid_t, gid_t) { return KResult(-EBADF); }
|
||||
virtual KResult chmod(FileDescription&, mode_t) { return KResult(-EBADF); }
|
||||
|
||||
virtual const char* class_name() const = 0;
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue