search for: syscalling

GEN usr/klibc/syscalls/SYSCALLS.i GEN usr/klibc/syscalls/syscalls.nrs GEN usr/klibc/syscalls/typesize.c KLIBCCC usr/klibc/syscalls/typesize.o OBJCOPY usr/klibc/syscalls/typesize.bin GEN usr/klibc/syscalls/syscalls.mk GEN usr/klibc/syscalls/SYSCALLS.i GEN usr/klibc/syscalls/syscalls.nrs GEN usr/klibc/syscalls/typesize.c KLIBCCC

Factor out all kernel specific path's (those containing usr/) into two variables: KLIBSRC + KLIBINC. Set the variables in a kernel spcific Kbuild file. Sam commit e6f989c1597a837f4aecbd11083697184c089611 tree 93f88d7564bb9e4d4bc95fd455b842d0bd0fdc54 parent 8151f4a98f82fba4fe3b949f49da4ab8bba71501 author Sam Ravnborg <sam@mars.(none)> Thu, 28 Jul 2005 23:36:07 +0200 committer Sam

Le 30/05/2019 ? 01:23, Mauro Carvalho Chehab a ?crit?: > Mostly due to x86 and acpi conversion, several documentation > links are still pointing to the old file. Fix them. > > Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung at kernel.org> > --- > Documentation/acpi/dsd/leds.txt | 2 +- > Documentation/admin-guide/kernel-parameters.rst | 6

Le 30/05/2019 ? 01:23, Mauro Carvalho Chehab a ?crit?: > Mostly due to x86 and acpi conversion, several documentation > links are still pointing to the old file. Fix them. > > Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung at kernel.org> > --- > Documentation/acpi/dsd/leds.txt | 2 +- > Documentation/admin-guide/kernel-parameters.rst | 6

I'm trying to use rsync to back up a Mac OS X machine to a Linux server. I've used the instructions at http://www.bombich.com/mactips/rsync.html to patch and install rsync 3.0.2 to support HFS+ attributes and forks on the client. I was assuming the Linux box needed the same version, and so tried compiling the patched rsync but got the following: syscall.c: In function

Em Mon, 3 Jun 2019 09:34:15 +0200 Christophe Leroy <christophe.leroy at c-s.fr> escreveu: > Le 30/05/2019 ? 01:23, Mauro Carvalho Chehab a ?crit?: > > Mostly due to x86 and acpi conversion, several documentation > > links are still pointing to the old file. Fix them. > > > > Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung at kernel.org> > > ---

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> ---

On Saturday, 25 July 2020, 23:36:33 CEST, Ben Hutchings wrote: > On Wed, 2020-07-08 at 08:37 +0200, Christian Eggers wrote: > > ... > > libkeyutils usually invokes syscall() directly. As syscall() is not > > provided by klibc, libkeyutils has to be slightly modified for using the > > klibc wrappers. > > Wouldn't it be more useful for klibc to implement

I'm trying to do a full rebase (history clean) of the klibc kernel tree, and came across the following changesets between klibc 1.3.12 and .16: --- a/usr/klibc/arch/s390/syscall.c +++ b/usr/klibc/arch/s390/syscall.c @@ -11,6 +11,6 @@ long int __syscall_common(long int err) { if ((unsigned long)(err) < (unsigned long)(-125)) return err; - errno = err; +

hi fnds, i want to print the filenames on which the stat system call is acting when a stat system call is invoked. can anyone can help me this regard. Thanks jeevan

Dear dtrace Experts, I have seen some dtrace utilities like opensnoop and execsnoop etc. My interest is to write a simple script that can snoop the files which uses the 3 syscalls like open,create,unlink. I have gone through dtrace oneliners that can do the same : dtrace -n ''syscall::open*:entry { printf("%s %s",execname,copyinstr(arg0));}'' dtrace -n

Debian: (Closes: #334917) Signed-off-by: Thorsten Glaser <tg at mirbsd.de> --- usr/klibc/arch/m68k/syscall.S | 42 +++++++++++++++++++++++++++++++++------- usr/klibc/arch/m68k/vfork.S | 13 +++-------- 2 files changed, 38 insertions(+), 17 deletions(-) diff --git a/usr/klibc/arch/m68k/syscall.S b/usr/klibc/arch/m68k/syscall.S index 966c92d..f468678 100644 ---

On July 27, 2020 2:43:36 AM PDT, Christian Eggers <ceggers at arri.de> wrote: >On Saturday, 25 July 2020, 23:36:33 CEST, Ben Hutchings wrote: >> On Wed, 2020-07-08 at 08:37 +0200, Christian Eggers wrote: >> > ... >> > libkeyutils usually invokes syscall() directly. As syscall() is not >> > provided by klibc, libkeyutils has to be slightly modified for

Hi. I have following errors in my log file: Mar 22 05:33:11 xentest libvirtd: 05:33:11.518: error : failed Xen syscall topology cpuset syntax error Mar 22 05:33:21 xentest libvirtd: 05:33:21.418: error : failed Xen syscall topology cpuset syntax error Mar 22 05:33:41 xentest libvirtd: 05:33:41.274: error : failed Xen syscall topology cpuset syntax error Mar 22 05:33:41 xentest libvirtd:

tag 334917 = patch thanks Hi, I?ve fixed the m68k syscall of klibc and made it able to use six-argument syscalls like mmap2. However, I could not yet fully test it (only mostly; opendir() specifically fails) due to: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47533 @m68k porters: Please have a look at the gcc bug as well. @klibc: Please apply the patch, it?s better than what we have, and

I have just started my first ''serious'' dtrace script and can use some advice. I want to have a probe triggered when close() occurs after a succesfull write of /etc/hosts ( I want to regenerate the nameserver zone files from /etc/hosts after it has changed) At the moment I have the following code: syscall::open*:entry, syscall::creat*:entry { self->file=arg0;

what is differenct between syscall::write:entry fbt::write:entry are the two probe fires at the same place. -- This message posted from opensolaris.org

> From the provided documentation I understood that in memory data > structures of a PNaCl program are incompatible to the host program because > ABIs are different (e.g. PNaCl pointers are always 32-bit even when running > on x86_64 platform). > So PNaCl program can't access any data structures of the host program > directly. The only communication way is by using syscalls,

Hi, I was trying to determine how Wine captures syscalls, and I found this thread: http://www.winehq.org/pipermail/wine-users/2002-October/009077.html The answer was that Wine *doesn't* deal with syscalls, and relies on the application never directly making a syscall, but instead calling into the standard system libraries (Win32). Is this still true today? I'm surprised that Wine can

Reimplement __common_syscall in assembler. The 32-bit ABI says that the fifth and sixth arguments to the function are passed on the stack, but our syscall ABI says they are passed in %arg4 and %arg5 like the 64-bit ABI. Also, tried to optimize the code slightly by making use of the cmpb delay slot to load the errno return of -1. Signed-off-by: Kyle McMartin <kyle@parisc-linux.org> diff