mirror of
https://github.com/LadybirdBrowser/ladybird.git
synced 2025-04-28 07:18:51 +00:00
Kernel: Add the futimens syscall
We have a problem with the original utimensat syscall because when we do call LibC futimens function, internally we provide an empty path, and the Kernel get_syscall_path_argument method will detect this as an invalid path. This happens to spit an error for example in the touch utility, so if a user is running "touch non_existing_file", it will create that file, but the user will still see an error coming from LibC futimens function. This new syscall gets an open file description and it provides the same functionality as utimensat, on the specified open file description. The new syscall will be used later by LibC to properly implement LibC futimens function so the situation described with relation to the "touch" utility could be fixed.
This commit is contained in:
parent
71e665f0f9
commit
cbf78975f1
Notes:
sideshowbarker
2024-07-17 03:03:44 +09:00
Author: https://github.com/supercomputer7
Commit: cbf78975f1
Pull-request: https://github.com/SerenityOS/serenity/pull/18231
Reviewed-by: https://github.com/ADKaster ✅
5 changed files with 49 additions and 2 deletions
|
@ -313,10 +313,15 @@ ErrorOr<void> VirtualFileSystem::utime(Credentials const& credentials, StringVie
|
|||
ErrorOr<void> VirtualFileSystem::utimensat(Credentials const& credentials, StringView path, Custody& base, timespec const& atime, timespec const& mtime, int options)
|
||||
{
|
||||
auto custody = TRY(resolve_path(credentials, path, base, nullptr, options));
|
||||
auto& inode = custody->inode();
|
||||
return do_utimens(credentials, custody, atime, mtime);
|
||||
}
|
||||
|
||||
ErrorOr<void> VirtualFileSystem::do_utimens(Credentials const& credentials, Custody& custody, timespec const& atime, timespec const& mtime)
|
||||
{
|
||||
auto& inode = custody.inode();
|
||||
if (!credentials.is_superuser() && inode.metadata().uid != credentials.euid())
|
||||
return EACCES;
|
||||
if (custody->is_readonly())
|
||||
if (custody.is_readonly())
|
||||
return EROFS;
|
||||
|
||||
// NOTE: A standard ext2 inode cannot store nanosecond timestamps.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue