| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The software version for packaging purposes is consituted from the
following rules:
- If the version information (from Git tags or the embedded version
header file) is available, the version number for the packaging is
set to those found version information.
- If there isn't any version information available (e.g. missing Git
tags), the version number for the packaging is set to '0.0' to
represent an unkown version number.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change links the dnbd3-server with 'libatomic' to add support for
atomic operations not supported by hardware (especially 32-bit hardware
architectures, such as ARM). Thus the dnbd3-server can also run on a
Raspberry Pi 1 running Rasperry Pi OS.
Note that the dnbd3-server is still linked to the libatomic, even if the
hardware supports atomic operations. In this case, the compiler resolves
atomic operations and replaces them automatically with specific built-in
functions. This unnecessary linkage can be removed in the future if the
GCC supports an upcoming option called automatic linking of libatomic
(--enable-autolink-libatomic).
|
| |
|
|
|
|
|
| |
This patch adds support to locate the build directory for generated
artifacts out of the original checked out Git source code repository.
|
|
|
|
|
|
|
|
|
| |
This patch fixes the issue that a Docker container for the dnbd3
components (including the dnbd3-server) can be built with missing
dnbd3-server's binary. Since the created Docker container starts
the missing binary, it will fail. Therefore, a built of the Docker
image is only possible if building of the dnbd3-server is enabled
(CMAKE option DNBD3_SERVER=ON).
|
| |
|
|
|
|
|
|
|
|
| |
C flags which are set by the environment variable CFLAGS have been
ignored by CMake since the corresponding CMake variable CMAKE_C_FLAGS
was not extended with those passed flags, but have been overwritten by a
fixed set of flags. This patch fixes the overwrite of CMAKE_C_FLAGS and
extends its content with the C flags passed in the environment variable.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds the following CMake targets
- package
- source
to build bundeled packages. Those packages contain either all built
binary artifacts or all source files for source code distribution. Both
CMake targets are available in Release build configuration.
|
|
|
|
|
| |
The afl-fuzz support for the dnbd3-server requires an AFL C compiler
like afl-gcc and can be enabled with the CMake option DNBD3_SERVER_AFL.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This change restructures the source code directories, separates shared
form non-shared application code and adds CMake dependencies. These
dependencies allow the tracking of changes and trigger a rebuild of
those build targets where changed files are involved.
WARNING: Note that the support of the DNBD3_SERVER_AFL build option is
not supported yet. Thus, the option should be never turned on.
|
|
|
|
|
|
|
| |
This change enables compiler optimization (-O2) in Release builds to fix
the following error warning:
_FORTIFY_SOURCE requires compiling with optimization (-O)
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change converts all debug messages to support the Linux kernel's
dynamic debug feature. Debug messages can be enabled or disabled by
the debug feature if the
- kernel module is built in debug mode (EXTRA_CFLAGS=-g -DDEBUG)
- Linux kernel supports dynamic debug (CONFIG_DYNAMIC_DEBUG is set)
This patch removes outdated kernel compatibility macros (used for Linux
kernels in version 4.x) and cleans up the kernel module's code.
|
|
|
|
|
|
|
|
|
|
|
| |
This converts the dnbd3 kernel module driver to use the blk-mq
infrastructure, which allows the dnbd3 kernel module driver to be
compatible with Linux kernels in version 5.x or later. The conversion of
the implementation uses one hardware queue to preserve the existing
send/receive and load-balancing logic, but can be scaled up in the
future. In addition to that, time measurements in the implementation are
converted to ktime based accessors to replace the use of deprecated time
interfaces.
|
| |
|
|
|
|
|
| |
Still needs some cleanup and optimizations, variable naming sucks,
comments, etc.
|
| |
|
|
|
|
|
| |
BULLSHIT
BULLSHIT
|
| |
|
|
|
|
| |
Added new query type q=version, which uses the STATS access rights.
|
|\ |
|
| | |
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
AFL is an instrumenting fuzzer.
It expects to pass input to the program to be tested
via command line (file name) or via stdin. This adds
support for reading messages that normally would arrive
via network directly from stdin. In this mode, the server
is pretty useless otherwise.
http://lcamtuf.coredump.cx/afl/
|
|
|
|
|
|
|
| |
Simple and lean interface, no bloat, noice.
Slighly modified to use a simple string struct
for passing around strings that are not null
terminated, instead of separate char* and length.
|
|
|
|
|
|
| |
We only used it for CRC-32, so now the source
tree includes a stripped down version of the crc32
code from the zlib project.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We steal 8 bits from the request offset to count hops when requests
get relayed by proxies. This still leaves plenty of bits for the
offset (56 bits, supporting images of up to 72 petabytes).
This is used to detect proxy cycles. The algorithm is not perfect
but should prevent endless relays of the same request.
This is backwards compatible to old clients and servers, as the server
only ever sets the hopcount in relayed requests if the upstream server
is using protocol version 3 or newer, and clients are automatically
upwards compatible as there is practically no image larger than 74PB,
so the newly introduced hop count field is always 0 even in requests
from old clients.
|
|
|
|
|
|
| |
turn them on/off
Use either cmake -DBUILD_*=ON/OFF, or handle via ccmake's gui
|