Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
L
lxc
Project
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Chen Yisong
lxc
Commits
87545854
Unverified
Commit
87545854
authored
Feb 05, 2021
by
Christian Brauner
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
mount_utils: detect new mount api support
Signed-off-by:
Christian Brauner
<
christian.brauner@ubuntu.com
>
parent
55a85f4a
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
23 additions
and
0 deletions
+23
-0
mount_utils.h
src/lxc/mount_utils.h
+23
-0
No files found.
src/lxc/mount_utils.h
View file @
87545854
...
...
@@ -10,6 +10,7 @@
#include "compiler.h"
#include "memory_utils.h"
#include "syscall_wrappers.h"
/* open_tree() flags */
...
...
@@ -186,4 +187,26 @@ __hidden extern int fd_bind_mount(int dfd_from, const char *path_from,
__u64
o_flags_to
,
__u64
resolve_flags_to
,
unsigned
int
attr_flags
,
bool
recursive
);
/*
* We use openat2() as indicator whether or not the new mount api is supported.
* First, because openat2() has been introduced after all syscalls from the new
* mount api we currently use and second because our hardened mount logic
* relies on openat2() to safely resolve paths.
*/
static
inline
bool
new_mount_api
(
void
)
{
__do_close
int
fd
;
static
int
supported
=
-
1
;
if
(
supported
==
-
1
)
{
fd
=
openat2
(
-
EBADF
,
""
,
NULL
,
0
);
if
(
fd
<
0
&&
errno
!=
ENOSYS
)
supported
=
1
;
else
supported
=
0
;
}
return
supported
==
1
;
}
#endif
/* __LXC_MOUNT_UTILS_H */
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment