History

bpf, tls: add tls header to tools infrastructure

Andrey reported a build error for the BPF kselftest suite when compiled on a machine which does not have tls related header bits installed natively: test_sockmap.c:120:23: fatal error: linux/tls.h: No such file or directory #include <linux/tls.h> ^ compilation terminated. Fix it by adding the header to the tools include infrastructure and add definitions such as SOL_TLS that could potentially be missing.

Daniel Borkmann committed 8 years ago

Commit 421f4291 parent 2c59f062 files · +86 −5Browse files

Showing the changes to tools/include/uapi (1 of 2 files). Show all

Unified · Split

tools/include/uapi/linux/tls.h+78−0
@@ -0,0 +1,78 @@
1+/* SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR Linux-OpenIB) */
2+/*
3+ * Copyright (c) 2016-2017, Mellanox Technologies. All rights reserved.
4+ *
5+ * This software is available to you under a choice of one of two
6+ * licenses. You may choose to be licensed under the terms of the GNU
7+ * General Public License (GPL) Version 2, available from the file
8+ * COPYING in the main directory of this source tree, or the
9+ * OpenIB.org BSD license below:
10+ *
11+ * Redistribution and use in source and binary forms, with or
12+ * without modification, are permitted provided that the following
13+ * conditions are met:
14+ *
15+ * - Redistributions of source code must retain the above
16+ * copyright notice, this list of conditions and the following
17+ * disclaimer.
18+ *
19+ * - Redistributions in binary form must reproduce the above
20+ * copyright notice, this list of conditions and the following
21+ * disclaimer in the documentation and/or other materials
22+ * provided with the distribution.
23+ *
24+ * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
25+ * EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
26+ * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
27+ * NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS
28+ * BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
29+ * ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
30+ * CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
31+ * SOFTWARE.
32+ */
33+
34+#ifndef _UAPI_LINUX_TLS_H
35+#define _UAPI_LINUX_TLS_H
36+
37+#include <linux/types.h>
38+
39+/* TLS socket options */
40+#define TLS_TX 1 /* Set transmit parameters */
41+#define TLS_RX 2 /* Set receive parameters */
42+
43+/* Supported versions */
44+#define TLS_VERSION_MINOR(ver) ((ver) & 0xFF)
45+#define TLS_VERSION_MAJOR(ver) (((ver) >> 8) & 0xFF)
46+
47+#define TLS_VERSION_NUMBER(id) ((((id##_VERSION_MAJOR) & 0xFF) << 8) | \
48+ ((id##_VERSION_MINOR) & 0xFF))
49+
50+#define TLS_1_2_VERSION_MAJOR 0x3
51+#define TLS_1_2_VERSION_MINOR 0x3
52+#define TLS_1_2_VERSION TLS_VERSION_NUMBER(TLS_1_2)
53+
54+/* Supported ciphers */
55+#define TLS_CIPHER_AES_GCM_128 51
56+#define TLS_CIPHER_AES_GCM_128_IV_SIZE 8
57+#define TLS_CIPHER_AES_GCM_128_KEY_SIZE 16
58+#define TLS_CIPHER_AES_GCM_128_SALT_SIZE 4
59+#define TLS_CIPHER_AES_GCM_128_TAG_SIZE 16
60+#define TLS_CIPHER_AES_GCM_128_REC_SEQ_SIZE 8
61+
62+#define TLS_SET_RECORD_TYPE 1
63+#define TLS_GET_RECORD_TYPE 2
64+
65+struct tls_crypto_info {
66+ __u16 version;
67+ __u16 cipher_type;
68+};
69+
70+struct tls12_crypto_info_aes_gcm_128 {
71+ struct tls_crypto_info info;
72+ unsigned char iv[TLS_CIPHER_AES_GCM_128_IV_SIZE];
73+ unsigned char key[TLS_CIPHER_AES_GCM_128_KEY_SIZE];
74+ unsigned char salt[TLS_CIPHER_AES_GCM_128_SALT_SIZE];
75+ unsigned char rec_seq[TLS_CIPHER_AES_GCM_128_REC_SEQ_SIZE];
76+};
77+
78+#endif /* _UAPI_LINUX_TLS_H */