mirror of
https://github.com/torvalds/linux.git
synced 2026-04-18 14:53:58 -04:00
6285f0881e
The sys_foo() naming scheme used by the syscall wrappers may collide with application symbols. Especially as 'sys_' is an obvious naming scheme an application may choose for its own custom systemcall wrappers. Avoid these conflicts by using an leading underscore which moves the names into the implementation's namespace. This naming scheme was chosen over a '__nolibc_' prefix, as these functions are not an implementation detail but a documented interface meant to be used by applications. While this may break some existing users, adapting them should be straightforward. Given that nolibc is most-likely vendored, no unexpected breakage should happen. No in-tree users are affected. These conflicts happen when compiling some of the kernel selftests with nolibc. Signed-off-by: Thomas Weißschuh <linux@weissschuh.net> Acked-by: Willy Tarreau <w@1wt.eu> Link: https://patch.msgid.link/20260319-nolibc-namespacing-v1-1-33c22eaddb5e@weissschuh.net
43 lines
756 B
C
43 lines
756 B
C
/* SPDX-License-Identifier: LGPL-2.1 OR MIT */
|
|
/*
|
|
* Utsname definitions for NOLIBC
|
|
* Copyright (C) 2017-2021 Willy Tarreau <w@1wt.eu>
|
|
*/
|
|
|
|
/* make sure to include all global symbols */
|
|
#include "../nolibc.h"
|
|
|
|
#ifndef _NOLIBC_SYS_UTSNAME_H
|
|
#define _NOLIBC_SYS_UTSNAME_H
|
|
|
|
#include "../sys.h"
|
|
|
|
#include <linux/utsname.h>
|
|
|
|
/*
|
|
* int uname(struct utsname *buf);
|
|
*/
|
|
|
|
struct utsname {
|
|
char sysname[65];
|
|
char nodename[65];
|
|
char release[65];
|
|
char version[65];
|
|
char machine[65];
|
|
char domainname[65];
|
|
};
|
|
|
|
static __attribute__((unused))
|
|
int _sys_uname(struct utsname *buf)
|
|
{
|
|
return __nolibc_syscall1(__NR_uname, buf);
|
|
}
|
|
|
|
static __attribute__((unused))
|
|
int uname(struct utsname *buf)
|
|
{
|
|
return __sysret(_sys_uname(buf));
|
|
}
|
|
|
|
#endif /* _NOLIBC_SYS_UTSNAME_H */
|