This bug was fixed in the package linux-aws - 5.3.0-1003.3
---------------
linux-aws (5.3.0-1003.3) eoan; urgency=medium
* eoan/linux-aws: 5.3.0-1003.3 -proposed tracker (LP: #1847291)
[ Ubuntu: 5.3.0-18.19 ]
* eoan/linux: 5.3.0-18.19 -proposed tracker (LP: #1847298)
* Enable the Dragonboards out of Eoan/master arm64 kernel (LP: #1846704)
- [Packaging] arm64: snapdragon: introduce a snapdragon flavour
- [Packaging] arm64: snapdragon: switch kernel format to Image
- [Config] arm64: snapdragon: CONFIG_PINCTRL_MSM8916=y
- [Config] arm64: snapdragon: CONFIG_PINCTRL_MSM8994=y
- [Config] arm64: snapdragon: CONFIG_PINCTRL_MSM8996=y
- [Config] arm64: snapdragon: CONFIG_PINCTRL_MSM8998=y
- [Config] arm64: snapdragon: CONFIG_REGULATOR_QCOM_RPMH=y
- [Config] arm64: snapdragon: CONFIG_QCOM_BAM_DMA=y
- [Config] arm64: snapdragon: CONFIG_QCOM_HIDMA_MGMT=y
- [Config] arm64: snapdragon: CONFIG_QCOM_HIDMA=y
- [Config] arm64: snapdragon: CONFIG_COMMON_CLK_QCOM=y
- [Config] arm64: snapdragon: CONFIG_QCOM_CLK_RPMH=y
- [Config] arm64: snapdragon: CONFIG_MSM_GCC_8916=y
- [Config] arm64: snapdragon: CONFIG_MSM_GCC_8994=y
- [Config] arm64: snapdragon: CONFIG_MSM_MMCC_8996=y
- [Config] arm64: snapdragon: CONFIG_MSM_GCC_8998=y
- [Config] arm64: snapdragon: CONFIG_HWSPINLOCK_QCOM=y
- [Config] arm64: snapdragon: CONFIG_QCOM_APCS_IPC=y
- [Config] arm64: snapdragon: CONFIG_RPMSG_QCOM_GLINK_RPM=y
- [Config] arm64: snapdragon: CONFIG_QCOM_GENI_SE=y
- [Config] arm64: snapdragon: CONFIG_QCOM_SMEM=y
- [Config] arm64: snapdragon: CONFIG_QCOM_SMD_RPM=y
- [Config] arm64: snapdragon: CONFIG_QCOM_SMP2P=y
- [Config] arm64: snapdragon: CONFIG_QCOM_SMSM=y
- [Config] arm64: snapdragon: CONFIG_QCOM_QFPROM=y
- [Config] arm64: snapdragon: CONFIG_SERIAL_QCOM_GENI=y
- [Config] arm64: snapdragon: CONFIG_QCOM_TSENS=y
- [Config] arm64: snapdragon: CONFIG_REGULATOR_QCOM_SMD_RPM=y
- [Config] arm64: snapdragon: CONFIG_QCOM_CLK_SMD_RPM=y
- [Config] arm64: snapdragon: CONFIG_RPMSG_QCOM_SMD=y
- [Config] arm64: snapdragon: CONFIG_MFD_QCOM_RPM=y
- [Config] arm64: snapdragon: CONFIG_SCSI_UFSHCD=y
- [Config] arm64: snapdragon: CONFIG_SCSI_UFSHCD_PLATFORM=y
- [Config] arm64: snapdragon: CONFIG_SCSI_UFS_HISI=y
- [Config] arm64: snapdragon: CONFIG_MMC_SDHCI=y
- [Config] arm64: snapdragon: CONFIG_MMC_SDHCI_PLTFM=y
- [Config] arm64: snapdragon: CONFIG_MMC_SDHCI_MSM=y
- [Config] arm64: snapdragon: CONFIG_REGULATOR_QCOM_SPMI=y
- [Config] arm64: snapdragon: CONFIG_PINCTRL_QCOM_SPMI_PMIC=y
- [Config] arm64: snapdragon: CONFIG_PHY_QCOM_USB_HS=y
- [Config] arm64: snapdragon: CONFIG_PHY_QCOM_QMP=y
- [Config] arm64: snapdragon: CONFIG_PHY_QCOM_UFS=y
- [Config] arm64: snapdragon: CONFIG_PHY_QCOM_USB_HSIC=y
- [Config] arm64: snapdragon: CONFIG_USB_CHIPIDEA_OF=y
- [Config] arm64: snapdragon: CONFIG_USB_EHCI_HCD_PLATFORM=y
- [Config] arm64: snapdragon: CONFIG_EXTCON_USB_GPIO=y
- [Config] arm64: snapdragon: CONFIG_REGULATOR_FIXED_VOLTAGE=y
- [Config] arm64: snapdragon: CONFIG_LEDS_GPIO=y
- [Config] arm64: snapdragon: CONFIG_USB_HSIC_USB3503=y
- [Config] arm64: snapdragon: CONFIG_USB_NET_DRIVERS=y
- [Config] arm64: snapdragon: CONFIG_USB_OTG=y
- [Config] arm64: snapdragon: CONFIG_USB_XHCI_PLATFORM=y
- [Config] arm64: snapdragon: CONFIG_USB_OHCI_HCD_PLATFORM=y
- [Config] arm64: snapdragon: CONFIG_USB_MUSB_HDRC=y
- [Config] arm64: snapdragon: CONFIG_USB_DWC3=y
- [Config] arm64: snapdragon: CONFIG_USB_DWC3_PCI=y
- [Config] arm64: snapdragon: CONFIG_USB_DWC3_OF_SIMPLE=y
- [Config] arm64: snapdragon: CONFIG_USB_DWC3_QCOM=y
- [Config] arm64: snapdragon: CONFIG_LEDS_PWM=y
- [Config] arm64: snapdragon: CONFIG_LEDS_TRIGGER_HEARTBEAT=y
- [Config] arm64: snapdragon: CONFIG_LEDS_TRIGGER_DEFAULT_ON=y
- [Config] arm64: snapdragon: CONFIG_QCOM_A53PLL=y
- [Config] arm64: snapdragon: CONFIG_QCOM_CLK_APCS_MSM8916=y
- [Config] arm64: snapdragon: CONFIG_NLS_ISO8859_1=y
- [Config] arm64: snapdragon: CONFIG_USB_USBNET=y
- [Config] arm64: snapdragon: CONFIG_CRYPTO_DEV_QCOM_RNG=y
- [Config] arm64: snapdragon: CONFIG_POWER_RESET_QCOM_PON=y
- [Config] arm64: snapdragon: CONFIG_INPUT_PM8941_PWRKEY=y
- [Config] arm64: snapdragon: CONFIG_KEYBOARD_GPIO=y
- [Config] arm64: snapdragon: CONFIG_RTC_DRV_PM8XXX=y
[ Ubuntu: 5.3.0-17.18 ]
* eoan/linux: 5.3.0-17.18 -proposed tracker (LP: #1846641)
* CVE-2019-17056
- nfc: enforce CAP_NET_RAW for raw sockets
* CVE-2019-17055
- mISDN: enforce CAP_NET_RAW for raw sockets
* CVE-2019-17054
- appletalk: enforce CAP_NET_RAW for raw sockets
* CVE-2019-17053
- ieee802154: enforce CAP_NET_RAW for raw sockets
* CVE-2019-17052
- ax25: enforce CAP_NET_RAW for raw sockets
* CVE-2019-15098
- ath6kl: fix a NULL-ptr-deref bug in ath6kl_usb_alloc_urb_from_pipe()
* xHCI on AMD Stoney Ridge cannot detect USB 2.0 or 1.1 devices.
(LP: #1846470)
- x86/PCI: Avoid AMD FCH XHCI USB PME# from D0 defect
* Re-enable linux-libc-dev build on i386 (LP: #1846508)
- [Packaging] Build only linux-libc-dev for i386
- [Debian] final-checks -- ignore archtictures with no binaries
* arm64: loop on boot after installing linux-generic-hwe-18.04-edge/bionic-
proposed (LP: #1845820)
- [Config] Disable CONFIG_ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT
* Revert ESE DASD discard support (LP: #1846219)
- SAUCE: Revert "s390/dasd: Add discard support for ESE volumes"
* Miscellaneous Ubuntu changes
- update dkms package versions
[ Ubuntu: 5.3.0-16.17 ]
* eoan/linux: 5.3.0-16.17 -proposed tracker (LP: #1846204)
* zfs fails to build on s390x with debug symbols enabled (LP: #1846143)
- SAUCE: s390: Mark atomic const ops always inline
-- Andrea Righi <andrea.ri...@canonical.com> Wed, 09 Oct 2019 16:29:08
+0200
** Changed in: linux-aws (Ubuntu)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-15098
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-17052
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-17053
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-17054
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-17055
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-17056
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1761379
Title:
[18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common
deb on Ubuntu
Status in The Ubuntu-power-systems project:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-aws package in Ubuntu:
Fix Released
Status in linux-aws-edge package in Ubuntu:
Fix Committed
Status in linux-aws-hwe package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
Invalid
Status in linux-aws source package in Xenial:
Invalid
Status in linux-aws-edge source package in Xenial:
Invalid
Status in linux-aws-hwe source package in Xenial:
Fix Released
Status in linux source package in Artful:
Won't Fix
Status in linux-aws source package in Artful:
Invalid
Status in linux-aws-edge source package in Artful:
Invalid
Status in linux-aws-hwe source package in Artful:
Invalid
Status in linux source package in Bionic:
Fix Released
Status in linux-aws source package in Bionic:
Fix Released
Status in linux-aws-edge source package in Bionic:
Fix Released
Status in linux-aws-hwe source package in Bionic:
Invalid
Status in linux source package in Cosmic:
Invalid
Status in linux-aws source package in Cosmic:
Invalid
Status in linux-aws-edge source package in Cosmic:
Invalid
Status in linux-aws-hwe source package in Cosmic:
Invalid
Status in linux source package in Disco:
Fix Released
Status in linux-aws source package in Disco:
Fix Released
Status in linux-aws-edge source package in Disco:
Invalid
Status in linux-aws-hwe source package in Disco:
Invalid
Bug description:
[Impact]
File libperf-jvmti.so is missing in linux-tools-common deb making it
impossible to use perf for the JVM JITed methods.
[Test case]
$ sudo perf record -k 1 -e instructions:u ./java
-agentpath:/usr/lib/linux-tools-5.0.0-8/libperf-jvmti.so crc32
$ sudo perf inject -i ./perf.data -j -o ./perf.data.jitted
$ sudo perf report -f -i ./perf.data.jitted
[Fix]
Include java build dependencies and install the library into linux-tools
package.
[Regression potential]
Small regression potential, an extra file is distributed and is not
automatically linked to anything. It could impact the build, which was tested.
---Problem Description---
File libperf-jvmti.so is missing in linux-tools-common deb making it
impossible to use perf for the JVM JITed methods
---uname output---
linux-image-4.13.0-36-generic
Machine Type = not relevant
---Debugger---
A debugger is not configured
---Steps to Reproduce---
File libperf-jvmti.so is missing in linux-tools-common deb provided for
Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also
checked if the file is available on launchpad
(https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main)
at it's also absent there:
gromero@ltc-wspoon3:~/download$ dpkg -c
linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm
gromero@ltc-wspoon3:~/download$ dpkg -c
linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm
I do see the file in tools/perf/jvmti dir in the source .tar.gz, but
apparently it's no being packaged in any .deb file?
Thanks.
Userspace tool common name: perf
The userspace tool has the following bit modes: 64-bit
Userspace tool obtained from project website: na
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+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
