- 10 Dec, 2018 40 commits
-
-
Tobin C. Harding authored
Currently the 'Coding Style' section mentions only the kernel coding style. We have additions on top on this outlined in CODING_STYLE.md. We should direct readers to this document as well as the kernel docs. Direct readers to CODING_STLYE.md in the 'Coding Style' section. Signed-off-by:Tobin C. Harding <me@tobin.cc>
-
Tobin C. Harding authored
Currently we link to a URL for v4.10 of the kernel docs. Since we already mention the kernel tree we should link to the _latest_ kernel docs online instead of a fixed past version. Link to latest online kernel docs tracking the mainline instead of past fixed version. Signed-off-by:Tobin C. Harding <me@tobin.cc>
-
Tobin C. Harding authored
Kernel coding style guide filename is stale, this file has been renamed in the kernel tree. While this file still exists we should use the new filename. Update reference to kernel coding style guide to use the new file name. Signed-off-by:Tobin C. Harding <me@tobin.cc>
-
Christian Brauner authored
Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com> Cc: Serge Hallyn <serge@hallyn.com>
-
Christian Brauner authored
String not null terminated Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
We don't want to link caps.{c,h} against utils.{c,h} for the sake of our static builds init.lxc.static. This means lxc_write_nointr() will not be available. So handle it EINTR. Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
We don't want to link log.{c,h} against utils.{c,h} for the sake of our static builds init.lxc.static. This means lxc_write_nointr() will not be available. So handle it EINTR. Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Rafał Miłecki authored
It's a valid case to call nla_put() with NULL data and 0 len. It's done e.g. in the nla_put_attr(). There has to be a check for data in nla_put() as passing NULL to the memcpy() is not allowed. Even if length is 0, both pointers have to be valid. For a reference see C99 standard (7.21.1/2), it says: "pointer arguments on such a call shall still have valid values". Reported-by:
Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us> Signed-off-by:
Rafał Miłecki <rafal@milecki.pl> [christian.brauner@ubuntu.com: adapted commit message] Signed-off-by:
Christian Brauner <christian.brauner@ubuntu.com>
-
2xsec authored
Signed-off-by:2xsec <dh48.jeong@samsung.com>
-
2xsec authored
Explicit null dereferenced Signed-off-by:2xsec <dh48.jeong@samsung.com>
-
Christian Brauner authored
This means they need to be added for remount and for fresh mounts. Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
2xsec authored
Signed-off-by:2xsec <dh48.jeong@samsung.com>
-
Christian Brauner authored
Unchecked return value Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
Unchecked return value Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
2xsec authored
Explicit null dereferenced Signed-off-by:2xsec <dh48.jeong@samsung.com>
-
Christian Brauner authored
Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
Christian Brauner authored
Signed-off-by:Christian Brauner <christian.brauner@ubuntu.com>
-
2xsec authored
Let's ensure that we always use the thread-safe strerror_r() function and add an approriate macro. Additionally, define SYS*() macros for all log levels. They will use the new macro and ensure thread-safe retrieval of errno values. Signed-off-by:
2xsec <dh48.jeong@samsung.com> [christian.brauner@ubuntu.com: simplify lxc_log_strerror_r macro] Signed-off-by:
Christian Brauner <christian.brauner@ubuntu.com>
-
2xsec authored
Signed-off-by:2xsec <dh48.jeong@samsung.com>
-
2xsec authored
Signed-off-by:2xsec <dh48.jeong@samsung.com>
-