From owner-freebsd-hackers@freebsd.org Tue Nov 17 16:25:17 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A780BA31679 for ; Tue, 17 Nov 2015 16:25:17 +0000 (UTC) (envelope-from peter.blok@bsd4all.org) Received: from mail.bsd4all.org (mail.bsd4all.org [78.47.125.12]) by mx1.freebsd.org (Postfix) with ESMTP id 6E0FB1E10 for ; Tue, 17 Nov 2015 16:25:17 +0000 (UTC) (envelope-from peter.blok@bsd4all.org) Received: from mail.bsd4all.org (localhost [127.0.0.1]) by mail.bsd4all.org (Postfix) with ESMTP id 87A442B1ED for ; Tue, 17 Nov 2015 17:25:16 +0100 (CET) X-Virus-Scanned: amavisd-new at bsd4all.org Received: from mail.bsd4all.org ([127.0.0.1]) by mail.bsd4all.org (newnas.bsd4all.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gaywOtGNHVhs for ; Tue, 17 Nov 2015 17:25:16 +0100 (CET) Received: from [192.168.1.64] (unknown [192.168.1.64]) by mail.bsd4all.org (Postfix) with ESMTPSA id 26B232B1E5 for ; Tue, 17 Nov 2015 17:25:16 +0100 (CET) From: Peter Blok Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: regression after FreeBSD-EN-15:17.libc Message-Id: Date: Tue, 17 Nov 2015 17:25:14 +0100 To: freebsd-hackers@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Nov 2015 16:25:17 -0000 Dear hackers, I have a strange problem with signal handling after the above errata was = implemented. It exposes itself after a slogin to a = FreeBSD-10.2-RELEASE-p7 and pressing Ctrl-C. It terminates the csh and = disconnects. This happens on two systems, one physical Octacore Atom and = on a virtual system at Hetzner. Both systems are in production and = amd64. Sources are in sync with svn. .cshrc is standard. I have tried to setup different test systems - one quad core Xeon and = one VMWare Fusion, running the exact same code, but they don=E2=80=99t = exhibit the problem. Besides the termination of the csh, I have seen corruptions in a db5 = database, after reboots. For example the sshguard database was garbled = after reboot. My suspicion is that it is signal related, caused by = reboot. This is why I am investigating further. I had a feeling it happened after the above errata change was = implemented. If I backout the changes everything works ok. If I put them = back in, it fails again. Checked the changes, but I can=E2=80=99t see anything wrong with them in = relation to the problem. Some other data points. - it doesn=E2=80=99t happen with ksh93 - it doesn=E2=80=99t happen after "exec csh -F=E2=80=9D which = doesn=E2=80=99t use vfork At one time I used ktrace and noticed the signal was delivered twice. I=E2=80=99ll make an exact clone of the Hetzner image and try to = reproduce it, but any other advice is welcome. Peter=