* 0001-kabi-drop-page_counter-size-assertion-for-non-SMP.patch
- Use git tag and offset for version string
- Merge opensuse-kernel/SLE15-SP6 68036e061fb1a
- lkl: link tests against common private library
- lkl: fix hijack and zpoline parallel builds
- lkl: tests: fix net setup_backend return status
- lkl: tests: drop sleep before lklfuse unmount
- Add ID_FS_UUID based locking to avoid duplicate mounts (bsc#1237471)
* lkl: tests: add lklfuse_lock_conflict test
* lkl: systemd: use lklfuse lock parameter
* lklfuse: add lock parameter to avoid duplicate mounts
- Drop upstreamed patches:
* 0001-lkl-tests-drop-unused-lkl_test.fn-parameters.patch
* 0001-lkl-hijack-explicitly-build-with-std-gnu11.patch
OBS-URL: https://build.opensuse.org/package/show/filesystems/lkl?expand=0&rev=23
- lkl: tests: handler lkl_init failures
- lkl: remove string functions duplicate implementation
- lkl: Remove use of CONFIG_NO_BOOTMEM
- lkl: Remove use of CONFIG_HAVE_MEMBLOCK
- lkl: Remove use of CONFIG_ARCH_NO_COHERENT_DMA_MMAP
- lkl: Remove use of CONFIG_FLAT_NODE_MEM_MAP
- lkl: Remove use of CONFIG_RWSEM_GENERIC_SPINLOCK
- lkl: fix lklfuse.sh umount
OBS-URL: https://build.opensuse.org/package/show/filesystems/lkl?expand=0&rev=15
- lkl: Define symbols for string utilities
- Fix OUTPUT environment variable for LKL build.
- lkl: hijack: move dbg.c code into dbg_handler.c
- lkl: hijack: move dbg_handler out of liblkl
- lkl: Remove the stat symbol hijack
- Add LKL arch implementation of memmove.
- lkl: fix zpoline runtime issue missing libgcc_s.so
- lkl: fix install headers issue on Windows
- lkl: add android/binder.h and mman.h to headers_install
* Rebase without pulling in binder fuzzer and MMU features
- lkl: fix windows python issue (freeze_support)
OBS-URL: https://build.opensuse.org/package/show/filesystems/lkl?expand=0&rev=11
extensively as possible with minimal effort and reduced maintenance overhead.
Examples of how LKL can be used are: creating userspace applications (running on
Linux and other operating systems) that can read or write Linux filesystems or
can use the Linux networking stack, creating kernel drivers for other operating
systems that can read Linux filesystems, bootloaders support for reading/writing
Linux filesystems, etc.
With LKL, the kernel code is compiled into an object file that can be directly
linked by applications. The API offered by LKL is based on the Linux system call
interface.
WARNING: LKL is EXPERIMENTAL; using it could cause data corruption!
OBS-URL: https://build.opensuse.org/package/show/filesystems/lkl?expand=0&rev=1
