[Kernel-packages] [Bug 1548414] Re: Floating-point exception handler receives empty Data-Exception Code in Floating Point Control register
This bug was fixed in the package linux - 4.4.0-9.24 --- linux (4.4.0-9.24) xenial; urgency=low [ Tim Gardner ] * Release Tracking Bug - LP: #1551319 * AppArmor logs denial for when the device path is ENOENT (LP: #1482943) - SAUCE: apparmor: fix log of apparmor audit message when kern_path() fails * BUG: unable to handle kernel NULL pointer dereference (aa_label_merge) (LP: #1448912) - SAUCE: apparmor: Fix: insert race between label_update and label_merge - SAUCE: apparmor: Fix: ensure aa_get_newest will trip debugging if the replacedby is not setup - SAUCE: apparmor: Fix: label merge handling of marking unconfined and stale - SAUCE: apparmor: Fix: refcount race between locating in labelset and get - SAUCE: apparmor: Fix: ensure new labels resulting from merge have a replacedby - SAUCE: apparmor: Fix: label_vec_merge insertion - SAUCE: apparmor: Fix: deadlock in aa_put_label() call chain - SAUCE: apparmor: Fix: add required locking of __aa_update_replacedby on merge path - SAUCE: apparmor: Fix: convert replacedby update to be protected by the labelset lock - SAUCE: apparmor: Fix: update replacedby allocation to take a gfp parameter * apparmor kernel BUG kills firefox (LP: #1430546) - SAUCE: apparmor: Disallow update of cred when then subjective != the objective cred - SAUCE: apparmor: rework retrieval of the current label in the profile update case * sleep from invalid context in aa_move_mount (LP: #1539349) - SAUCE: apparmor: fix sleep from invalid context * s390x: correct restore of high gprs on signal return (LP: #1550468) - s390/compat: correct restore of high gprs on signal return * missing SMAP support (LP: #1550517) - x86/entry/compat: Add missing CLAC to entry_INT80_32 * Floating-point exception handler receives empty Data-Exception Code in Floating Point Control register (LP: #1548414) - s390/fpu: signals vs. floating point control register * kvm fails to boot GNU Hurd kernels with 4.4 Xenial kernel (LP: #1550596) - KVM: x86: fix conversion of addresses to linear in 32-bit protected mode * Surelock GA2 SP1: capiredp01: cxl_init_adapter fails for CAPI devices :01:00.0 and 0005:01:00.0 after upgrading to 840.10 Platform firmware build fips840/b1208b_1604.840 (LP: #1532914) - cxl: Fix PSL timebase synchronization detection * [Feature]EDAC support for Knights Landing (LP: #1519631) - EDAC, sb_edac: Set fixed DIMM width on Xeon Knights Landing * Various failures of kernel_security suite on Xenial kernel on s390x arch (LP: #1531327) - [config] s390x -- CONFIG_DEFAULT_MMAP_MIN_ADDR=65536 * Unable to install VirtualBox Guest Service in 15.04 (LP: #1434579) - [Config] Provides: virtualbox-guest-modules when appropriate * linux is missing provides for virtualbox-guest-modules [i386 amd64 x32] (LP: #1507588) - [Config] Provides: virtualbox-guest-modules when appropriate * Backport more recent driver for SKL, KBL and BXT graphics (LP: #1540390) - SAUCE: i915_bpo: Provide a backport driver for SKL, KBL & BXT graphics - SAUCE: i915_bpo: Update intel_ips.h file location - SAUCE: i915_bpo: Rename the backport driver to i915_bpo - SAUCE: i915_bpo: Add i915_bpo_*() calls for ubuntu/i915 - drm/i915: remove an extra level of indirection in PCI ID list - drm/i915/kbl: Add Kabylake PCI ID - drm/i915/kbl: Add Kabylake GT4 PCI ID - mm: Export nr_swap_pages - async: export current_is_async() - drm: fix potential dangling else problems in for_each_ macros - dp/mst: add SDP stream support - drm: Implement drm_modeset_lock_all_ctx() - drm: Add "prefix" parameter to drm_rect_debug_print() - drm/i915: Set connector_state->connector using the helper. - drm/atomic: add connector mask to drm_crtc_state. - drm/i915: Report context GTT size - drm/i915: Add get_eld audio component - SAUCE: Backport I915_PARAM_HAS_EXEC_SOFTPIN and EXEC_OBJECT_PINNED - SAUCE: i915_bpo: Revert passing plane/encoder name - SAUCE: sound/hda: Load i915_bpo from the hda driver on SKL/KBL/BXT - SAUCE: i915_bpo: Support only SKL, KBL and BXT with the backport driver - drm/i915/bxt: update list of PCIIDs - drm/i915/skl: Add missing SKL ids - SAUCE: i915_bpo: Revert "drm/i915: Defer probe if gmux is present but its driver isn't" - SAUCE: uapi/drm/i915: Backport I915_EXEC_BSD_MASK - drm/atomic: Do not unset crtc when an encoder is stolen - drm/i915: Update connector_mask during readout, v2. - drm/atomic: Add encoder_mask to crtc_state, v3. - SAUCE: drm/core: Add drm_encoder_index. - SAUCE: i915_bpo: Revert "drm/i915: Switch DDC when reading the EDID" - i915_bpo: [Config] Enable CONFIG_DRM_I915_BPO=m * arm64: guest hangs when ntpd is running (LP: #1549494) - hrtimer: Add support for CLOCK_MONOTONIC_RAW -
[Kernel-packages] [Bug 1548414] Re: Floating-point exception handler receives empty Data-Exception Code in Floating Point Control register
** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1548414 Title: Floating-point exception handler receives empty Data-Exception Code in Floating Point Control register Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: == Comment: #0 - Alexander Efremkin- 2016-02-17 12:18:14 == With a C program sets FPE handler and triggers an FPE exception, it expects that machine-dependent context data, which is passed to the handler, will contain sensible values. In this scenario, however, FPC register was zero and contained no DXC (Data-Exception Code) indication: #include #include #include void trapFunction() { asm volatile ("lhi %r1,0\n\t" "cit %r1,0,8\n\t"); } static void sigFPE_handler(int signal, siginfo_t *info, void *context) { ucontext_t *uc = context; mcontext_t mc = uc->uc_mcontext; fpregset_t fpregs = mc.fpregs; unsigned int fpc = fpregs.fpc; printf("received signal!\n"); printf("fpc: %08x\n", fpc ); } int main() { struct sigaction action; memset(, '\0', sizeof(action)); printf("registering signal handler\n"); action.sa_flags |= SA_SIGINFO; action.sa_sigaction = sigFPE_handler; if (sigaction(SIGFPE, , NULL)) printf("error calling sigaction\n"); printf("firing trap\n"); trapFunction(); return 0; } This program prints "fpc: ", but the expected output is "fpc: ff00".. The IBM Java team has encountered test failures around the use of trap instructions; Linux on z Distribution Test reproduced the issue on the following system: z13 LPAR Ubuntu 16.04 Kernel 4.4.0-4-generic gcc (Ubuntu 5.3.1-8ubuntu2) 5.3.1 20160205 libc6 2.21-0ubuntu5 Also, similar issue has been found during test of SIMD (vector) instructions, FPC contents was also zero, whereas it expected at least an exception mask and vector-defined DXC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1548414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1548414] Re: Floating-point exception handler receives empty Data-Exception Code in Floating Point Control register
New kernel upload has entered xenial-proposed, and is being tested before migrating to release component For full changelog see: https://launchpad.net/ubuntu/+source/linux/4.4.0-9.24 Kernel release process workflow bug for this kernel is at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551319 To see progress of this kernel being released to xenial release component. Highlights from the changelog: * s390x: correct restore of high gprs on signal return (LP: #1550468) - s390/compat: correct restore of high gprs on signal return * Floating-point exception handler receives empty Data-Exception Code in Floating Point Control register (LP: #1548414) - s390/fpu: signals vs. floating point control register * Various failures of kernel_security suite on Xenial kernel on s390x arch (LP: #1531327) - [config] s390x -- CONFIG_DEFAULT_MMAP_MIN_ADDR=65536 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1548414 Title: Floating-point exception handler receives empty Data-Exception Code in Floating Point Control register Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: == Comment: #0 - Alexander Efremkin- 2016-02-17 12:18:14 == With a C program sets FPE handler and triggers an FPE exception, it expects that machine-dependent context data, which is passed to the handler, will contain sensible values. In this scenario, however, FPC register was zero and contained no DXC (Data-Exception Code) indication: #include #include #include void trapFunction() { asm volatile ("lhi %r1,0\n\t" "cit %r1,0,8\n\t"); } static void sigFPE_handler(int signal, siginfo_t *info, void *context) { ucontext_t *uc = context; mcontext_t mc = uc->uc_mcontext; fpregset_t fpregs = mc.fpregs; unsigned int fpc = fpregs.fpc; printf("received signal!\n"); printf("fpc: %08x\n", fpc ); } int main() { struct sigaction action; memset(, '\0', sizeof(action)); printf("registering signal handler\n"); action.sa_flags |= SA_SIGINFO; action.sa_sigaction = sigFPE_handler; if (sigaction(SIGFPE, , NULL)) printf("error calling sigaction\n"); printf("firing trap\n"); trapFunction(); return 0; } This program prints "fpc: ", but the expected output is "fpc: ff00".. The IBM Java team has encountered test failures around the use of trap instructions; Linux on z Distribution Test reproduced the issue on the following system: z13 LPAR Ubuntu 16.04 Kernel 4.4.0-4-generic gcc (Ubuntu 5.3.1-8ubuntu2) 5.3.1 20160205 libc6 2.21-0ubuntu5 Also, similar issue has been found during test of SIMD (vector) instructions, FPC contents was also zero, whereas it expected at least an exception mask and vector-defined DXC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1548414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1548414] Re: Floating-point exception handler receives empty Data-Exception Code in Floating Point Control register
Cherry-picked 1b17cb796f5d40ffa239c6926385abd83a77a49b s390/fpu: signals vs. floating point control register ** Also affects: linux (Ubuntu Xenial) Importance: High Assignee: Andy Whitcroft (apw) Status: Triaged ** Changed in: linux (Ubuntu Xenial) Status: Triaged => Fix Committed ** Changed in: linux (Ubuntu Xenial) Assignee: Andy Whitcroft (apw) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1548414 Title: Floating-point exception handler receives empty Data-Exception Code in Floating Point Control register Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: == Comment: #0 - Alexander Efremkin- 2016-02-17 12:18:14 == With a C program sets FPE handler and triggers an FPE exception, it expects that machine-dependent context data, which is passed to the handler, will contain sensible values. In this scenario, however, FPC register was zero and contained no DXC (Data-Exception Code) indication: #include #include #include void trapFunction() { asm volatile ("lhi %r1,0\n\t" "cit %r1,0,8\n\t"); } static void sigFPE_handler(int signal, siginfo_t *info, void *context) { ucontext_t *uc = context; mcontext_t mc = uc->uc_mcontext; fpregset_t fpregs = mc.fpregs; unsigned int fpc = fpregs.fpc; printf("received signal!\n"); printf("fpc: %08x\n", fpc ); } int main() { struct sigaction action; memset(, '\0', sizeof(action)); printf("registering signal handler\n"); action.sa_flags |= SA_SIGINFO; action.sa_sigaction = sigFPE_handler; if (sigaction(SIGFPE, , NULL)) printf("error calling sigaction\n"); printf("firing trap\n"); trapFunction(); return 0; } This program prints "fpc: ", but the expected output is "fpc: ff00".. The IBM Java team has encountered test failures around the use of trap instructions; Linux on z Distribution Test reproduced the issue on the following system: z13 LPAR Ubuntu 16.04 Kernel 4.4.0-4-generic gcc (Ubuntu 5.3.1-8ubuntu2) 5.3.1 20160205 libc6 2.21-0ubuntu5 Also, similar issue has been found during test of SIMD (vector) instructions, FPC contents was also zero, whereas it expected at least an exception mask and vector-defined DXC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1548414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1548414] Re: Floating-point exception handler receives empty Data-Exception Code in Floating Point Control register
>From IBM: This is kernel problem in the signal handling. An upstream kernel patch has been made and is currently on the s390 maintainers git tree on the fixes branch: "s390/fpu: signals vs. floating point control register" http://git.kernel.org/cgit/linux/kernel/git/s390/linux.git/log/?h=fixes ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Andy Whitcroft (apw) ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1548414 Title: Floating-point exception handler receives empty Data-Exception Code in Floating Point Control register Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - Alexander Efremkin- 2016-02-17 12:18:14 == With a C program sets FPE handler and triggers an FPE exception, it expects that machine-dependent context data, which is passed to the handler, will contain sensible values. In this scenario, however, FPC register was zero and contained no DXC (Data-Exception Code) indication: #include #include #include void trapFunction() { asm volatile ("lhi %r1,0\n\t" "cit %r1,0,8\n\t"); } static void sigFPE_handler(int signal, siginfo_t *info, void *context) { ucontext_t *uc = context; mcontext_t mc = uc->uc_mcontext; fpregset_t fpregs = mc.fpregs; unsigned int fpc = fpregs.fpc; printf("received signal!\n"); printf("fpc: %08x\n", fpc ); } int main() { struct sigaction action; memset(, '\0', sizeof(action)); printf("registering signal handler\n"); action.sa_flags |= SA_SIGINFO; action.sa_sigaction = sigFPE_handler; if (sigaction(SIGFPE, , NULL)) printf("error calling sigaction\n"); printf("firing trap\n"); trapFunction(); return 0; } This program prints "fpc: ", but the expected output is "fpc: ff00".. The IBM Java team has encountered test failures around the use of trap instructions; Linux on z Distribution Test reproduced the issue on the following system: z13 LPAR Ubuntu 16.04 Kernel 4.4.0-4-generic gcc (Ubuntu 5.3.1-8ubuntu2) 5.3.1 20160205 libc6 2.21-0ubuntu5 Also, similar issue has been found during test of SIMD (vector) instructions, FPC contents was also zero, whereas it expected at least an exception mask and vector-defined DXC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1548414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1548414] Re: Floating-point exception handler receives empty Data-Exception Code in Floating Point Control register
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1548414 Title: Floating-point exception handler receives empty Data-Exception Code in Floating Point Control register Status in linux package in Ubuntu: Incomplete Bug description: == Comment: #0 - Alexander Efremkin- 2016-02-17 12:18:14 == With a C program sets FPE handler and triggers an FPE exception, it expects that machine-dependent context data, which is passed to the handler, will contain sensible values. In this scenario, however, FPC register was zero and contained no DXC (Data-Exception Code) indication: #include #include #include void trapFunction() { asm volatile ("lhi %r1,0\n\t" "cit %r1,0,8\n\t"); } static void sigFPE_handler(int signal, siginfo_t *info, void *context) { ucontext_t *uc = context; mcontext_t mc = uc->uc_mcontext; fpregset_t fpregs = mc.fpregs; unsigned int fpc = fpregs.fpc; printf("received signal!\n"); printf("fpc: %08x\n", fpc ); } int main() { struct sigaction action; memset(, '\0', sizeof(action)); printf("registering signal handler\n"); action.sa_flags |= SA_SIGINFO; action.sa_sigaction = sigFPE_handler; if (sigaction(SIGFPE, , NULL)) printf("error calling sigaction\n"); printf("firing trap\n"); trapFunction(); return 0; } This program prints "fpc: ", but the expected output is "fpc: ff00".. The IBM Java team has encountered test failures around the use of trap instructions; Linux on z Distribution Test reproduced the issue on the following system: z13 LPAR Ubuntu 16.04 Kernel 4.4.0-4-generic gcc (Ubuntu 5.3.1-8ubuntu2) 5.3.1 20160205 libc6 2.21-0ubuntu5 Also, similar issue has been found during test of SIMD (vector) instructions, FPC contents was also zero, whereas it expected at least an exception mask and vector-defined DXC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1548414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp