linux_4.9.168-1+deb9u2_multi.changes ACCEPTED into proposed-updates->stable-new
Mapping stable-security to proposed-updates. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 13 May 2019 21:59:18 +0100 Binary: linux-doc-4.9 linux-headers-4.9.0-9-common linux-headers-4.9.0-9-common-rt linux-manual-4.9 linux-source-4.9 linux-support-4.9.0-9 Source: linux Architecture: all source Version: 4.9.168-1+deb9u2 Distribution: stretch-security Urgency: high Maintainer: Debian Kernel Team Changed-By: Ben Hutchings Closes: 928125 Description: linux-doc-4.9 - Linux kernel specific documentation for version 4.9 linux-headers-4.9.0-9-common - Common header files for Linux 4.9.0-9 linux-headers-4.9.0-9-common-rt - Common header files for Linux 4.9.0-9-rt linux-manual-4.9 - Linux kernel API manual pages for version 4.9 linux-source-4.9 - Linux kernel source for version 4.9 with Debian patches linux-support-4.9.0-9 - Support files for Linux 4.9 Changes: linux (4.9.168-1+deb9u2) stretch-security; urgency=high . [ Salvatore Bonaccorso ] * Revert "block/loop: Use global lock for ioctl() operation." (Closes: #928125) . linux (4.9.168-1+deb9u1) stretch-security; urgency=high . * [x86] Update speculation mitigations: - x86/MCE: Save microcode revision in machine check records - x86/cpufeatures: Hide AMD-specific speculation flags - x86/bugs: Add AMD's variant of SSB_NO - x86/bugs: Add AMD's SPEC_CTRL MSR usage - x86/bugs: Switch the selection of mitigation from CPU vendor to CPU features - x86/bugs: Fix the AMD SSBD usage of the SPEC_CTRL MSR - x86/microcode/intel: Add a helper which gives the microcode revision - x86/microcode/intel: Check microcode revision before updating sibling threads - x86/microcode: Make sure boot_cpu_data.microcode is up-to-date - x86/microcode: Update the new microcode revision unconditionally - x86/mm: Use WRITE_ONCE() when setting PTEs - bitops: avoid integer overflow in GENMASK(_ULL) - x86/speculation: Simplify the CPU bug detection logic - locking/atomics, asm-generic: Move some macros from to a new file - x86/speculation: Remove SPECTRE_V2_IBRS in enum spectre_v2_mitigation - x86/cpu: Sanitize FAM6_ATOM naming - Documentation/l1tf: Fix small spelling typo - x86/speculation: Apply IBPB more strictly to avoid cross-process data leak - x86/speculation: Enable cross-hyperthread spectre v2 STIBP mitigation - x86/speculation: Propagate information about RSB filling mitigation to sysfs - x86/speculation/l1tf: Drop the swap storage limit restriction when l1tf=off - x86/speculation: Update the TIF_SSBD comment - x86/speculation: Clean up spectre_v2_parse_cmdline() - x86/speculation: Remove unnecessary ret variable in cpu_show_common() - x86/speculation: Move STIPB/IBPB string conditionals out of cpu_show_common() - x86/speculation: Disable STIBP when enhanced IBRS is in use - x86/speculation: Rename SSBD update functions - x86/speculation: Reorganize speculation control MSRs update - x86/Kconfig: Select SCHED_SMT if SMP enabled - sched: Add sched_smt_active() - x86/speculation: Rework SMT state change - x86/l1tf: Show actual SMT state - x86/speculation: Reorder the spec_v2 code - x86/speculation: Mark string arrays const correctly - x86/speculataion: Mark command line parser data __initdata - x86/speculation: Unify conditional spectre v2 print functions - x86/speculation: Add command line control for indirect branch speculation - x86/speculation: Prepare for per task indirect branch speculation control - x86/process: Consolidate and simplify switch_to_xtra() code - x86/speculation: Avoid __switch_to_xtra() calls - x86/speculation: Prepare for conditional IBPB in switch_mm() - x86/speculation: Split out TIF update - x86/speculation: Prepare arch_smt_update() for PRCTL mode - x86/speculation: Prevent stale SPEC_CTRL msr content - x86/speculation: Add prctl() control for indirect branch speculation - x86/speculation: Enable prctl mode for spectre_v2_user - x86/speculation: Add seccomp Spectre v2 user space protection mode - x86/speculation: Provide IBPB always command line options - kvm: x86: Report STIBP on GET_SUPPORTED_CPUID - x86/msr-index: Cleanup bit defines - x86/speculation: Consolidate CPU whitelists - Documentation: Move L1TF to separate directory - cpu/speculation: Add 'mitigations=' cmdline option - x86/speculation: Support 'mitigations=' cmdline option - x86/speculation/mds: Add 'mitigations=' support for MDS - x86/cpu/bugs: Use __initconst for 'const' init data * [x86] Mitigate Microarchitectural Data Sampling (MDS) vulnerabilities (CVE-2018-12126, CVE-2018-12127, CVE-2018-12130, CVE-2019-11091): - x86/speculation/mds: Add basic bug infrastructure for MDS -
Processed: found 928989 in 4.9.168-1
Processing commands for cont...@bugs.debian.org:
> found 928989 4.9.168-1
Bug #928989 {Done: Salvatore Bonaccorso } [src:linux]
linux-image-4.19.0-4-amd64: CVE-2019-11815
Marked as found in versions linux/4.9.168-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
928989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928989
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
linux_4.19.37-2_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 14 May 2019 17:34:37 +0100 Source: linux Architecture: source Version: 4.19.37-2 Distribution: unstable Urgency: high Maintainer: Debian Kernel Team Changed-By: Ben Hutchings Closes: 928618 Changes: linux (4.19.37-2) unstable; urgency=high . * debian/bin: Fix Python static checker regressions (Closes: #928618) * Clean up speculation mitigations: - Documentation/l1tf: Fix small spelling typo - x86/cpu: Sanitize FAM6_ATOM naming - kvm: x86: Report STIBP on GET_SUPPORTED_CPUID - x86/msr-index: Cleanup bit defines - x86/speculation: Consolidate CPU whitelists - Documentation: Move L1TF to separate directory - cpu/speculation: Add 'mitigations=' cmdline option - x86/speculation: Support 'mitigations=' cmdline option - powerpc/speculation: Support 'mitigations=' cmdline option - s390/speculation: Support 'mitigations=' cmdline option - x86/speculation/mds: Add 'mitigations=' support for MDS * [x86] Mitigate Microarchitectural Data Sampling (MDS) vulnerabilities (CVE-2018-12126, CVE-2018-12127, CVE-2018-12130, CVE-2019-11091): - x86/speculation/mds: Add basic bug infrastructure for MDS - x86/speculation/mds: Add BUG_MSBDS_ONLY - x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests - x86/speculation/mds: Add mds_clear_cpu_buffers() - x86/speculation/mds: Clear CPU buffers on exit to user - x86/kvm/vmx: Add MDS protection when L1D Flush is not active - x86/speculation/mds: Conditionally clear CPU buffers on idle entry - x86/speculation/mds: Add mitigation control for MDS - x86/speculation/mds: Add sysfs reporting for MDS - x86/speculation/mds: Add mitigation mode VMWERV - Documentation: Add MDS vulnerability documentation - x86/speculation/mds: Add mds=full,nosmt cmdline option - x86/speculation: Move arch_smt_update() call to after mitigation decisions - x86/speculation/mds: Add SMT warning message - x86/speculation/mds: Fix comment - x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off - x86/mds: Add MDSUM variant to the MDS documentation - Documentation: Correct the possible MDS sysfs values - x86/speculation/mds: Fix documentation typo * [x86] linux-cpupower: Update CPPFLAGS for change in Checksums-Sha1: 0f3898fb50eaf82ebcccffcea79b6af3ac83e58d 189124 linux_4.19.37-2.dsc e5d28f26074b82ba27ef5bf3ec470f52fae36224 1231028 linux_4.19.37-2.debian.tar.xz 04d7e8722f9b410bc3d5b3f4b3b8ce9d5bb9745a 47334 linux_4.19.37-2_source.buildinfo Checksums-Sha256: fa5e2bb6ecbfd13b0db17ace1e2b0edc8f860ad0c6e1c6054635f8bb93adaa46 189124 linux_4.19.37-2.dsc 758572eb0b6eaf20097cd3046e1ab35dfc01643db4c32669c5816489408ad12f 1231028 linux_4.19.37-2.debian.tar.xz aa653914dfac9fedc580b6c5137525de46c53cb176a417d21971040554d7c07b 47334 linux_4.19.37-2_source.buildinfo Files: 1acdf564916a6db0c9136dce0938afbc 189124 kernel optional linux_4.19.37-2.dsc 2c2c39e74d5edbd524f445abec3afe96 1231028 kernel optional linux_4.19.37-2.debian.tar.xz 7b9b8b9a0ddb1afa1a18f073880a4ccd 47334 kernel optional linux_4.19.37-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAlzbCwoACgkQ57/I7JWG EQlJ3xAAvQgCCeyrcmW+NRRNq2u76aXDF9sJq2tIi6d1Pwh4yU3M2zAVq/O1IMoi RCinxFUvkrx00XOtA9h2DCdVwLltXxv+fcMD6odiwHo5nPBVoi0LkoiR8jNNwZmL sEP67Wc/ve2/HZq06NHhyK+/SHs5YdHizhsgw7eTN1PlUuXMIa9sIWtEAdSs/Yi0 uJ0SUmb7CVZwa6EQHz5iV1nLAqt5nI09kIulBLfCKtPlimrVTxiIxTvyDJzXcFEr e+Q32LH63pWula/bjVwp24pL3b9ceejDucqsoYwaY7NjDhZfk8jKQheacsHBpAKG HimB984q5DP3jzSmOQVZu+kWZ8kTGMSgcJhHSBzYrhYjmu4N3PQWxWOP5ymU+DCn hki+UpSkbt8ngChpkVS0gWcOnwRA+T3sH5j1XSjjXd3a8Lyy5BoP/B4EIyP5z47V sNtgVumh5TVt7ZSlKQbuMtFPkndbakS+7ZlEwjg2m8ly4frUk/U8WDclEFdXcBuu bv3rj/yB3rbMGtKia5LN6maA0CWMBjr9ATT36fWw0DzWu9mN6lBEzRaoJOroha17 wgy429F6yf2xzkufdzKSwS3den0S2F2nh5hrURyGivctckEHMw8tV/mXtyxxp9yS CqU42smMLB1/WMccmOs04XrArgOTzSgHL5K/3YIjFK4b/B33/AY= =H8IY -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processed: closing 928989
Processing commands for cont...@bugs.debian.org: > close 928989 4.19.37-1 Bug #928989 [src:linux] linux-image-4.19.0-4-amd64: CVE-2019-11815 Ignoring request to alter fixed versions of bug #928989 to the same values previously set Bug #928989 [src:linux] linux-image-4.19.0-4-amd64: CVE-2019-11815 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 928989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928989 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#928989: linux-image-4.19.0-4-amd64: CVE-2019-11815
Processing control commands: > fixed -1 4.19.37-1 Bug #928989 [src:linux] linux-image-4.19.0-4-amd64: CVE-2019-11815 Marked as fixed in versions linux/4.19.37-1. > found -1 4.9.168-2 Bug #928989 [src:linux] linux-image-4.19.0-4-amd64: CVE-2019-11815 The source 'linux' and version '4.9.168-2' do not appear to match any binary packages Marked as found in versions linux/4.9.168-2. > found -1 3.16.64-2 Bug #928989 [src:linux] linux-image-4.19.0-4-amd64: CVE-2019-11815 The source 'linux' and version '3.16.64-2' do not appear to match any binary packages Marked as found in versions linux/3.16.64-2. > severity -1 important Bug #928989 [src:linux] linux-image-4.19.0-4-amd64: CVE-2019-11815 Ignoring request to change severity of Bug 928989 to the same value. -- 928989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928989 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#928989: linux-image-4.19.0-4-amd64: CVE-2019-11815
Control: fixed -1 4.19.37-1 Control: found -1 4.9.168-2 Control: found -1 3.16.64-2 Control: severity -1 important On Tue, 2019-05-14 at 14:37 -0400, Jeff Cliff wrote: > Package: src:linux > Version: 4.19.28-2 > Severity: grave > Tags: security > Justification: user security hole > > Dear Maintainer, > > An issue was discovered in rds_tcp_kill_sock in net/rds/tcp.c in the > Linux kernel before 5.0.8. > There is a race condition leading to a use-after-free, related to net > namespace cleanup. > > the security-tracker is tracking this issue but there does not seem > to be a bug report for it > > https://security-tracker.debian.org/tracker/CVE-2019-11815 > > Fixed by: > https://git.kernel.org/linus/cb66ddd156203daefb8d71158036b27b0e2caf63 > > currently affects: buster/testing, stable > currently does not affect: sid [...] This was already mitigated in older suites, in that we disable auto- loading of the rds module. This is therefore only exploitable on systems that actually use rds. For that reason, I'm downgrading this to "important". Ben. -- Ben Hutchings I haven't lost my mind; it's backed up on tape somewhere. signature.asc Description: This is a digitally signed message part
Processing of linux_4.19.37-2_source.changes
linux_4.19.37-2_source.changes uploaded successfully to localhost along with the files: linux_4.19.37-2.dsc linux_4.19.37-2.debian.tar.xz linux_4.19.37-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#928618: marked as done (linux: autopkgtest regression)
Your message dated Tue, 14 May 2019 18:51:16 + with message-id and subject line Bug#928618: fixed in linux 4.19.37-2 has caused the Debian Bug report #928618, regarding linux: autopkgtest regression 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 ow...@bugs.debian.org immediately.) -- 928618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: linux Version: 4.19.37-1 X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: regression Dear maintainers, With a recent upload of linux the autopkgtest of linux fails in testing when that autopkgtest is run with the binary packages of linux from unstable. It passes when run with only packages from testing. In tabular form: passfail linux from testing4.19.37-1 versioned deps [0] from testingfrom unstable all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is a reason for blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] You can see what packages were added from the second line of the log file quoted below. The migration software adds source package from unstable to the list if they are needed to install packages from linux/4.19.37-1. I.e. due to versioned dependencies or breaks/conflicts. [1] https://qa.debian.org/excuses.php?package=linux https://ci.debian.net/data/autopkgtest/testing/amd64/l/linux/2340029/log.gz autopkgtest [03:11:55]: test python: [--- I: Running pycodestyle... debian/bin/gencontrol_signed.py:303:30: E131 continuation line unaligned for hanging indent debian/bin/gencontrol_signed.py:308:36: E202 whitespace before '}' E: pycodestyle detected problems I: Running pyflakes... debian/bin/abiupdate.py:139: local variable 'e' is assigned to but never used E: pyflakes detected problems I: Running debian_linux.debian unit tests... . -- Ran 21 tests in 0.002s OK autopkgtest [03:11:57]: test python: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: linux Source-Version: 4.19.37-2 We believe that the bug you reported is fixed in the latest version of linux, 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 928...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier of updated linux 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 14 May 2019 17:34:37 +0100 Source: linux Architecture: source Version: 4.19.37-2 Distribution: unstable Urgency: high Maintainer: Debian Kernel Team Changed-By: Ben Hutchings Closes: 928618 Changes: linux (4.19.37-2) unstable; urgency=high . * debian/bin: Fix Python static checker regressions (Closes: #928618) * Clean up speculation mitigations: - Documentation/l1tf: Fix small spelling typo - x86/cpu: Sanitize FAM6_ATOM naming - kvm: x86: Report STIBP on GET_SUPPORTED_CPUID - x86/msr-index: Cleanup bit defines - x86/speculation: Consolidate CPU whitelists - Documentation: Move L1TF to separate directory - cpu/speculation: Add 'mitigations=' cmdline option - x86/speculation: Support 'mitigations=' cmdline option - powerpc/speculation: Support 'mitigations=' cmdline option - s390/speculation: Support 'mitigations=' cmdline option - x86/speculation/mds: Add 'mitigations=' support for MDS * [x86] Mitigate Microarchitectural Data Sampling (MDS) vulnerabilities (CVE-2018-12126, CVE-2018-12127, CVE-2018-12130, CVE-2019-11091): - x86/speculation/mds: Add basic bug infrastructure for MDS - x86/speculation/mds: Add BUG_MSBDS_ONLY - x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests - x86/speculation/mds: Add
Processed: Re: linux-image-4.19.0-4-amd64: CVE-2019-11815
Processing commands for cont...@bugs.debian.org: > severity 928989 important Bug #928989 [src:linux] linux-image-4.19.0-4-amd64: CVE-2019-11815 Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 928989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928989 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#928989: linux-image-4.19.0-4-amd64: CVE-2019-11815
Package: src:linux Version: 4.19.28-2 Severity: grave Tags: security Justification: user security hole Dear Maintainer, An issue was discovered in rds_tcp_kill_sock in net/rds/tcp.c in the Linux kernel before 5.0.8. There is a race condition leading to a use-after-free, related to net namespace cleanup. the security-tracker is tracking this issue but there does not seem to be a bug report for it https://security-tracker.debian.org/tracker/CVE-2019-11815 Fixed by: https://git.kernel.org/linus/cb66ddd156203daefb8d71158036b27b0e2caf63 currently affects: buster/testing, stable currently does not affect: sid -- Package-specific info: ** Version: Linux version 4.19.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-2)) #1 SMP Debian 4.19.28-2 (2019-03-15) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-4-amd64 root=UUID=6fa86bad-c261-44db-8fc0-f7bd76dc2be3 ro quiet ** Not tainted ** Kernel log: Unable to read kernel log; any relevant messages should be attached -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-4.19.0-4-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.133 ii kmod26-1 ii linux-base 4.5 Versions of packages linux-image-4.19.0-4-amd64 recommends: ii apparmor 2.13.2-10 ii firmware-linux-free 3.4 ii irqbalance 1.5.0-3 Versions of packages linux-image-4.19.0-4-amd64 suggests: ii debian-kernel-handbook 1.0.19 ii grub-pc 2.02+dfsg1-16 pn linux-doc-4.19 Versions of packages linux-image-4.19.0-4-amd64 is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree pn firmware-misc-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- debconf-show failed
Processed: reassign 901389 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 901389 src:linux 4.19.37-1 Bug #901389 [src:linux] [firmware-iwlwifi] Crash when using as a hotspot with intense usage Ignoring request to reassign bug #901389 to the same package Bug #901389 [src:linux] [firmware-iwlwifi] Crash when using as a hotspot with intense usage No longer marked as found in versions linux/4.16.12-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 901389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901389 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#901389: [firmware-iwlwifi] Crash when using as a hotspot with intense usage
Package: src:linux Version: 4.19.37-1 Severity: important Dear Maintainer, I use another version of linux in my debian box,but I also have totally the same problem when I use my laptop as a hotspot. I attached crash log filename="crash.log" in this report. This problem is randomly and often happened. I think this problem is more often happend when windows10 pc access to this hotspot via wifi. I hope someone will fix this problem. Thank you in advance, -- Takahide Nojima -- Package-specific info: ** Version: Linux version 4.19.0-5-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-7)) #1 SMP Debian 4.19.37-1 (2019-05-05) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-5-amd64 root=UUID=f8dd9a0a-8954-4faa- afe8-ecda81deca67 ro quiet ** Not tainted ** Kernel log: [5.342873] Bluetooth: hci0: API lock is enabled [5.342873] Bluetooth: hci0: Debug lock is disabled [5.342875] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [5.355324] bluetooth hci0: firmware: direct-loading firmware intel/ibt-11-5.sfi [5.355328] Bluetooth: hci0: Found device firmware: intel/ibt-11- 5.sfi [5.355879] idma64 idma64.1: Found Intel integrated DMA 64-bit [5.368464] sr 0:0:0:0: Attached scsi generic sg0 type 5 [5.387753] Adding 1952764k swap on /dev/nvme0n1p5. Priority:-2 extents:1 across:1952764k SSFS [5.396268] intel_rapl: Found RAPL domain package [5.396270] intel_rapl: Found RAPL domain core [5.396270] intel_rapl: Found RAPL domain uncore [5.396271] intel_rapl: Found RAPL domain dram [5.410355] usbcore: registered new interface driver uvcvideo [5.410356] USB Video Class driver (1.1.1) [5.410916] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input19 [5.410968] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input20 [5.411321] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input21 [5.411593] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input22 [5.411639] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input23 [5.411680] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input24 [5.411722] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input25 [5.448734] iwlwifi :05:00.0: base HW address: 28:16:ad:e9:10:c9 [5.498155] pktcdvd: pktcdvd0: writer mapped to sr0 [5.506507] pktcdvd: pktcdvd0: pkt_get_last_written failed [5.528738] input: VAIO0002:00 04F3:3014 Touchpad as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c- VAIO0002:00/0018:04F3:3014.0001/input/input27 [5.528875] hid-multitouch 0018:04F3:3014.0001: input,hidraw0: I2C HID v1.00 Mouse [VAIO0002:00 04F3:3014] on i2c-VAIO0002:00 [5.550162] ieee80211 phy0: Selected rate control algorithm 'iwl- mvm-rs' [5.550408] thermal thermal_zone4: failed to read out thermal zone (-61) [5.552550] iwlwifi :05:00.0 wlp5s0: renamed from wlan0 [5.556225] audit: type=1400 audit(1557846641.909:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/unreal-*/System/*.bin" pid=568 comm="apparmor_parser" [5.559893] audit: type=1400 audit(1557846641.913:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/telepathy/mission-control-5" pid=567 comm="apparmor_parser" [5.559897] audit: type=1400 audit(1557846641.913:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/telepathy/telepathy-*" pid=567 comm="apparmor_parser" [5.559899] audit: type=1400 audit(1557846641.913:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/telepathy/telepathy-*//pxgsettings" pid=567 comm="apparmor_parser" [5.559900] audit: type=1400 audit(1557846641.913:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/telepathy/telepathy-*//sanitized_helper" pid=567 comm="apparmor_parser" [5.559902] audit: type=1400 audit(1557846641.913:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/telepathy/telepathy-ofono" pid=567 comm="apparmor_parser" [5.560973] audit: type=1400 audit(1557846641.913:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=574 comm="apparmor_parser" [5.560976] audit: type=1400 audit(1557846641.913:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=574 comm="apparmor_parser" [5.563849] audit: type=1400 audit(1557846641.917:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=575 comm="apparmor_parser" [5.563851] audit: type=1400 audit(1557846641.917:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=575 comm="apparmor_parser" [
Re: Bug#928924: user-mode-linux: xterm functionality broken due to wrong path to port-helper
On Tue, 2019-05-14 at 13:57 +0100, Ben Hutchings wrote: > Does user-mode-linux need to be a separate source package at all? I guess it is separate to not require building yet another variant. Looks like merging it was discussed in 2016: https://bugs.debian.org/837920 -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Re: Bug#928924: user-mode-linux: xterm functionality broken due to wrong path to port-helper
Control: notforwarded -1
On Tue, 2019-05-14 at 14:36 +0530, Ritesh Raj Sarraf wrote:
> I submitted this fix upstream to the kernel some time ago. I don't
> recollect if the 4.19 kernel is what had it included.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9ca19a3a3e2482916c475b90f3d7fa2a03d8e5ed
That patch is already applied in the Debian user-mode-linux package:
debian/patches/fix-port-helper-path.patch
I noticed that the path embedded in the binary has an extra slash in it
compared to what the patch changes it to so I think the problem is that
the OS_LIB_PATH variable isn't defined correctly on amd64.
There seems to be some sort of confusion about the CONFIG_64BIT var but
it seems like the paths and variables in the sources are correct so I'm
not sure what is going on.
BTW, is it possible to do source-only uploads so that the build logs
are available on amd64, or do the versioned binaries mean no logs? If
so I think it would be good to only upload i386 binary packages so that
we get the build logs for the most used architecture.
~/linux-4.19.37 $ grep -rC1 OS_LIB_PATH
arch/um/drivers/xterm.c-char *argv[] = { terminal_emulator,
title_switch, title, exec_switch,
arch/um/drivers/xterm.c: OS_LIB_PATH
"/uml/port-helper", "-uml-socket",
arch/um/drivers/xterm.c- file, NULL };
--
arch/um/include/shared/os.h-#ifdef CONFIG_64BIT
arch/um/include/shared/os.h:#define OS_LIB_PATH "/usr/lib64/"
arch/um/include/shared/os.h-#else
arch/um/include/shared/os.h:#define OS_LIB_PATH "/usr/lib/"
arch/um/include/shared/os.h-#endif
--
arch/um/os-Linux/main.c-
arch/um/os-Linux/main.c:#define UML_LIB_PATH":" OS_LIB_PATH "/uml"
arch/um/os-Linux/main.c-
~/user-mode-linux-4.19-1um $ grep -r CONFIG_64BIT
config.i386:# CONFIG_64BIT is not set
config.amd64:CONFIG_64BIT=y
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
Re: Bug#928924: user-mode-linux: xterm functionality broken due to wrong path to port-helper
On Tue, 2019-05-14 at 18:13 +0530, Ritesh Raj Sarraf wrote: > On Tue, 2019-05-14 at 10:45 +0100, Ben Hutchings wrote: > > > Irrespective, I think it is a fair candidate to be backported if > > 4.19 > > > missed that window. For User-Mode-Linux, The sources are the same > > that > > > the Debian Linux kernel team maintains. So either they could pick > > this > > > commit as a patch or else I'll try to look into it soon. > > [...] > > > > Can you please send this request to sta...@vger.kernel.org as well? > > Thanks for the suggestion Ben. > > The fix for this bug is now queued for the 4.19 stable tree. So soon, > this fix will show up in the Debian Linux kernel package too. That is > when we can trigger a rebuild of user-mode-linux package and then mark > this bug fixed. > > Debian Buster already has the dependency set correct to the 4.19 > kernel. Wishfully it would be much nicer if this whole process of the > build could be automated to trigger periodically, or trigger on every > upload of the linux-source package. Does user-mode-linux need to be a separate source package at all? It might be difficult to integrate it with the linux source package, as we currently assume a strict separation between kernel and userland binary packages, but it is probably possible to do. Something to consider for the bullseye release cycle. Ben. -- Ben Hutchings I haven't lost my mind; it's backed up on tape somewhere. signature.asc Description: This is a digitally signed message part
Re: Bug#928924: user-mode-linux: xterm functionality broken due to wrong path to port-helper
On Tue, 2019-05-14 at 10:45 +0100, Ben Hutchings wrote: > > Irrespective, I think it is a fair candidate to be backported if > 4.19 > > missed that window. For User-Mode-Linux, The sources are the same > that > > the Debian Linux kernel team maintains. So either they could pick > this > > commit as a patch or else I'll try to look into it soon. > [...] > > Can you please send this request to sta...@vger.kernel.org as well? Thanks for the suggestion Ben. The fix for this bug is now queued for the 4.19 stable tree. So soon, this fix will show up in the Debian Linux kernel package too. That is when we can trigger a rebuild of user-mode-linux package and then mark this bug fixed. Debian Buster already has the dependency set correct to the 4.19 kernel. Wishfully it would be much nicer if this whole process of the build could be automated to trigger periodically, or trigger on every upload of the linux-source package. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: This is a digitally signed message part
Re: [PATCH] um: Don't hardcode path as it is architecture dependent
On Tue, May 14, 2019 at 04:36:38PM +0530, Ritesh Raj Sarraf wrote: > Hello Greg, > > On Tue, 2019-05-14 at 12:26 +0200, Greg KH wrote: > > On Tue, May 14, 2019 at 03:46:57PM +0530, Ritesh Raj Sarraf wrote: > > > The current code fails to run on amd64 because of hardcoded > > > reference to > > > i386 > > > > > > Signed-off-by: Ritesh Raj Sarraf > > > Signed-off-by: Richard Weinberger > > > --- > > > arch/um/drivers/port_user.c | 2 +- > > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > What is the git commit id of this patch in Linus's tree? > > The git commit id should be: 9ca19a3a3e2482916c475b90f3d7fa2a03d8e5ed Thanks, now queued up. greg k-h
Re: [PATCH] um: Don't hardcode path as it is architecture dependent
Hello Greg, On Tue, 2019-05-14 at 12:26 +0200, Greg KH wrote: > On Tue, May 14, 2019 at 03:46:57PM +0530, Ritesh Raj Sarraf wrote: > > The current code fails to run on amd64 because of hardcoded > > reference to > > i386 > > > > Signed-off-by: Ritesh Raj Sarraf > > Signed-off-by: Richard Weinberger > > --- > > arch/um/drivers/port_user.c | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > What is the git commit id of this patch in Linus's tree? The git commit id should be: 9ca19a3a3e2482916c475b90f3d7fa2a03d8e5ed The web url is: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9ca19a3a3e2482916c475b90f3d7fa2a03d8e5ed -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: This is a digitally signed message part
Re: [PATCH] um: Don't hardcode path as it is architecture dependent
On Tue, May 14, 2019 at 03:46:57PM +0530, Ritesh Raj Sarraf wrote: > Dear Stable Team, > Request for inclusion into the stable branches of Linux. This change > went into 4.20 but 4.19 is the LTS release that many of the Linux > Vendors are rebasing on. Hence, it'd be nice to see this part of the LTS > releases, at least 4.19. > > > The current code fails to run on amd64 because of hardcoded reference to > i386 > > Signed-off-by: Ritesh Raj Sarraf > Signed-off-by: Richard Weinberger > --- > arch/um/drivers/port_user.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) What is the git commit id of this patch in Linus's tree? thanks, greg k-h
[PATCH] um: Don't hardcode path as it is architecture dependent
Dear Stable Team,
Request for inclusion into the stable branches of Linux. This change
went into 4.20 but 4.19 is the LTS release that many of the Linux
Vendors are rebasing on. Hence, it'd be nice to see this part of the LTS
releases, at least 4.19.
The current code fails to run on amd64 because of hardcoded reference to
i386
Signed-off-by: Ritesh Raj Sarraf
Signed-off-by: Richard Weinberger
---
arch/um/drivers/port_user.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/um/drivers/port_user.c b/arch/um/drivers/port_user.c
index 9a8e1b64c22e..5f56d11b886f 100644
--- a/arch/um/drivers/port_user.c
+++ b/arch/um/drivers/port_user.c
@@ -168,7 +168,7 @@ int port_connection(int fd, int *socket, int *pid_out)
{
int new, err;
char *argv[] = { "/usr/sbin/in.telnetd", "-L",
-"/usr/lib/uml/port-helper", NULL };
+OS_LIB_PATH "/uml/port-helper", NULL };
struct port_pre_exec_data data;
new = accept(fd, NULL, 0);
--
2.20.1
Re: Bug#928924: user-mode-linux: xterm functionality broken due to wrong path to port-helper
On Tue, 2019-05-14 at 14:36 +0530, Ritesh Raj Sarraf wrote: > Control: tag -1 +fixed-upstream > > CC: Adding Debian Kernel Maintainers > > > Hello Paul, > > I submitted this fix upstream to the kernel some time ago. I don't > recollect if the 4.19 kernel is what had it included. It went into 4.20 and hasn't been applied to 4.19-stable. > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9ca19a3a3e2482916c475b90f3d7fa2a03d8e5ed > > Irrespective, I think it is a fair candidate to be backported if 4.19 > missed that window. For User-Mode-Linux, The sources are the same that > the Debian Linux kernel team maintains. So either they could pick this > commit as a patch or else I'll try to look into it soon. [...] Can you please send this request to sta...@vger.kernel.org as well? Ben. -- Ben Hutchings I haven't lost my mind; it's backed up on tape somewhere. signature.asc Description: This is a digitally signed message part
Re: Bug#928924: user-mode-linux: xterm functionality broken due to wrong path to port-helper
Control: tag -1 +fixed-upstream CC: Adding Debian Kernel Maintainers Hello Paul, I submitted this fix upstream to the kernel some time ago. I don't recollect if the 4.19 kernel is what had it included. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9ca19a3a3e2482916c475b90f3d7fa2a03d8e5ed Irrespective, I think it is a fair candidate to be backported if 4.19 missed that window. For User-Mode-Linux, The sources are the same that the Debian Linux kernel team maintains. So either they could pick this commit as a patch or else I'll try to look into it soon. Thanks, Ritesh On Mon, 2019-05-13 at 13:01 +0800, Paul Wise wrote: > Package: user-mode-linux > Version: 4.19-1um-1 > Severity: important > File: /usr/bin/linux.uml > > linux.uml in a GNOME terminal gives these errors in new tabs: > > There was an error creating the child process for this terminal > Failed to execute child process “port-helper” (No such file or > directory) > > The linux.uml binary references the wrong path for port-helper: > > $ strings /usr/bin/linux.uml | grep port-helper > /usr/lib//uml/port-helper > > $ dpkg -L uml-utilities | grep port-helper > /usr/lib64/uml/port-helper > > Please fix this issue in Debian buster, it is an annoying bug. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System signature.asc Description: This is a digitally signed message part
