similar to: [klibc:master] Add support for reboot syscall argument

Add support to the reboot command so an argument for the 4th parameter of the syscall can be passed around. --- usr/include/sys/reboot.h | 4 ++-- usr/klibc/reboot.c | 6 +++--- usr/utils/halt.c | 36 ++++++++++++++++++++++-------------- 3 files changed, 27 insertions(+), 19 deletions(-) diff --git a/usr/include/sys/reboot.h b/usr/include/sys/reboot.h index 3337d27..b46a1c5

While trying to port kexec cleanly to klibc, came across this syscall usage for reboot(2). Calling reboot directly simplifies the code. Signed-off-by: maximilian attems <max at stro.at> --- kexec/kexec-syscall.h | 18 ------------------ kexec/kexec.c | 3 ++- 2 files changed, 2 insertions(+), 19 deletions(-) v2: keep LINUX_REBOOT_CMD_KEXEC defines, thus no need of

On Nov 3, 2017, at 4:23 PM, Dovecot list <cr4shydlo+dovecot at gmail.com> wrote: > > Hello. > I try to migrate about 200G of mails from one server to another. > On the old i have Dovecot1 with Maildirs (without master pass etc.), on the > new one i setup dovecot2 with mdbox. I need now to migrate (partialy, not > all at once) mails from one to another. > I can't

As a new co-maintainer of klibc, I have just released version 2.0.5. The git repository remains at: https://git.kernel.org/pub/scm/libs/klibc/klibc.git A tarball will be available from the usual place later, but I'm not currently able to upload there. This new release fixes various build and run-time failures with current versions of Linux, gcc, and binutils on mips, sparc and x86; and

The following changes since commit 4d19974d7020488f63651244e1f9f51727c3f66c: [klibc] fwrite: fix typo in comment (2016-02-01 13:26:01 -0800) are available in the Git repository at: https://git.kernel.org/pub/scm/linux/kernel/git/bwh/klibc.git for-hpa for you to fetch changes up to 7b49d9729ff6b3118c57eb6fe52c4f186016cfa0: [klibc] x86_64: Use -Ttext-segment to avoid address collision

On Wed, 2020-07-08 at 08:37 +0200, Christian Eggers wrote: > libkeyutils is used by the keyctl command which is required for loading > keys into the kernel (e.g. for mounting an authenticated UBIFS as root > file system). > > libkeyutils usually invokes syscall() directly. As syscall() is not > provided by klibc, libkeyutils has to be slightly modified for using the > klibc

libkeyutils is used by the keyctl command which is required for loading keys into the kernel (e.g. for mounting an authenticated UBIFS as root file system). libkeyutils usually invokes syscall() directly. As syscall() is not provided by klibc, libkeyutils has to be slightly modified for using the klibc wrappers. Signed-off-by: Christian Eggers <ceggers at arri.de> ---

Hello. I try to migrate about 200G of mails from one server to another. On the old i have Dovecot1 with Maildirs (without master pass etc.), on the new one i setup dovecot2 with mdbox. I need now to migrate (partialy, not all at once) mails from one to another. I can't find any solution that i can use? I dont have master password, and i want to mikgrate all mailaccont each other. Can anyone

Currently the fs sync function (super.c:btrfs_sync_fs()) doesn''t wait for delayed work to finish before returning success to the caller. This change fixes this, ensuring that there''s no data loss if a power failure happens right after fs sync returns success to the caller and before the next commit happens. Steps to reproduce the data loss issue: $ mkfs.btrfs -f /dev/sdb3 $

--9jxsPFA5p3P2qPhR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I stripped down the insmod command from modules-init-tools for use with klibc. Rusty agreed to have this contributed to klibc. The second patch removes old style modules support. -- ciao, Marco --9jxsPFA5p3P2qPhR Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment;

With some hacks kexec-tools can compile against klibc. On the klibc side only this syscall addition is missing. The patch has been carried in OpenEmbedded klibc for some time. Signed-off-by: Thomas Kunze <thommycheck at gmx.de> Signed-off-by: Yuri Bushmelev <jay4mail at gmail.com> Signed-off-by: Andrea Adami <andrea.adami at gmail.com> Signed-off-by: maximilian attems <max at

The finit_module() system call was merged in Linux 3.8. This system call is similar to init_module(), but it allows to load Linux kernel modules from file descriptors. Signed-off-by: Nikita Ermakov <sh1r4s3 at mail.si-head.nl> --- usr/klibc/SYSCALLS.def | 1 + 1 file changed, 1 insertion(+) diff --git a/usr/klibc/SYSCALLS.def b/usr/klibc/SYSCALLS.def index c8ac9e0d..7a67b01f 100644 ---

The warnings in daemon were aggravating and risky for development (too easy to miss new ones) so I spent some time last week and today working on removing them. The first patch gets us down to almost no warnings with the original -Wall setting. That was by far the hardest part. Once I'd done that, I enabled nearly all of gcc's warnings via gnulib's warnings and manywarnings modules

I had a klibc build failure (on s390) because of include/sys/module.h and noticed that it still has the old system call interface for 2.4 style modutils. Is there any reason to keep that in klibc? This patch fixes the build problem by removing the old file and also makes it possible to build module-init-tools (after some tweaking there) against klibc. Arnd <>< =====

https://bugzilla.mindrot.org/show_bug.cgi?id=1535 Summary: rename doesn't fall back to rename syscall upon ENOSYS of link syscall Product: Portable OpenSSH Version: 5.1p1 Platform: ix86 OS/Version: Linux Status: NEW Keywords: patch Severity: normal Priority: P3 Component:

I keep getting the following error when I do a catalog run: err: Could not request certificate: SSL_connect SYSCALL returned=5 errno=0 state=SSLv2/v3 read server hello A No idea why its giving me this error. Any help would be appreciated. Thanks! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to

>>However, in case (2) the i386 guest kernel unconditionally goes for >>sysenter, and the hypervisor will accept this because CPUID has advertised >>SEP. *But* AMD CPUs do not support sysenter except in legacy mode! The >>correct thing to do is to use syscall. The hypervisor 32-on-64 compat code >>would accept CALLBACKTYPE_syscall, but the Linux i386 code here

(noticed during preparation of initial PAE-guest-on-64bit patches) The offset used to compare the return IP was apparently wrong; I didn''t actually test that things didn''t work as intended (or that they do now with this change), it just caught my eye that the UREGS_rip access a little further up in the same function was done with adjustment for the extra item on the stack, but

hello dtrace experts, I have a query on knowing the syscall corresponding to "mv" command. For instance "touch" or "vi" commands correspond to syscall::open (or) syscall::open64 entry. Please do let me know regarding the same. Thanks, Partha This message posted from opensolaris.org

Hello everyone, I have a few questions about syscall interception in Xen. Thanks for any advice/suggestion. Setting: CPU, Xen and PV Linux guest are all 64-bit (1) If a guest app uses "syscall" instruction to launch a system call to the guest kernel, is that behavior intercepted by Xen by default? If yes, could someone please point me to the related code in Xen for this interception?