search for: sigreturn

Hi, We have a few users experiencing locking problem. When starting Thunderbird, there is no new emails in Inbox. Dovecot createa a lock file /var/spool/mail/<user>.lock. It never completes openning Inbox. If closing the mail client, the open imap session does not get closed, nor the lock file get deleted. Here are the errors in log: dovecot: Oct 13 11:18:35 Warning: IMAP(user1): Our

Hi, I have run into an issue using puppet in an ldap environment and I am wondering if anyone else has run into the same issue. A number of the puppet clients in my testing environment are failing to apply new configurations because the puppet client is getting an ldap error. Currently, I am attempting to push a new bash_profile to my home directory and then set my username/group to then own the

...acd2099463f68d4 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Thu, 30 Apr 2020 13:31:32 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 25 Jul 2020 17:33:29 +0100 [klibc] alpha: Set sa_restorer for signals and disable executable stack Add a __sigreturn routine and point sa_restorer to it by default, so that the kernel doesn't create stack trampolines for signal return. With that done, we no longer need an executable stack. Signed-off-by: Ben Hutchings <ben at decadent.org.uk> --- usr/include/arch/alpha/klibc/archconfig.h | 3 +++ us...

...4800a8ac9c4dd74 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Thu, 30 Apr 2020 13:31:32 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Thu, 20 Aug 2020 23:22:58 +0100 [klibc] alpha: Set sa_restorer for signals and disable executable stack Add a __sigreturn routine and point sa_restorer to it by default, so that the kernel doesn't create stack trampolines for signal return. With that done, we no longer need an executable stack. Signed-off-by: Ben Hutchings <ben at decadent.org.uk> --- usr/include/arch/alpha/klibc/archconfig.h | 3 +++ us...

...k alpha does not support the SA_RESTORER flag, but allows specifiying a restorer callback as an additional parameter to rt_sigaction(). We should do this to avoid needing an executable stack. * Force the SA_SIGINFO flag on for all signal handlers, so that we can always return from them with rt_sigreturn * Define a __sigreturn() routine that calls rt_sigreturn * Pass that routine as the last argument to rt_sigaction() * Set KLIBCEXECSTACK=n Signed-off-by: Ben Hutchings <ben at decadent.org.uk> --- usr/include/arch/alpha/klibc/archconfig.h | 2 ++ usr/klibc/arch/alpha/Kbuild...

...= 0 write(1, "Executing last minute cleanups\n", 31Executing last minute cleanups ) = 31 tgkill(2974, 2974, SIGURG) = 0 --- SIGURG (Urgent I/O condition) @ 0 (0) --- rt_sigaction(SIGURG, {0x80a5cc0, [URG], SA_RESTART}, {0x80a5cc0, [URG], SA_RESTART}, 8) = 0 sigreturn() = ? (mask now []) == Destroying musiconhold processes;40mDestro"..., 59 ) = 59 tgkill(2974, 2974, SIGURG) = 0 --- SIGURG (Urgent I/O condition) @ 0 (0) --- rt_sigaction(SIGURG, {0x80a5cc0, [URG], SA_RESTART}, {0x80a5cc0, [URG], SA_RESTART}, 8) = 0...

...builds did for us. Here is a ktrace of the spinning imap process: topos:tmp# kdump 18248 imap EMUL "native" 18248 imap PSIG SIGALRM caught handler=0x1c03ff88 mask=0x0 18248 imap CALL setitimer(0,0xcfbcb3bc,0xcfbcb3ac) 18248 imap RET setitimer 0 18248 imap CALL sigreturn(0xcfbcb3ec) 18248 imap RET sigreturn JUSTRETURN 18248 imap PSIG SIGALRM caught handler=0x1c03ff88 mask=0x0 18248 imap CALL setitimer(0,0xcfbcb3bc,0xcfbcb3ac) 18248 imap RET setitimer 0 18248 imap CALL sigreturn(0xcfbcb3ec) 18248 imap RET sigreturn JUSTRETURN If any...

...+ usr/klibc/README.klibc | 2 +- usr/klibc/arch/avr32/Kbuild | 8 ++ usr/klibc/arch/avr32/MCONFIG | 16 ++++ usr/klibc/arch/avr32/crt0.S | 20 +++++ usr/klibc/arch/avr32/setjmp.S | 30 ++++++++ usr/klibc/arch/avr32/sigreturn.S | 15 ++++ usr/klibc/arch/avr32/syscall.S | 24 ++++++ usr/klibc/arch/avr32/sysstub.ph | 31 ++++++++ usr/klibc/arch/avr32/vfork.S | 26 +++++++ 14 files changed, 359 insertions(+), 1 deletions(-) create mode 100644 usr/include/arch/avr32/klibc/...

...============= 0.078863 --- SIGURG (Urgent I/O condition) @ 0 (0) --- 0.000052 write(1, "Urgent handler\n", 15) = 15 0.000566 rt_sigaction(SIGURG, {0x80a5d60, [URG], SA_RESTORER|SA_RESTART, 0x34aa58}, {0x80a5d60, [URG], SA_RESTORER|SA_RESTART, 0x34aa58}, 8) = 0 0.000181 sigreturn() = ? (mask now []) 0.000143 read(0, 0xbff63c2b, 1) = ? ERESTARTSYS (To be restarted) 311.584380 --- SIGURG (Urgent I/O condition) @ 0 (0) --- 0.000056 write(1, "Urgent handler\n", 15) = 15 0.000634 rt_sigaction(SIGURG, {0x80a5d60, [URG], SA_RESTORER|SA_...

...| 127 ++++++++++++++++++++++++++++ usr/klibc/arch/x86_64/MCONFIG | 35 ++++++++ usr/klibc/arch/x86_64/Makefile.inc | 18 ++++ usr/klibc/arch/x86_64/crt0.S | 22 +++++ usr/klibc/arch/x86_64/setjmp.S | 54 ++++++++++++ usr/klibc/arch/x86_64/sigreturn.S | 15 +++ usr/klibc/arch/x86_64/syscall.S | 28 ++++++ usr/klibc/arch/x86_64/sysstub.ph | 23 +++++ usr/klibc/arch/x86_64/vfork.S | 26 ++++++ 14 files changed, 539 insertions(+), 0 deletions(-) diff --git a/usr/include/arch/x86_64/klibc/archcon...

https://bugzilla.samba.org/show_bug.cgi?id=2766 ------- Additional Comments From paul@debian.org 2005-06-02 08:47 ------- It seems to be looping in userspace (no system calls, hence strace doesn't show anything). Could you try ltrace instead of strace, that should show what library functions (if any) are being called which may help. -- Configure bugmail:

...7 asterisk CALL gettimeofday(0x281c8e88,0) > 74987 asterisk RET gettimeofday 0 > 74987 asterisk CALL sigprocmask(0x3,0x281c8ef8,0) > 74987 asterisk RET sigprocmask 0 > 74987 asterisk CALL poll(0x80cf000,0x4,0) > 74987 asterisk RET poll 0 > 74987 asterisk CALL sigreturn(0xbfa87cec) > 74987 asterisk RET sigreturn JUSTRETURN > 74987 asterisk CALL poll(0x851e400,0x1,0) > 74987 asterisk RET poll 1 > 74987 asterisk CALL read(0x15,0x2845e060,0x100) > 74987 asterisk GIO fd 21 read 0 bytes > > > ----------------- > > ____...

...diff --git a/usr/include/klibc/sysconfig.h b/usr/include/klibc/sysconfig.h index c91d5b85..4e38b1fd 100644 --- a/usr/include/klibc/sysconfig.h +++ b/usr/include/klibc/sysconfig.h @@ -154,7 +154,8 @@ * * Some architectures, like x86-64 and some i386 Fedora kernels, * do not provide a default sigreturn, and therefore must have - * SA_RESTORER set. + * SA_RESTORER set. On others, the default sigreturn requires an + * executable stack, which we should avoid. */ #ifndef _KLIBC_NEEDS_SA_RESTORER # define _KLIBC_NEEDS_SA_RESTORER 0 diff --git a/usr/klibc/sigaction.c b/usr/klibc/sigaction.c index...

...= 1410 geteuid32() = 1410 setresuid32(0, 0, -1) = 0 geteuid32() = 0 kill(11697, SIGUSR1) = 0 --- SIGUSR1 (User defined signal 1) @ 0 (0) --- write(24, "\n", 1) = 1 sigreturn() = ? (mask now [FPE USR2 PIPE]) setresuid32(1410, 1410, -1) = 0 geteuid32() = 1410 getuid32() = 1410 write(5, "\0\0\0/\377SMB/\0\0\0\0\210\1\310\0\0\0\0\0\0\0\0\0\0\0"..., 51) = 51 fcntl...

...(Segmentation fault) @ 0 (0) --- 15154 +++ killed by SIGSEGV +++ 15153 --- SIGCHLD (Child exited) @ 0 (0) --- 15153 waitpid(-1, [WIFSIGNALED(s) && WTERMSIG(s) == SIGSEGV && WCOREDUMP(s)], WNOHANG) = 15154 15153 waitpid(-1, 0xbffff864, WNOHANG) = -1 ECHILD (No child processes) 15153 sigreturn() = ? (mask now []) 15153 exit_group(0) = ? 1) It's a bother that it first daemonizes itself and then checks the config etc., giving no feedback whatsoever that it's not running. 2) core dumps are never good :-( Here'a a proposed patch to...

...) = 22 2705 write(2, "There may be bound raw devices l"..., 71) = 71 2705 write(2, "using the raw(8) command.\n", 26) = 26 2705 rt_sigaction(SIGSEGV, {SIG_DFL}, {0x402f0b30, [SEGV], SA_RESTORER|SA_RESTART, 0x40346988}, 8) = 0 2705 kill(2705, SIGSEGV) = 0 2705 sigreturn() = ? (mask now [RTMIN]) 2705 --- SIGSEGV (Segmentation fault) @ 0 (0) --- 2705 +++ killed by SIGSEGV +++ ***** Indeed 8,32 points to /dev/sdc which is the wrong device, it doesn't exist on this node. The shared device is /dev/sdb. Using ocfstool on the other node work...

...arch/i386/libgcc/__muldi3.S | 34 ++++++++ usr/klibc/arch/i386/libgcc/__negdi2.S | 21 +++++ usr/klibc/arch/i386/open.S | 29 +++++++ usr/klibc/arch/i386/openat.S | 26 ++++++ usr/klibc/arch/i386/setjmp.S | 58 ++++++++++++++ usr/klibc/arch/i386/sigreturn.S | 15 ++++ usr/klibc/arch/i386/socketcall.S | 55 +++++++++++++ usr/klibc/arch/i386/syscall.S | 69 ++++++++++++++++ usr/klibc/arch/i386/sysstub.ph | 26 ++++++ usr/klibc/arch/i386/varsyscall.S | 36 +++++++++ usr/klibc/arch/i386/vfork.S...

We've seen Samba crash and burn twice in the last 48 hours - it just started happening, and we have no idea what might be causing it. I'm hoping that someone will recognize this problem. Platform: we are running RedHat Enterprise Server, with Samba 3.0.7. We're using security=domain in an old-style NT4 domain environment. The symptom that we're seeing is that the number of

...k(int, const sigset_t *, sigset_t *, size_t); diff --git a/usr/klibc/arch/alpha/Kbuild b/usr/klibc/arch/alpha/Kbuild index 89386aea..715a430c 100644 --- a/usr/klibc/arch/alpha/Kbuild +++ b/usr/klibc/arch/alpha/Kbuild @@ -9,7 +9,7 @@ always := crt0.o targets := crt0.o -klib-y := pipe.o setjmp.o sigreturn.o syscall.o sysdual.o +klib-y := pipe.o sigaction.o setjmp.o sigreturn.o syscall.o sysdual.o # Special CFLAGS for the divide code DIVCFLAGS = $(KLIBCREQFLAGS) $(KLIBCARCHREQFLAGS) \ diff --git a/usr/klibc/arch/alpha/sigaction.c b/usr/klibc/arch/alpha/sigaction.c new file mode 100644 index 00000...

...p;& WEXITSTATUS(s) == 255}], WNOHANG) = 28446 28461 close(3 <unfinished ...> 28445 waitpid(-1, <unfinished ...> 28461 <... close resumed> ) = 0 28445 <... waitpid resumed> 0xbfffd2f4, WNOHANG) = 0 28461 lstat64("...", <unfinished ...> 28445 sigreturn( <unfinished ...> 28461 <... lstat64 resumed> {st_mode=S_IFREG|0600, st_size=262144, ...}) = 0 28445 <... sigreturn resumed> ) = ? (mask now []) 28461 lchown32("...", 8, 12 <unfinished ... > 28445 write(4, "\10\0YK\n\0\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0...