[Bug 1866211] [NEW] [UBUNTU 20.04] valgrind: Recognize z15 and disable deflate-conversion facility bit

[bugproxy]

Public bug reported:

Trying to deflate using zlib under valgrind on z15 causes an
"unrecognised instruction" crash:

vex s390->IR: unknown insn: B939 A024
==42593== valgrind: Unrecognised instruction at address 0x4acec80.
==42593==    at 0x4ACEC80: ??? (in /usr/lib64/libz.so.1.2.11)
==42593==    by 0x4AC105B: deflateResetKeep (in /usr/lib64/libz.so.1.2.11)

In fact, the unrecognised instruction is the "deflate conversion call",
which is not supported by Valgrind yet.  Thus Valgrind should have
masked off the respective facility bit, but it didn't.

Upstream commit 3a2711c659ac839934f13e0529e14d6c15325383 fixes this.  It
will be part of the next Valgrind release 3.16.0.

** Affects: valgrind (Ubuntu)
     Importance: Undecided
     Assignee: Skipper Bug Screeners (skipper-screen-team)
         Status: New


** Tags: architecture-s39064 bugnameltc-184223 severity-high targetmilestone-inin2004

** Tags added: architecture-s39064 bugnameltc-184223 severity-high
targetmilestone-inin2004

** Changed in: ubuntu
     Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

** Package changed: ubuntu => valgrind (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to valgrind in Ubuntu.
https://bugs.launchpad.net/bugs/1866211

Title:
  [UBUNTU 20.04] valgrind: Recognize z15 and disable deflate-conversion
  facility bit

Status in valgrind package in Ubuntu:
  New

Bug description:
  Trying to deflate using zlib under valgrind on z15 causes an
  "unrecognised instruction" crash:

  vex s390->IR: unknown insn: B939 A024
  ==42593== valgrind: Unrecognised instruction at address 0x4acec80.
  ==42593==    at 0x4ACEC80: ??? (in /usr/lib64/libz.so.1.2.11)
  ==42593==    by 0x4AC105B: deflateResetKeep (in /usr/lib64/libz.so.1.2.11)

  In fact, the unrecognised instruction is the "deflate conversion
  call", which is not supported by Valgrind yet.  Thus Valgrind should
  have masked off the respective facility bit, but it didn't.

  Upstream commit 3a2711c659ac839934f13e0529e14d6c15325383 fixes this.
  It will be part of the next Valgrind release 3.16.0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1866211/+subscriptions