Your message dated Fri, 07 Apr 2017 15:50:39 +0000 with message-id <[email protected]> and subject line Bug#858400: fixed in gnupg2 2.1.20-3 has caused the Debian Bug report #858400, regarding gpgscm fails on s390x due to new vector representation to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 858400: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858400 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: gnupg2 Version: 2.1.19-3 Control: -1 tags + help On Tue 2017-03-21 17:32:27 -0400, Daniel Kahn Gillmor wrote: > but since the upgrade to 2.1.19-3 in experimental, we're seeing the the > segfault on s390x. > > I'm not even sure how to interpret the error message: is it saying that > make itself Segfaulted, or that gpgscm segfaulted? > > I've connected to zelenka to try to reproduce the problem directly on > s390x but i haven't been able to get there yet. OK, i've managed to reproduce some of the failures (intermittently) on a sid chroot (named "gnupg2-xcheck-segfault") in zelenka. With the source of 2.1.19-3 in /home/dkg/src/gnupg2/gnupg2, and having built the package out-of-tree in /home/dkg/src/gnupg2/gnupg2/build (via debian/rules), i repeatedly run just the first two simple test suites From /home/dkg/src/gnupg2/gnupg2/: LC_ALL=C EXEEXT= PATH=../gpgscm:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games srcdir=/home/dkg/src/gnupg2/gnupg2/build/../tests/openpgp objdir=/home/dkg/src/gnupg2/gnupg2/build GPGSCM_PATH=/home/dkg/src/gnupg2/gnupg2/build/../tests/gpgscm:/home/dkg/src/gnupg2/gnupg2/build/../tests/openpgp /home/dkg/src/gnupg2/gnupg2/build/tests/gpgscm/gpgscm run-tests.scm version.scm The failures are intermittent -- sometimes no failures, sometimes both run-tests.scm and version.scm fail, sometimes only one of them. In one example, i got this result: PASS: setup.scm gpgscm: error running 'version.scm': terminated FAIL: version.scm 1 tests run, 0 succeeded, 1 failed, 0 skipped. Failed tests: version.scm and then looking in dmesg, i see the following log: [1099865.715125] User process fault: interruption code 0x4003B in gpgscm[2aae2582000+37000] [1099865.715135] failing address: 00000000196d1000 TEID: 00000000196d1800 [1099865.715138] Fault in primary space mode while using user ASCE. [1099865.715141] AS:000000007feec1c7 R3:0000000000000024 [1099865.715145] CPU: 0 PID: 7395 Comm: gpgscm Not tainted 3.16.0-4-s390x #1 Debian 3.16.39-1+deb8u2 [1099865.715148] task: 00000000fb6ea108 ti: 000000003d600000 task.ti: 000000003d600000 [1099865.715151] User PSW : 0705200180000000 000002aae259450a [1099865.715154] R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 EA:3 User GPRS: 000002ab196c6888 000000000000003f 00000000196d1588 0000000000000007 [1099865.715160] 000002aae2596876 0000000000000001 0000000000000008 000002ab196c6888 [1099865.715163] 000002ab196c6868 0000000000000008 0000000000000007 000002ab196c6740 [1099865.715166] 000003fffd59c000 000002ab196c6888 000002aae25968ce 000003ffff893098 [1099865.715175] User Code: 000002aae25944fe: 0707 bcr 0,%r7 000002aae2594500: a718003f lhi %r1,63 #000002aae2594504: ebeff0700024 stmg %r14,%r15,112(%r15) >000002aae259450a: 54102000 n %r1,0(%r2) 000002aae259450e: a7fbff60 aghi %r15,-160 000002aae2594512: a71e0017 chi %r1,23 000002aae2594516: a7740016 brc 7,2aae2594542 000002aae259451a: e33020080021 clg %r3,8(%r2) [1099865.715286] Last Breaking-Event-Address: [1099865.715301] [<000002aae25968c8>] 0x2aae25968c8 I have no idea what this means :( Any suggestions? The failures are intermittent enough that i imagine just a series of repeated givebacks *might* result in one successful test, but that isn't very satisfying. I'm reporting this to the BTS so that we have someplace specific to track the problem. Please drop [email protected] from any followup! Hoping for some help, --dkg
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---Source: gnupg2 Source-Version: 2.1.20-3 We believe that the bug you reported is fixed in the latest version of gnupg2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Kahn Gillmor <[email protected]> (supplier of updated gnupg2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Fri, 07 Apr 2017 11:36:51 -0400 Source: gnupg2 Binary: gnupg-agent scdaemon gpgsm gnupg gnupg2 gpgv gpgv2 dirmngr gpgv-udeb gpgv-static gpgv-win32 gnupg-l10n Architecture: source Version: 2.1.20-3 Distribution: experimental Urgency: medium Maintainer: Debian GnuPG Maintainers <[email protected]> Changed-By: Daniel Kahn Gillmor <[email protected]> Description: dirmngr - GNU privacy guard - network certificate management service gnupg - GNU privacy guard - a free PGP replacement gnupg-agent - GNU privacy guard - cryptographic agent gnupg-l10n - GNU privacy guard - localization files gnupg2 - GNU privacy guard - a free PGP replacement (dummy transitional pa gpgsm - GNU privacy guard - S/MIME version gpgv - GNU privacy guard - signature verification tool gpgv-static - minimal signature verification tool (static build) gpgv-udeb - minimal signature verification tool (udeb) gpgv-win32 - GNU privacy guard - signature verification tool (win32 build) gpgv2 - GNU privacy guard - signature verification tool (dummy transition scdaemon - GNU privacy guard - smart card support Closes: 858400 Changes: gnupg2 (2.1.20-3) experimental; urgency=medium . * more upstream bugfixes (Closes: #858400) Checksums-Sha1: f87da35a63d9e0810e6004a8060a073565bf1e2e 3115 gnupg2_2.1.20-3.dsc 47d221a6db6a38e3c37954fc5b3d85c92c44c13c 70397 gnupg2_2.1.20-3.debian.tar.bz2 9c4e71f4f0962cb9ff4624c90b24beb13ae3ff6c 16412 gnupg2_2.1.20-3_amd64.buildinfo Checksums-Sha256: a9c45831237ba7268b7ed68a87dc6d9651483b503b40f11deab1da0028bcadb6 3115 gnupg2_2.1.20-3.dsc 915a76f0762766141a0974643c14a0a536b2e881534a0bfb2a9d336f569ecf73 70397 gnupg2_2.1.20-3.debian.tar.bz2 dbd0330f3467e52b602b7a9569c3a300b82ac7bc3cdb73db97a4b915a6321717 16412 gnupg2_2.1.20-3_amd64.buildinfo Files: dc337846b8f43d9c85937b0395b179f1 3115 utils optional gnupg2_2.1.20-3.dsc 178675dd9b1cbbe3563ecf4ed1ec2069 70397 utils optional gnupg2_2.1.20-3.debian.tar.bz2 fe9effe29650cd41501c1ce46b23bf07 16412 utils optional gnupg2_2.1.20-3_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEOCdgUepHf6PklTkyFJitxsGSMjcFAljntBMACgkQFJitxsGS MjeikxAAjVPUq7pL+vQUuoT1avr8/gVlHGha/XKxotGAUPnRO6cp2v3b5MLCcYEI c8C5Poy11UPoOKb6yvsfgpYTZgVK8yPPPNkS/YBSzb+FzP5jbMlrC2UqEGtOFyK2 veubn9ly2mZ2alxgLrdJSUH5FuwSd/+KDmoDJ08Y/OM/kBX9fLKSUkdl2h1u3vZU Ku1f/fgDa+79RNLvtdEvXHTmh+YlucurJCmdGLNcCFim4bBHzVIJkFfPiimPOvs/ unEnqsDl6jJgj94LmHMFrgIKov8uBOVbRL/zsBqNRk4hMqb+cF7Ah7/wknXqEvOY R7Jb0L6iaZcuN2P93KdORESaFSR2OzJ7pJ29aqn256jXFbj9grJQvRWHwk4eY490 jxljVQQX5naEeb4V+fBCpC3RV5tcyOkUWv7VnaANu6jKXXgMTQSuTxU+KkkA36yD CW1TAw88mictHoHOYeeMJW+7Uqnlx6ZUaMlL1h5Jtm+DdSMugLfroKC19Mr+p1R+ KFrgC/eAeO7T0hQm1OwQ/yB+eXVtZ7F2dmIN+CeMToMsJb8lEoLvb+C33hvyOR3P l3iTmoadPW7r9EXetaG6PfYH4ymIQfvBpMbTqpqiOM5fBZ7MvDjQCKSOqkOwEbt8 JL46l5joJRN5Zb78IhoQuJVyh7CMbLN7EM63BHg8X2sdho6RIhw= =UrOj -----END PGP SIGNATURE-----
--- End Message ---
