lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:   Fri, 19 Apr 2019 02:08:40 +0800
From:   Wang YanQing <udknight@...il.com>
To:     davem@...emloft.net
Cc:     netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH] uapi:libc-compat.h: Correct the comment about the value of
 __UAPI_DEF_FOO

In reality, when the userspace libc header has been included first, we need
to set the value of guard macros to 0, and set the value of guard macros to
1 when uapi header comes first.

Signed-off-by: Wang YanQing <udknight@...il.com>
---
 include/uapi/linux/libc-compat.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/include/uapi/linux/libc-compat.h b/include/uapi/linux/libc-compat.h
index 8254c93..ba10eede 100644
--- a/include/uapi/linux/libc-compat.h
+++ b/include/uapi/linux/libc-compat.h
@@ -25,8 +25,8 @@
  *     userspace libc header has been included first.
  *
  * (c) If the userspace libc header has been included first define a set of
- *     guard macros of the form __UAPI_DEF_FOO and set their values to 1, else
- *     set their values to 0.
+ *     guard macros of the form __UAPI_DEF_FOO and set their values to 0, else
+ *     set their values to 1.
  *
  * (d) Back in the UAPI header with the conflicting definitions, guard the
  *     definitions with:
-- 
1.8.5.6.2.g3d8a54e.dirty

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ