[Kernel-packages] [Bug 1775068] Re: Volume control not working Dell XPS 27 (7760)

2019-07-23 Thread Juerg Haefliger
** Changed in: linux (Ubuntu Bionic)
   Status: New => Fix Committed

-- 
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/1775068

Title:
  Volume control not working Dell XPS 27 (7760)

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Pressing vol up/vol down show OSD change up/down but volume all time
  is at 100%.

  I found temporary fix:

  Add section:
  [Element Master]
  switch = mute
  volume = ignore

  To:
  /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  trolinka   1610 F pulseaudio
   /dev/snd/controlC1:  trolinka   1610 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-02 (121 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner 
sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0T12MX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 13
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 7760 AIO
  dmi.sys.vendor: Dell Inc.
  ---
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  trolinka   1846 F pulseaudio
   /dev/snd/controlC1:  trolinka   1846 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-02 (122 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Dell Inc. XPS 7760 AIO
  Package: pulseaudio 1:11.1-1ubuntu7.1
  PackageArchitecture: amd64
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=3df8d974-f6bb-455e-a7a6-a7099388ad54 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner 
sudo vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0T12MX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 13
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 7760 AIO
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775068/+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 1764792] Re: Build Nvidia drivers in conjunction with kernel

2019-07-23 Thread Juerg Haefliger
** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Bionic)
   Status: New => Fix Committed

-- 
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/1764792

Title:
  Build Nvidia drivers in conjunction with kernel

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Released

Bug description:
  We want to deliver a great out of the box experience of Ubuntu users
  running on Nvidia GPU enabled platforms (including instances in the
  cloud).  Can we explore the possibility of pre-building the nvidia
  drivers alongside the kernel build, but not pre-link the drivers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764792/+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 1807378] Re: zfs/spl build in conjunction with the kernel from DKMS source

2019-07-23 Thread Juerg Haefliger
** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Bionic)
   Status: New => Fix Committed

-- 
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/1807378

Title:
  zfs/spl build in conjunction with the kernel from DKMS source

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  We currently carry a complete copy of the zfs/spl source in the kernel
  package.  It would be much simpler to maintain if we used the
  published sources for the dkms package to build these at kernel build
  time.  We are still able to sign those modules into the kernel modules
  key.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807378/+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 1788308] Re: [Regression] Colour banding appears on Lenovo B50-80 integrated display

2019-07-23 Thread Juerg Haefliger
** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Bionic)
   Status: New => Fix Committed

-- 
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/1788308

Title:
  [Regression] Colour banding appears on Lenovo B50-80 integrated
  display

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  The problem affects the integrated display on a Lenovo B50-80
  notebook.

  Colour banding is visible everywhere on the system, as dithering seems
  not to be enabled on this 6bpp display. This issue was not present on
  non-HWE Ubuntu 16.04, and it showed up after I upgraded to Ubuntu
  18.04. There was already a very similar bug #1749420 that had a fix
  released, however, because the make and model of an LCD screen in that
  case was different, the quirk added to the kernel did not address the
  problem that affects my machine. The cause of this issue is probably
  the same, since I have checked that pre-4.8.0-rc2 kernels handled
  dithering correctly, and 4.8.0-rc2 and later kernels already had the
  bug described. I believe that adding quirk for an another type of
  display may fix the problem.

  I attached the results of running
  sudo get-edid | parse-edid in a file named edid.txt
  and
  sudo get-edid | edid-decode in a file named edid-decoded.txt.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  me 1245 F pulseaudio
   /dev/snd/controlC1:  me 1245 F pulseaudio
  Date: Wed Aug 22 00:26:15 2018
  HibernationDevice: RESUME=UUID=93b28df5-b453-452b-960d-7173994d778e
  InstallationDate: Installed on 2018-08-21 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 80EW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=a1cd5b8c-2707-4840-858b-3ca12517193b ro quiet splash vt.handoff=1
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A8CN54WW(V3.07)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo B50-80
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo B50-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrA8CN54WW(V3.07):bd09/02/2016:svnLENOVO:pn80EW:pvrLenovoB50-80:rvnLENOVO:rnLenovoB50-80:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoB50-80:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80EW
  dmi.product.version: Lenovo B50-80
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788308/+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 1794387] Re: Colour banding in HP Pavilion 15-n233sl integrated display

2019-07-23 Thread Juerg Haefliger
** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Bionic)
   Status: New => Fix Committed

-- 
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/1794387

Title:
  Colour banding in HP Pavilion 15-n233sl integrated display

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  Colour bandind is visible everywhere in the system, and it appeared
  after I had my integrated monitor replaced. I believe it's not a
  hardware problem, since booting with 'nomodeset' works as expected.

  There were already two similar bugs,
  https://bugs.launchpad.net/bugs/1749420 and
  https://bugs.launchpad.net/bugs/1788308, but the fixes provided for
  those bugs did not work for my specific monitor.

  I'm running Ubuntu 18.04 with kernel linux-image-4.15.0-34-generic,
  installing linux-image-4.18.8 with UKUU didn't help.

  I attached the results of running
  sudo get-edid | parse-edid in a file named edid.txt
  sudo get-edid | edid-decode in a file named edid-decoded.txt
  cat /proc/version_signature in version.log
  sudo lspci -vnvn in lspci-vnvn.log.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matt   1796 F pulseaudio
   /dev/snd/controlC1:  matt   1796 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: KDE neon 18.04
  InstallationDate: Installed on 2018-09-27 (0 days ago)
  InstallationMedia: neon devunstable "Bionic" - Build amd64 LIVE Binary 
20180924-13:08
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision 
HD camera
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=c3f61207-d13e-474b-a499-98030ddef8e1 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-generic N/A
   linux-backports-modules-4.15.0-34-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-34-generic x86_64
  UnreportableReason: Questa segnalazione riguarda un pacchetto che non è 
installato.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo
  _MarkForUpload: False
  dmi.bios.date: 03/13/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.71
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2166
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 29.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.71:bd03/13/2017:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2166:rvr29.42:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 098B1140410620180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794387/+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 1822802] Re: linux-raspi2: 4.15.0-1034.36 -proposed tracker

2019-04-03 Thread Juerg Haefliger
** Summary changed:

- linux-raspi2:  -proposed tracker
+ linux-raspi2: 4.15.0-1034.36 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger 
(juergh)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger 
(juergh)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1822802

Title:
  linux-raspi2: 4.15.0-1034.36 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  kernel-stable-master-bug: 1822820
  phase: Packaging
  phase-changed: Wednesday, 03. April 2019 15:04 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822802/+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 1822809] Re: linux-kvm: 4.15.0-1032.32 -proposed tracker

2019-04-04 Thread Juerg Haefliger
** Summary changed:

- linux-kvm:  -proposed tracker
+ linux-kvm: 4.15.0-1032.32 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger 
(juergh)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger 
(juergh)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1822809

Title:
  linux-kvm: 4.15.0-1032.32 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  kernel-stable-master-bug: 1822820
  phase: Ready for Packaging
  phase-changed: Wednesday, 03. April 2019 08:37 UTC
  reason:
prepare-package: Pending -- version not specified

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822809/+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 1814054] Re: BUG: unable to handle kernel paging request at ee835a95

2019-04-08 Thread Juerg Haefliger
*** This bug is a duplicate of bug 1813244 ***
https://bugs.launchpad.net/bugs/1813244

** This bug is no longer a duplicate of bug 1736390
   openvswitch: kernel oops destroying interfaces on i386
** This bug has been marked a duplicate of bug 1813244
   systemd cause kernel trace "BUG: unable to handle kernel paging request at 
6db23a14" on Cosmic i386

-- 
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/1814054

Title:
  BUG: unable to handle kernel paging request at ee835a95

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux source package in Disco:
  Incomplete

Bug description:
  Booting Bionic i386 in a VM and running the following commands
  repeatedly:

  ovs-vsctl add-br test
  ovs-vsctl del-br test

  
  eventually leads to:

  [   44.476751] IP: kmem_cache_alloc_trace+0x91/0x1d0
  [   44.477299] *pdpt = 1ae13001 *pde =  
  [   44.477956] Oops:  [#1] SMP
  [   44.478340] Modules linked in: dummy openvswitch nsh nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack isofs kvm_intel kvm irqbypass input_leds joydev serio_raw 
sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp 
libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear psmouse virtio_blk virtio_net 
floppy
  [   44.483687] CPU: 0 PID: 553 Comm: systemd-network Tainted: GW  
  4.15.0-44-generic #47-Ubuntu
  [   44.484819] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.11.1-1ubuntu1 04/01/2014
  [   44.485865] EIP: kmem_cache_alloc_trace+0x91/0x1d0
  [   44.486451] EFLAGS: 00010286 CPU: 0
  [   44.486917] EAX: df719701 EBX: ee835a95 ECX: e8e4 EDX: e8e3
  [   44.487663] ESI: df7197e0 EDI: df401a00 EBP: df7cbda0 ESP: df7cbd78
  [   44.488440]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   44.489103] CR0: 80050033 CR2: ee835a95 CR3: 1f7f7ac0 CR4: 06f0
  [   44.489918] DR0:  DR1:  DR2:  DR3: 
  [   44.490717] DR6: fffe0ff0 DR7: 0400
  [   44.491265] Call Trace:
  [   44.491655]  ? seq_open+0x2d/0x80
  [   44.492136]  seq_open+0x2d/0x80
  [   44.492602]  kernfs_fop_open+0x1a0/0x360
  [   44.493146]  do_dentry_open+0x1ac/0x2f0
  [   44.493688]  ? kernfs_seq_start+0x90/0x90
  [   44.494258]  vfs_open+0x41/0x70
  [   44.494717]  path_openat+0x5e0/0x13f0
  [   44.495234]  ? dput.part.23+0xcf/0x1e0
  [   44.495761]  ? mntput+0x20/0x40
  [   44.496227]  do_filp_open+0x6a/0xd0
  [   44.496739]  ? __alloc_fd+0x36/0x160
  [   44.497267]  do_sys_open+0x1ad/0x2b0
  [   44.497800]  SyS_openat+0x1b/0x20
  [   44.498297]  do_fast_syscall_32+0x7f/0x1e0
  [   44.498882]  entry_SYSENTER_32+0x4e/0x7c
  [   44.499450] EIP: 0xb7f0dd09
  [   44.499888] EFLAGS: 0282 CPU: 0
  [   44.500410] EAX: ffda EBX: ff9c ECX: bfa5fdc0 EDX: 00088000
  [   44.501244] ESI:  EDI:  EBP: 00088000 ESP: bfa5fc60
  [   44.502078]  DS: 007b ES: 007b FS:  GS: 0033 SS: 007b
  [   44.502833] Code: 33 87 b8 00 00 00 89 75 dc 89 c3 89 45 e0 8b 45 f0 31 f3 
8b 37 64 0f c7 0e 0f 94 c0 84 c0 74 bb 8b 75 dc 3b 75 e0 74 0e 03 5f 14 <33> 1b 
33 9f b8 00 00 00 0f 18 03 f7 45 ec 00 80 00 00 0f 85 f7
  [   44.505346] EIP: kmem_cache_alloc_trace+0x91/0x1d0 SS:ESP: 0068:df7cbd78
  [   44.506250] CR2: ee835a95
  [   44.506751] ---[ end trace 3c49b27dd79507a3 ]---
  [   44.508624] BUG: unable to handle kernel paging request at ee835a95
  [   44.509508] IP: __kmalloc+0x85/0x220
  [   44.510020] *pdpt = 1ae13001 *pde =  
  [   44.510829] Oops:  [#2] SMP
  [   44.511307] Modules linked in: dummy openvswitch nsh nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack isofs kvm_intel kvm irqbypass input_leds joydev serio_raw 
sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp 
libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear psmouse virtio_blk virtio_net 
floppy
  [   44.517190] CPU: 0 PID: 1854 Comm: journal-offline Tainted: G  D W 
   4.15.0-44-generic #47-Ubuntu
  [   44.518478] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.11.1-1ubuntu1 04/01/2014
  [   44.519730] EIP: __kmalloc+0x85/0x220
  [   44.520275] EFLAGS: 00010086 CPU: 0
  [   44.520794] EAX: dfacdbf0 EBX:  ECX: ee835a95 EDX: e8e4
  [   44.521666] ESI: dae09bf0 EDI: df401a00 EBP: dcaf59fc ESP: dcaf59d4
  [   44.522497]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   

[Kernel-packages] [Bug 1712831] Re: 4.12.0-11-generic - crashing in infrastructure on i386 openvswitch tests

2019-04-08 Thread Juerg Haefliger
*** This bug is a duplicate of bug 1813244 ***
https://bugs.launchpad.net/bugs/1813244

** This bug is no longer a duplicate of bug 1736390
   openvswitch: kernel oops destroying interfaces on i386
** This bug has been marked a duplicate of bug 1813244
   systemd cause kernel trace "BUG: unable to handle kernel paging request at 
6db23a14" on Cosmic i386

-- 
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/1712831

Title:
  4.12.0-11-generic - crashing in infrastructure on i386 openvswitch
  tests

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  Hi,
  this seems to me to be a kernel crash of some sorts.
  Somewhat in the spirit of older bugs:
  - bug 1630940
  - bug 1630578

  Xnox asked me to look into a hang on openvswitch dep8 tests.
  What I found initially was in the log just
"ERROR: Removing temporary files on testbed timed out"
  That message brought me to the two bugs above.

  But in there I read that this was the infra running dep8 crashing.
  So for a better bug report I tried to reproduce locally and that actually 
seems to work very reliable.

  To reproduce do:
  $ autopkgtest-buildvm-ubuntu-cloud -a i386 -r artful -s 10G
  $ pull-lp-source openvswitch
  $ autopkgtest --apt-upgrade --shell --no-built-binaries 
openvswitch_2.8.0~git20170809.7aa47a19d-0ubuntu1.dsc -- qemu 
~/work/autopkgtest-artful-i386.img
  # This guest currently will crash after a while of testing

  
  But with that running you can attach to the console and monitor of that guest.
  For example:
  $ sudo nc -U /tmp/autopkgtest-virt-qemu.*/ttyS0

  That gave me a crash on the hang which kind of matches the older bugs, here 
the console:
  [   54.256253] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   54.257156] IP: add_grec+0x28/0x440
  [   54.257553] *pdpt = 1a869001 *pde =  
  [   54.257555] 
  [   54.258338] Oops:  [#1] SMP
  [   54.258638] Modules linked in: veth openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm irqbypass joydev 
input_leds serio_raw 9pnet_virtio parport_pc 9pnet parport qemu_fw_cfg 
i2c_piix4 mac_hid ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse 
virtio_blk virtio_net floppy pata_acpi
  [   54.261891] CPU: 0 PID: 0 Comm: swapper/0 Tainted: GW   
4.12.0-11-generic #12-Ubuntu
  [   54.262715] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.1-1ubuntu1~cloud0 04/01/2014
  [   54.263610] task: c7b622c0 task.stack: c7b5a000
  [   54.264039] EIP: add_grec+0x28/0x440
  [   54.264378] EFLAGS: 00010202 CPU: 0
  [   54.264711] EAX:  EBX: dd062540 ECX: 0006 EDX: dd062540
  [   54.265308] ESI: dd1e6e00 EDI: dd1e6e00 EBP: dbcc5f30 ESP: dbcc5ef0
  [   54.265793]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   54.266297] CR0: 80050033 CR2:  CR3: 1e930d80 CR4: 06f0
  [   54.266885] Call Trace:
  [   54.267120]  
  [   54.267349]  mld_ifc_timer_expire+0xfe/0x250
  [   54.267754]  ? mld_dad_timer_expire+0x50/0x50
  [   54.268173]  call_timer_fn+0x30/0x120
  [   54.268524]  ? mld_dad_timer_expire+0x50/0x50
  [   54.268942]  ? mld_dad_timer_expire+0x50/0x50
  [   54.269364]  run_timer_softirq+0x3c5/0x420
  [   54.269760]  ? __softirqentry_text_start+0x8/0x8
  [   54.270198]  __do_softirq+0xa9/0x245
  [   54.270539]  ? __softirqentry_text_start+0x8/0x8
  [   54.270976]  do_softirq_own_stack+0x24/0x30
  [   54.271373]  
  [   54.271611]  irq_exit+0xad/0xb0
  [   54.271913]  smp_apic_timer_interrupt+0x38/0x50
  [   54.272344]  apic_timer_interrupt+0x39/0x40
  [   54.272745] EIP: native_safe_halt+0x5/0x10
  [   54.273139] EFLAGS: 0246 CPU: 0
  [   54.273624] EAX:  EBX:  ECX: 0001 EDX: 
  [   54.274000] ESI:  EDI: c7b622c0 EBP: c7b5bf10 ESP: c7b5bf10
  [   54.274361]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   54.274687]  default_idle+0x1c/0xf0
  [   54.274896]  arch_cpu_idle+0xe/0x10
  [   54.275286]  default_idle_call+0x1e/0x30
  [   54.275787]  do_idle+0x145/0x1c0
  [   54.276092]  cpu_startup_entry+0x65/0x70
  [   54.276441]  rest_init+0x62/0x70
  [   54.276718]  start_kernel+0x3be/0x3d7
  [   54.276974]  i386_start_kernel+0x9d/0xa1
  [   54.277260]  startup_32_smp+0x16b/0x16d
  [   54.277509] Code: 00 00 00 3e 8d 74 26 00 55 89 e5 57 56 53 89 c6 83 ec 34 
89 4d e8 65 a1 14 00 00 00 89 45 f0 31 c0 8b 42 10 f6 42 48 08 89 45 cc <8b> 00 
c7 45 ec 00 00 00 00 89 45 c8 89 f0 0f 85 b4 02 00 00 8b
  [   54.279314] EIP: add_grec+0x28/0x440 SS:ESP: 0068:dbcc5ef0
  [   54.279829] CR2: 
  [   54.280143] ---[ end trace 3164b1c0dd7745bc ]---
  [   54.280550] Kernel panic - not syncing: Fatal exception in interrupt
  [   54.281078] Kernel Offset: 0x600 from 0xc1000

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel oops destroying interfaces on i386

2019-04-08 Thread Juerg Haefliger
*** This bug is a duplicate of bug 1813244 ***
https://bugs.launchpad.net/bugs/1813244

** This bug has been marked a duplicate of bug 1813244
   systemd cause kernel trace "BUG: unable to handle kernel paging request at 
6db23a14" on Cosmic i386

-- 
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/1736390

Title:
  openvswitch: kernel oops destroying interfaces on i386

Status in linux package in Ubuntu:
  In Progress
Status in openvswitch package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  Won't Fix
Status in openvswitch source package in Artful:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in openvswitch source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  In Progress
Status in openvswitch source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  In Progress
Status in openvswitch source package in Disco:
  Invalid

Bug description:
  == SRU Justification ==

  Commit 120645513f55 ("openvswitch: Add eventmask support to CT
  action.") introduced a regression on i386. Simply running the
  following commands in a loop will trigger a crash rather quickly:

  ovs-vsctl add-br test
  ovs-vsctl del-br test

  == Fix ==

  Disable the logic introduced by the above commit on i386.

  == Regression Potential ==

  Low, the above commit introduced a new feature. Per upstream, the
  result of not having this feature results in higher CPU usage and
  potential buffering issues in user space.

  == Test Case ==

  See SRU justification above.


  Original bug description:

  Reproducable on bionic using the autopkgtest's from openvswitch on
  i386:

  [   41.420568] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   41.421000] IP: igmp_group_dropped+0x21/0x220
  [   41.421246] *pdpt = 1d62c001 *pde = 

  [   41.421659] Oops:  [#1] SMP
  [   41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass 
input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg 
mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse 
virtio_blk virtio_net pata_acpi floppy
  [   41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW   
4.13.0-18-generic #21-Ubuntu
  [   41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [   41.424849] Workqueue: netns cleanup_net
  [   41.425071] task: db8fba80 task.stack: dba1
  [   41.425346] EIP: igmp_group_dropped+0x21/0x220
  [   41.425656] EFLAGS: 00010202 CPU: 0
  [   41.425864] EAX:  EBX: dd726360 ECX: dba11e6c EDX: 0002
  [   41.426335] ESI:  EDI: dd4db500 EBP: dba11dcc ESP: dba11d94
  [   41.426687]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   41.426990] CR0: 80050033 CR2:  CR3: 1e6d6d60 CR4: 06f0
  [   41.427340] Call Trace:
  [   41.427485]  ? __wake_up+0x36/0x40
  [   41.427680]  ip_mc_down+0x27/0x90
  [   41.427869]  inetdev_event+0x398/0x4e0
  [   41.428082]  ? skb_dequeue+0x5b/0x70
  [   41.428286]  ? wireless_nlevent_flush+0x4c/0x90
  [   41.428541]  notifier_call_chain+0x4e/0x70
  [   41.428772]  raw_notifier_call_chain+0x11/0x20
  [   41.429023]  call_netdevice_notifiers_info+0x2a/0x60
  [   41.429301]  dev_close_many+0x9d/0xe0
  [   41.429509]  rollback_registered_many+0xd7/0x380
  [   41.429768]  unregister_netdevice_many.part.102+0x10/0x80
  [   41.430075]  default_device_exit_batch+0x134/0x160
  [   41.430344]  ? do_wait_intr_irq+0x80/0x80
  [   41.430650]  ops_exit_list.isra.8+0x4d/0x60
  [   41.430886]  cleanup_net+0x18e/0x260
  [   41.431090]  process_one_work+0x1a0/0x390
  [   41.431317]  worker_thread+0x37/0x450
  [   41.431525]  kthread+0xf3/0x110
  [   41.431714]  ? process_one_work+0x390/0x390
  [   41.431941]  ? kthread_create_on_node+0x20/0x20
  [   41.432187]  ret_from_fork+0x19/0x24
  [   41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 
56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 
8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00
  [   41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94
  [   41.433750] CR2: 
  [   41.433961] ---[ end trace 595db54cab84070c ]---

  system then becomes unresponsive; no further interfaces can be
  created.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+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 1813244] Re: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386

2019-04-08 Thread Juerg Haefliger
@james-page, the fix has been sent to the Ubuntu kernel mailing list
[1], so it's scheduled for the next SRU cycle (assuming it gets two
ACKs).

[1] https://lists.ubuntu.com/archives/kernel-team/2019-April/099883.html

-- 
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/1813244

Title:
  systemd cause kernel trace "BUG: unable to handle kernel paging
  request at 6db23a14" on Cosmic i386

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  SRU Justification:

  [Impact]

   * Flow action buffer can be incorrectly resized to contain the newly
  added action entries: the buffer is always resized multiplying the
  previous size by 2, but this might be not enough if the requested size
  is bigger than previous_size*2, causing a buffer overflow

   * The fix correctly resizes the buffer to prevent the buffer overflow

   * Despite the subject this bug can be triggered potentially on any
  architecture, but it is very likely to happen on i386 running the
  following test case

  [Test Case]

   * run this openvswitch test case:
  https://launchpadlibrarian.net/416589265/lp1262692

  [Fix]

   * Instead of resizing the buffer by a factor of 2, use
  max(current_size * 2, current_size + requested_size)

  [Regression Potential]

   * Fix has been tested on the affected platform and verified using
  slub_debug. The patch has been queued up for -stable by David Miller,
  it will be included upstream for the next merge window. It is also a
  very small patch (a one-liner basically), so backport changes are
  minimal.

  [Original bug report]

  This issue was found after leaving a SUT to run overnight (was testing
  the ubuntu_cts_kernel test 13 hours ago before this happens). Can't
  tell if this is a regression, as I haven't find a way to reproduce it.
  But I do see similar reports on the Internet [1]

  After checking the systemd service timers, it looks like this is
  caused by the logrotate.service:

  $ sudo systemctl list-timers --all
  NEXT LEFT  LAST 
PASSEDUNIT ACTIVATES
  Fri 2019-01-25 06:18:58 UTC  1h 40min left Thu 2019-01-24 06:34:15 UTC  22h 
ago   apt-daily-upgrade.timer  apt-daily-upgrade.service
  Fri 2019-01-25 09:15:54 UTC  4h 37min left Fri 2019-01-25 03:43:24 UTC  55min 
ago apt-daily.timer  apt-daily.service
  Fri 2019-01-25 17:02:47 UTC  12h left  Fri 2019-01-25 04:20:17 UTC  18min 
ago motd-news.timer  motd-news.service
  Sat 2019-01-26 00:00:00 UTC  19h left  Fri 2019-01-25 00:00:37 UTC  4h 
38min ago  logrotate.timer  logrotate.service
  Sat 2019-01-26 04:02:38 UTC  23h left  Fri 2019-01-25 04:02:38 UTC  36min 
ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.serv
  Mon 2019-01-28 00:00:00 UTC  2 days left   Wed 2019-01-23 10:44:18 UTC  1 day 
17h ago fstrim.timer fstrim.service
  n/a  n/a   n/a  n/a   
snapd.snap-repair.timer  snapd.snap-repair.service

  7 timers listed.

  After this happens, you won't be able to reboot it with the command.
  $ sudo reboot
  sudo: unable to resolve host onza: Resource temporarily unavailable
  Killed

  Here is the error message, please refer to the attachment for a
  complete syslog:

  Jan 25 00:00:37 onza systemd[1]: Starting Rotate log files...
  Jan 25 00:00:37 onza kernel: [45282.956634] BUG: unable to handle kernel 
paging request at 6db23a14
  Jan 25 00:00:37 onza kernel: [45282.962902] *pdpt = 33fa1001 *pde = 

  Jan 25 00:00:37 onza kernel: [45282.968650] Oops:  [#1] SMP
  Jan 25 00:00:37 onza kernel: [45282.971796] CPU: 0 PID: 407 Comm: 
systemd-journal Not tainted 4.18.0-14-generic #15-Ubuntu
  Jan 25 00:00:37 onza kernel: [45282.980330] Hardware name: Dell Inc. 
PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012
  Jan 25 00:00:37 onza kernel: [45282.988127] EIP: __kmalloc+0xc9/0x240
  Jan 25 00:00:37 onza kernel: [45282.991785] Code: 4d e0 8d 4a 01 31 c6 8b 45 
f0 89 75 dc 31 f3 8b 37 64 0f c7 0e 0f 94 c0 84 c0 74 b9 8b 75 e4 8b 45 dc 39 
45 e0 74 0e 03 5f 14 <33> 1b 33 9f b4 00 00 00 0f 18 03 f7 45 ec 00 80 00 00 0f 
85 3f 01
  Jan 25 00:00:37 onza kernel: [45283.011254] EAX: 9e20b374 EBX: 6db23a14 ECX: 
350d EDX: 350c
  Jan 25 00:00:37 onza kernel: [45283.017769] ESI: eac03a00 EDI: eac03a00 EBP: 
f461fd9c ESP: f461fd74
  Jan 25 00:00:37 onza kernel: [45283.024304] DS: 007b ES: 007b FS: 00d8 GS: 
00e0 SS: 0068 EFLAGS: 00010206
  Jan 25 00:00:37 onza kernel: [45283.031245] CR0: 80050033 CR2: 6db23a14 CR3: 
29d304a0 CR4: 06f0
  Jan 25 00:00:37 onza kernel: [45283.037770] Call Trace:
  Jan 25 00:00:37 onza kernel: [45283.040395]  ? 
ext4_htree_store_dirent+0x2e/0x120
  Jan 25 00:00:37 onza kerne

[Kernel-packages] [Bug 1788098] Re: Avoid migration issues with aligned 2MB THB

2019-04-08 Thread Juerg Haefliger
Stefan NACK'ed the series. For some unknown reason that email did make
it into the archive so here is ist content:

> Since commit fb1522e099f0 ("KVM: update to new mmu_notifier semantic
> v2", 2017-08-31), the MMU notifier code in KVM no longer calls the
> kvm_unmap_hva callback.  This removes the PPC implementations of
> kvm_unmap_hva().  

This is not really the way SRUs should be done. We cannot remove support for
interfaces after release. Also the amount of change as a requisite should be
kept as minimal as possible. This just feels like too many changes without a
strong argument on why this must be done that way.

-Stefan

-- 
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/1788098

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next&id=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+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 1813244] Re: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386

2019-04-08 Thread Juerg Haefliger
** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

-- 
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/1813244

Title:
  systemd cause kernel trace "BUG: unable to handle kernel paging
  request at 6db23a14" on Cosmic i386

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

   * Flow action buffer can be incorrectly resized to contain the newly
  added action entries: the buffer is always resized multiplying the
  previous size by 2, but this might be not enough if the requested size
  is bigger than previous_size*2, causing a buffer overflow

   * The fix correctly resizes the buffer to prevent the buffer overflow

   * Despite the subject this bug can be triggered potentially on any
  architecture, but it is very likely to happen on i386 running the
  following test case

  [Test Case]

   * run this openvswitch test case:
  https://launchpadlibrarian.net/416589265/lp1262692

  [Fix]

   * Instead of resizing the buffer by a factor of 2, use
  max(current_size * 2, current_size + requested_size)

  [Regression Potential]

   * Fix has been tested on the affected platform and verified using
  slub_debug. The patch has been queued up for -stable by David Miller,
  it will be included upstream for the next merge window. It is also a
  very small patch (a one-liner basically), so backport changes are
  minimal.

  [Original bug report]

  This issue was found after leaving a SUT to run overnight (was testing
  the ubuntu_cts_kernel test 13 hours ago before this happens). Can't
  tell if this is a regression, as I haven't find a way to reproduce it.
  But I do see similar reports on the Internet [1]

  After checking the systemd service timers, it looks like this is
  caused by the logrotate.service:

  $ sudo systemctl list-timers --all
  NEXT LEFT  LAST 
PASSEDUNIT ACTIVATES
  Fri 2019-01-25 06:18:58 UTC  1h 40min left Thu 2019-01-24 06:34:15 UTC  22h 
ago   apt-daily-upgrade.timer  apt-daily-upgrade.service
  Fri 2019-01-25 09:15:54 UTC  4h 37min left Fri 2019-01-25 03:43:24 UTC  55min 
ago apt-daily.timer  apt-daily.service
  Fri 2019-01-25 17:02:47 UTC  12h left  Fri 2019-01-25 04:20:17 UTC  18min 
ago motd-news.timer  motd-news.service
  Sat 2019-01-26 00:00:00 UTC  19h left  Fri 2019-01-25 00:00:37 UTC  4h 
38min ago  logrotate.timer  logrotate.service
  Sat 2019-01-26 04:02:38 UTC  23h left  Fri 2019-01-25 04:02:38 UTC  36min 
ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.serv
  Mon 2019-01-28 00:00:00 UTC  2 days left   Wed 2019-01-23 10:44:18 UTC  1 day 
17h ago fstrim.timer fstrim.service
  n/a  n/a   n/a  n/a   
snapd.snap-repair.timer  snapd.snap-repair.service

  7 timers listed.

  After this happens, you won't be able to reboot it with the command.
  $ sudo reboot
  sudo: unable to resolve host onza: Resource temporarily unavailable
  Killed

  Here is the error message, please refer to the attachment for a
  complete syslog:

  Jan 25 00:00:37 onza systemd[1]: Starting Rotate log files...
  Jan 25 00:00:37 onza kernel: [45282.956634] BUG: unable to handle kernel 
paging request at 6db23a14
  Jan 25 00:00:37 onza kernel: [45282.962902] *pdpt = 33fa1001 *pde = 

  Jan 25 00:00:37 onza kernel: [45282.968650] Oops:  [#1] SMP
  Jan 25 00:00:37 onza kernel: [45282.971796] CPU: 0 PID: 407 Comm: 
systemd-journal Not tainted 4.18.0-14-generic #15-Ubuntu
  Jan 25 00:00:37 onza kernel: [45282.980330] Hardware name: Dell Inc. 
PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012
  Jan 25 00:00:37 onza kernel: [45282.988127] EIP: __kmalloc+0xc9/0x240
  Jan 25 00:00:37 onza kernel: [45282.991785] Code: 4d e0 8d 4a 01 31 c6 8b 45 
f0 89 75 dc 31 f3 8b 37 64 0f c7 0e 0f 94 c0 84 c0 74 b9 8b 75 e4 8b 45 dc 39 
45 e0 74 0e 03 5f 14 <33> 1b 33 9f b4 00 00 00 0f 18 03 f7 45 ec 00 80 00 00 0f 
85 3f 01
  Jan 25 00:00:37 onza kernel: [45283.011254] EAX: 9e20b374 EBX: 6db23a14 ECX: 
350d EDX: 350c
  Jan 25 00:00:37 onza kernel: [45283.017769] ESI: eac03a00 EDI: eac03a00 EBP: 
f461fd9c ESP: f461fd74
  Jan 25 00:00:37 onza kernel: [45283.024304] DS: 007b ES: 007b FS: 00d8 GS: 
00e0 SS: 0068 EFLAGS: 00010206
  Jan 25 00:00:37 onza kernel: [45283.031245] CR0: 80050033 CR2: 6db23a14 CR3: 
29d304a0 CR4: 06f0
  Jan 25 00:00:37 on

[Kernel-packages] [Bug 1813244] Re: systemd cause kernel trace "BUG: unable to handle kernel paging request at 6db23a14" on Cosmic i386

2019-04-08 Thread Juerg Haefliger
The referenced patch fixes an earlier commit [1] that was added in the
3.11 time frame so Trusty needs this too.

[1] 74f84a5726c7 ("openvswitch: Copy individual actions.")


** Also affects: linux (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Trusty)
   Status: New => Confirmed

-- 
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/1813244

Title:
  systemd cause kernel trace "BUG: unable to handle kernel paging
  request at 6db23a14" on Cosmic i386

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

   * Flow action buffer can be incorrectly resized to contain the newly
  added action entries: the buffer is always resized multiplying the
  previous size by 2, but this might be not enough if the requested size
  is bigger than previous_size*2, causing a buffer overflow

   * The fix correctly resizes the buffer to prevent the buffer overflow

   * Despite the subject this bug can be triggered potentially on any
  architecture, but it is very likely to happen on i386 running the
  following test case

  [Test Case]

   * run this openvswitch test case:
  https://launchpadlibrarian.net/416589265/lp1262692

  [Fix]

   * Instead of resizing the buffer by a factor of 2, use
  max(current_size * 2, current_size + requested_size)

  [Regression Potential]

   * Fix has been tested on the affected platform and verified using
  slub_debug. The patch has been queued up for -stable by David Miller,
  it will be included upstream for the next merge window. It is also a
  very small patch (a one-liner basically), so backport changes are
  minimal.

  [Original bug report]

  This issue was found after leaving a SUT to run overnight (was testing
  the ubuntu_cts_kernel test 13 hours ago before this happens). Can't
  tell if this is a regression, as I haven't find a way to reproduce it.
  But I do see similar reports on the Internet [1]

  After checking the systemd service timers, it looks like this is
  caused by the logrotate.service:

  $ sudo systemctl list-timers --all
  NEXT LEFT  LAST 
PASSEDUNIT ACTIVATES
  Fri 2019-01-25 06:18:58 UTC  1h 40min left Thu 2019-01-24 06:34:15 UTC  22h 
ago   apt-daily-upgrade.timer  apt-daily-upgrade.service
  Fri 2019-01-25 09:15:54 UTC  4h 37min left Fri 2019-01-25 03:43:24 UTC  55min 
ago apt-daily.timer  apt-daily.service
  Fri 2019-01-25 17:02:47 UTC  12h left  Fri 2019-01-25 04:20:17 UTC  18min 
ago motd-news.timer  motd-news.service
  Sat 2019-01-26 00:00:00 UTC  19h left  Fri 2019-01-25 00:00:37 UTC  4h 
38min ago  logrotate.timer  logrotate.service
  Sat 2019-01-26 04:02:38 UTC  23h left  Fri 2019-01-25 04:02:38 UTC  36min 
ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.serv
  Mon 2019-01-28 00:00:00 UTC  2 days left   Wed 2019-01-23 10:44:18 UTC  1 day 
17h ago fstrim.timer fstrim.service
  n/a  n/a   n/a  n/a   
snapd.snap-repair.timer  snapd.snap-repair.service

  7 timers listed.

  After this happens, you won't be able to reboot it with the command.
  $ sudo reboot
  sudo: unable to resolve host onza: Resource temporarily unavailable
  Killed

  Here is the error message, please refer to the attachment for a
  complete syslog:

  Jan 25 00:00:37 onza systemd[1]: Starting Rotate log files...
  Jan 25 00:00:37 onza kernel: [45282.956634] BUG: unable to handle kernel 
paging request at 6db23a14
  Jan 25 00:00:37 onza kernel: [45282.962902] *pdpt = 33fa1001 *pde = 

  Jan 25 00:00:37 onza kernel: [45282.968650] Oops:  [#1] SMP
  Jan 25 00:00:37 onza kernel: [45282.971796] CPU: 0 PID: 407 Comm: 
systemd-journal Not tainted 4.18.0-14-generic #15-Ubuntu
  Jan 25 00:00:37 onza kernel: [45282.980330] Hardware name: Dell Inc. 
PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012
  Jan 25 00:00:37 onza kernel: [45282.988127] EIP: __kmalloc+0xc9/0x240
  Jan 25 00:00:37 onza kernel: [45282.991785] Code: 4d e0 8d 4a 01 31 c6 8b 45 
f0 89 75 dc 31 f3 8b 37 64 0f c7 0e 0f 94 c0 84 c0 74 b9 8b 75 e4 8b 45 dc 39 
45 e0 74 0e 03 5f 14 <33> 1b 33 9f b4 00 00 00 0f 18 03 f7 45 ec 00 80 00 00 0f 
85 3f 01
  Jan 25 00:00:37 onza kernel: [45283.011254] EAX: 9e20b374 EBX: 6db23a14 ECX: 
350d EDX: 350c
  Jan 25 00:00:37 onza kernel: [45283.017769] ESI: eac03a00 EDI: eac03a00 EBP: 
f461fd9c ESP: f461fd74
  Jan 25 00:00:37 onza kernel: [45283.024304] DS: 007b ES: 007b FS: 00d8 GS: 
00e0 SS: 0068 EFL

[Kernel-packages] [Bug 1822810] Re: linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

2019-04-10 Thread Juerg Haefliger
** Summary changed:

- linux-ibm-gt:  -proposed tracker
+ linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger 
(juergh)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger 
(juergh)

-- 
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/1822810

Title:
  linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  kernel-stable-master-bug: 1822820
  phase: Ready for Packaging
  phase-changed: Wednesday, 03. April 2019 09:02 UTC
  reason:
prepare-package: Pending -- version not specified

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822810/+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 1811850] Re: linux-ibm-gt: 4.15.0-1015.17 -proposed tracker

2019-04-10 Thread Juerg Haefliger
*** This bug is a duplicate of bug 1822810 ***
https://bugs.launchpad.net/bugs/1822810

** This bug is no longer a duplicate of bug 1819701
   linux-ibm-gt: 4.15.0-1018.20 -proposed tracker
** This bug has been marked a duplicate of bug 1822810
   linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

-- 
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/1811850

Title:
  linux-ibm-gt: 4.15.0-1015.17 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.15.0-1015.17 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  phase: Testing
  phase-changed: Monday, 28. January 2019 18:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811850/+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 1819701] Re: linux-ibm-gt: 4.15.0-1018.20 -proposed tracker

2019-04-10 Thread Juerg Haefliger
*** This bug is a duplicate of bug 1822810 ***
https://bugs.launchpad.net/bugs/1822810

** This bug has been marked a duplicate of bug 1822810
   linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

-- 
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/1819701

Title:
  linux-ibm-gt: 4.15.0-1018.20 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Ready for Release
  phase-changed: Tuesday, 02. April 2019 09:48 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Pending -- ready to copy
promote-to-updates: Pending -- ready to copy

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819701/+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 1815061] Re: linux-ibm-gt: 4.15.0-1016.18 -proposed tracker

2019-04-10 Thread Juerg Haefliger
*** This bug is a duplicate of bug 1822810 ***
https://bugs.launchpad.net/bugs/1822810

** This bug is no longer a duplicate of bug 1819701
   linux-ibm-gt: 4.15.0-1018.20 -proposed tracker
** This bug has been marked a duplicate of bug 1822810
   linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

-- 
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/1815061

Title:
  linux-ibm-gt: 4.15.0-1016.18 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug is for tracking the 4.15.0-1016.18 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814726
  phase: Ready for Testing
  phase-changed: Sunday, 03. March 2019 06:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1815061/+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 1788098] Re: Avoid migration issues with aligned 2MB THB

2019-04-11 Thread Juerg Haefliger
Leonardo, since you seem to have a reliable reproducer now, could you
give this test kernel [1] a try? It just contains commit c066fafc595e
("KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()") and
is basically what Joe gave you (comment #5) but at that time you weren't
able to reproduce the issue.

[1] https://kernel.ubuntu.com/~juergh/lp1788098/

-- 
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/1788098

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next&id=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+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 1767857] Re: Kernel 4.4.0-122 Breaks qemu-system-x86

2019-04-16 Thread Juerg Haefliger
/usr/bin/qemu-system-i386 -name ldap -S -machine
pc-1.0,accel=kvm,usb=off -cpu host -m 1072 -realtime mlock=off -smp
1,sockets=1,cores=1,threads=1 -uuid 2a6c478a-9bd8-40f6-83cd-b2bf681ef5a0
-no-user-config -nodefaults -chardev
socket,id=charmonitor,path=/var/lib/libvirt/qemu/ldap.monitor,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-
shutdown -boot strict=on -device piix3-usb-
uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-
serial0,bus=pci.0,addr=0x5 -drive file=/opt/VIRT/LDAP/vda.raw,if=none,id
=drive-virtio-disk0,format=raw -device virtio-blk-
pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-
disk0,bootindex=1 -netdev tap,fd=23,id=hostnet0,vhost=on,vhostfd=24
-device virtio-net-
pci,netdev=hostnet0,id=net0,mac=52:54:00:4a:93:0a,bus=pci.0,addr=0x3
-chardev
socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/ldap.org.qemu.guest_agent.0,server,nowait
-device virtserialport,bus=virtio-
serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0
-chardev spicevmc,id=charchannel1,name=vdagent -device
virtserialport,bus=virtio-
serial0.0,nr=2,chardev=charchannel1,id=channel1,name=com.redhat.spice.0
-chardev pty,id=charconsole0 -device
virtconsole,chardev=charconsole0,id=console0 -device usb-
tablet,id=input0 -vnc 127.0.0.1:59 -device qxl-
vga,id=video0,ram_size=67108864,vram_size=67108864,bus=pci.0,addr=0x2
-device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-
duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-
pci,id=balloon0,bus=pci.0,addr=0x7

-- 
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/1767857

Title:
  Kernel 4.4.0-122 Breaks qemu-system-x86

Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Fully updated xubuntu 16.04 running kernel 4.4.0-122 breaks qemu-
  system-x86: black screen displays and qemu-system-x86 runs at 100% cpu
  indefinitely. Boot the same system with kernel 4.4.0-119 and qemu-
  system-x86 works fine running a Windows 10 VM.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu-system-x86 1:2.5+dfsg-5ubuntu10.25
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic i686
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sun Apr 29 15:58:25 2018
  InstallationDate: Installed on 2014-04-29 (1460 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0   394 2  0.0 [kvm-irqfd-clean]
  MachineType: Dell Inc. Inspiron 518
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic 
root=UUID=7cffb293-c044-4b2c-8343-dc50fd16db97 ro --verbose nosplash 
nmi_watchdog=0
  SourcePackage: qemu
  UpgradeStatus: Upgraded to xenial on 2016-08-10 (627 days ago)
  dmi.bios.date: 03/30/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.8
  dmi.board.name: 0K068D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.8:bd03/30/2009:svnDellInc.:pnInspiron518:pvr00:rvnDellInc.:rn0K068D:rvrA00:cvnDellInc.:ct3:cvrOEM:
  dmi.product.name: Inspiron 518
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767857/+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 1831899] Re: Kernel Oops 3b in libc-2.23 unable to handle pointer dereference in kernel virtual address space

2019-08-14 Thread Juerg Haefliger
I started to take a look at the dumps and noticed that there are faults
in libc-2.17 (and not 2.23 as mentioned in the bug description). What
are you running in those docker images? Can you share some details about
what the machine was doing when it died?

-- 
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/1831899

Title:
  Kernel Oops 3b in libc-2.23 unable to handle pointer dereference in
  kernel virtual address space

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  New

Bug description:
  == Comment: #0 - Robert J. Brenneman  - 2019-05-30 
11:16:45 ==
  ---Problem Description---
  Kernel Oops 3b in libc-2.23 unable to handle pointer dereference in virtual 
kernel address space

  Contact Information = rjbr...@us.ibm.com

  ---uname output---
  Linux ECOS0018 4.15.0-50-generic #54-Ubuntu SMP Tue May 7 05:57:08 UTC 2019 
s390x s390x s390x GNU/Linux

  Machine Type = z13   2964 NE1

  ---System Hang---
   z/VM took a VMDUMP and reIPLed
  (the attached and available dumps are Linux dumps)

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   boot system, start jenkins, let it run a couple days

  Stack trace output:
   05/29/19 13:24:06  Call Trace:
  05/29/19 13:24:06  (?<0012b97a>? __tlb_remove_table+0x6a/0xd0)
  05/29/19 13:24:06   ?<0012ba34>? tlb_remove_table_rcu+0x54/0x70
  05/29/19 13:24:06   ?<001f43b4>? rcu_process_callbacks+0x1d4/0x570
  05/29/19 13:24:06   ?<008e92d4>? __do_softirq+0x124/0x358
  05/29/19 13:24:06   ?<00179d52>? irq_exit+0xba/0xd0
  05/29/19 13:24:06   ?<0010c412>? do_IRQ+0x8a/0xb8
  05/29/19 13:24:06   ?<008e87f0>? ext_int_handler+0x134/0x138
  05/29/19 13:24:06   ?<00102cee>? enabled_wait+0x4e/0xe0
  05/29/19 13:24:06  (?<1201>? 0x1201)
  05/29/19 13:24:06   ?<0010303a>? arch_cpu_idle+0x32/0x48
  05/29/19 13:24:06   ?<001c5ae8>? do_idle+0xe8/0x1a8

  Oops output:
   05/29/19 13:24:06  User process fault: interruption code 003b ilc:3 in 
libc-2.23.so?3ffaca0+185000?
  05/29/19 13:24:06  Failing address:  TEID: 0800
  05/29/19 13:24:06  Fault in primary space mode while using user ASCE.
  05/29/19 13:24:06  AS:000710b241c7 R3:0024
  05/29/19 13:24:06  Unable to handle kernel pointer dereference in virtual 
kernel address space
  05/29/19 13:24:06  Failing address: 03dbe000 TEID: 03dbe403
  05/29/19 13:24:06  Fault in home space mode while using kernel ASCE.
  05/29/19 13:24:06  AS:00ea8007 R3:0024
  05/29/19 13:24:06  Oops: 003b ilc:3 ?#1? SMP
  05/29/19 13:24:06  Modules linked in: veth xt_nat xt_tcpudp ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_con
  05/29/19 13:24:06   ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 
sha256_s390 dasd_fba_mod dasd_eckd_mod sha1_s390 sha_common dasd_mod
  05/29/19 13:24:06  CPU: 7 PID: 0 Comm: swapper/7 Not tainted 
4.15.0-50-generic #54-Ubuntu
  05/29/19 13:24:06  Hardware name: IBM 2964 NE1 798 (z/VM 6.4.0)
  05/29/19 13:24:06  Krnl PSW : dcb002be 72762961 
(__tlb_remove_table+0x56/0xd0)
  05/29/19 13:24:06 R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 
PM:0 RI:0 EA:3
  05/29/19 13:24:06  Krnl GPRS: ffba 02b8 
02b80003 00eacac8
  05/29/19 13:24:06 ffba 00b9 
0700 000a
  05/29/19 13:24:06 0404c001 0007d2fb5c38 
0007cf71fdf0 03dbe000
  05/29/19 13:24:06 03dbe018 008fe740 
0007cf71fd08 0007cf71fcd8
  05/29/19 13:24:06  Krnl Code: 0012b956: ec2c002a027f   clij
%r2,2,12,12b9aa
  05/29/19 13:24:06 0012b95c: ec26001d037e   cij 
%r2,3,6,12b996
  05/29/19 13:24:06#0012b962: 41c0b018   la  
%r12,24(%r11)
  05/29/19 13:24:06>0012b966: e548b008   mvghi   
8(%r11),0
  05/29/19 13:24:06 0012b96c: a7390008   lghi
%r3,8
  05/29/19 13:24:06 0012b970: b904002b   lgr 
%r2,%r11
  05/29/19 13:24:06 0012b974: c0e5000e8f8a   brasl   
%r14,2fd888
  05/29/19 13:24:06 0012b97a: a718   lhi 
%r1,-1
  05/29/19 13:24:06  Call Trace:
  05/29/19 13:24:06  (?<0012b97a>? __tlb_remove_table+0x6a/0xd0)
  05/29/19 13:24:06   ?<0012ba34>? tlb_remove_table_rcu+0x54/0x70
  05/29/19 13:24:06   ?<001f43b4>? rcu_process_callbacks+0x1d4/0x570
  05/29/19 13:24:06   ?<008e92d4>? __do_softirq+0x124/0x358
  05/29/1

[Kernel-packages] [Bug 1831899] Re: Kernel Oops 3b in libc-2.23 unable to handle pointer dereference in kernel virtual address space

2019-08-14 Thread Juerg Haefliger
Also, I'm not able to convert the VMDUMP. What am I missing?

$ vmconvert dump.190529.1324 
vmconvert: Input file 'dump.190529.1324' is not a vmdump

-- 
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/1831899

Title:
  Kernel Oops 3b in libc-2.23 unable to handle pointer dereference in
  kernel virtual address space

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  New

Bug description:
  == Comment: #0 - Robert J. Brenneman  - 2019-05-30 
11:16:45 ==
  ---Problem Description---
  Kernel Oops 3b in libc-2.23 unable to handle pointer dereference in virtual 
kernel address space

  Contact Information = rjbr...@us.ibm.com

  ---uname output---
  Linux ECOS0018 4.15.0-50-generic #54-Ubuntu SMP Tue May 7 05:57:08 UTC 2019 
s390x s390x s390x GNU/Linux

  Machine Type = z13   2964 NE1

  ---System Hang---
   z/VM took a VMDUMP and reIPLed
  (the attached and available dumps are Linux dumps)

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   boot system, start jenkins, let it run a couple days

  Stack trace output:
   05/29/19 13:24:06  Call Trace:
  05/29/19 13:24:06  (?<0012b97a>? __tlb_remove_table+0x6a/0xd0)
  05/29/19 13:24:06   ?<0012ba34>? tlb_remove_table_rcu+0x54/0x70
  05/29/19 13:24:06   ?<001f43b4>? rcu_process_callbacks+0x1d4/0x570
  05/29/19 13:24:06   ?<008e92d4>? __do_softirq+0x124/0x358
  05/29/19 13:24:06   ?<00179d52>? irq_exit+0xba/0xd0
  05/29/19 13:24:06   ?<0010c412>? do_IRQ+0x8a/0xb8
  05/29/19 13:24:06   ?<008e87f0>? ext_int_handler+0x134/0x138
  05/29/19 13:24:06   ?<00102cee>? enabled_wait+0x4e/0xe0
  05/29/19 13:24:06  (?<1201>? 0x1201)
  05/29/19 13:24:06   ?<0010303a>? arch_cpu_idle+0x32/0x48
  05/29/19 13:24:06   ?<001c5ae8>? do_idle+0xe8/0x1a8

  Oops output:
   05/29/19 13:24:06  User process fault: interruption code 003b ilc:3 in 
libc-2.23.so?3ffaca0+185000?
  05/29/19 13:24:06  Failing address:  TEID: 0800
  05/29/19 13:24:06  Fault in primary space mode while using user ASCE.
  05/29/19 13:24:06  AS:000710b241c7 R3:0024
  05/29/19 13:24:06  Unable to handle kernel pointer dereference in virtual 
kernel address space
  05/29/19 13:24:06  Failing address: 03dbe000 TEID: 03dbe403
  05/29/19 13:24:06  Fault in home space mode while using kernel ASCE.
  05/29/19 13:24:06  AS:00ea8007 R3:0024
  05/29/19 13:24:06  Oops: 003b ilc:3 ?#1? SMP
  05/29/19 13:24:06  Modules linked in: veth xt_nat xt_tcpudp ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_con
  05/29/19 13:24:06   ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 
sha256_s390 dasd_fba_mod dasd_eckd_mod sha1_s390 sha_common dasd_mod
  05/29/19 13:24:06  CPU: 7 PID: 0 Comm: swapper/7 Not tainted 
4.15.0-50-generic #54-Ubuntu
  05/29/19 13:24:06  Hardware name: IBM 2964 NE1 798 (z/VM 6.4.0)
  05/29/19 13:24:06  Krnl PSW : dcb002be 72762961 
(__tlb_remove_table+0x56/0xd0)
  05/29/19 13:24:06 R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 
PM:0 RI:0 EA:3
  05/29/19 13:24:06  Krnl GPRS: ffba 02b8 
02b80003 00eacac8
  05/29/19 13:24:06 ffba 00b9 
0700 000a
  05/29/19 13:24:06 0404c001 0007d2fb5c38 
0007cf71fdf0 03dbe000
  05/29/19 13:24:06 03dbe018 008fe740 
0007cf71fd08 0007cf71fcd8
  05/29/19 13:24:06  Krnl Code: 0012b956: ec2c002a027f   clij
%r2,2,12,12b9aa
  05/29/19 13:24:06 0012b95c: ec26001d037e   cij 
%r2,3,6,12b996
  05/29/19 13:24:06#0012b962: 41c0b018   la  
%r12,24(%r11)
  05/29/19 13:24:06>0012b966: e548b008   mvghi   
8(%r11),0
  05/29/19 13:24:06 0012b96c: a7390008   lghi
%r3,8
  05/29/19 13:24:06 0012b970: b904002b   lgr 
%r2,%r11
  05/29/19 13:24:06 0012b974: c0e5000e8f8a   brasl   
%r14,2fd888
  05/29/19 13:24:06 0012b97a: a718   lhi 
%r1,-1
  05/29/19 13:24:06  Call Trace:
  05/29/19 13:24:06  (?<0012b97a>? __tlb_remove_table+0x6a/0xd0)
  05/29/19 13:24:06   ?<0012ba34>? tlb_remove_table_rcu+0x54/0x70
  05/29/19 13:24:06   ?<001f43b4>? rcu_process_callbacks+0x1d4/0x570
  05/29/19 13:24:06   ?<008e92d4>? __do_softirq+0x124/0x358
  05/29/19 13:24:06   ?<00179d52>? irq_exit+0xba/0xd0
  05/29/19 13:24:06   ?<0010c412>? do_IRQ+0x8a

[Kernel-packages] [Bug 1839995] Re: bionic/linux-ibm-gt: 4.15.0-1032.34 -proposed tracker

2019-08-15 Thread Juerg Haefliger
** Summary changed:

- bionic/linux-ibm-gt:  -proposed tracker
+ bionic/linux-ibm-gt: 4.15.0-1032.34 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger 
(juergh)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger 
(juergh)

-- 
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/1839995

Title:
  bionic/linux-ibm-gt: 4.15.0-1032.34 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  kernel-stable-master-bug: 1840006
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Packaging
  phase-changed: Thursday, 15. August 2019 10:05 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839995/+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 1839995] Re: bionic/linux-ibm-gt: 4.15.0-1032.34 -proposed tracker

2019-08-15 Thread Juerg Haefliger
** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

-- 
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/1839995

Title:
  bionic/linux-ibm-gt: 4.15.0-1032.34 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  kernel-stable-master-bug: 1840006
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Packaging
  phase-changed: Thursday, 15. August 2019 10:05 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839995/+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 1839995] Re: bionic/linux-ibm-gt: 4.15.0-1032.34 -proposed tracker

2019-08-19 Thread Juerg Haefliger
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Invalid

-- 
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/1839995

Title:
  bionic/linux-ibm-gt: 4.15.0-1032.34 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1840006
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Ready for Promote to Proposed
  phase-changed: Monday, 19. August 2019 11:01 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839995/+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 1839277] Re: bionic/linux-ibm-gt: 4.15.0-1031.33 -proposed tracker

2019-08-19 Thread Juerg Haefliger
*** This bug is a duplicate of bug 1839995 ***
https://bugs.launchpad.net/bugs/1839995

** This bug has been marked a duplicate of bug 1839995
   bionic/linux-ibm-gt: 4.15.0-1032.34 -proposed tracker

-- 
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/1839277

Title:
  bionic/linux-ibm-gt: 4.15.0-1031.33 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1839293
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Complete
  phase-changed: Tuesday, 13. August 2019 11:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839277/+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 1839108] Re: bionic/linux-ibm-gt: 4.15.0-1030.32 -proposed tracker

2019-08-19 Thread Juerg Haefliger
*** This bug is a duplicate of bug 1839995 ***
https://bugs.launchpad.net/bugs/1839995

** This bug is no longer a duplicate of bug 1839277
   bionic/linux-ibm-gt: 4.15.0-1031.33 -proposed tracker
** This bug has been marked a duplicate of bug 1839995
   bionic/linux-ibm-gt: 4.15.0-1032.34 -proposed tracker

-- 
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/1839108

Title:
  bionic/linux-ibm-gt: 4.15.0-1030.32 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Ready for Testing
  phase-changed: Wednesday, 07. August 2019 07:48 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839108/+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 1840974] Re: bionic/linux-ibm-gt: 4.15.0-1033.35 -proposed tracker

2019-08-21 Thread Juerg Haefliger
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Invalid

-- 
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/1840974

Title:
  bionic/linux-ibm-gt: 4.15.0-1033.35 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1840006
  packages:
main: linux-ibm-gt
meta: linux-meta-ibm-gt
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 21. August 2019 23:07 UTC
  reason:
promote-to-proposed: Pending -- ready for review
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840974/+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 1812086] Re: kernel BUG at /build/linux-vxxS7y/linux-4.15.0/mm/slub.c:296!

2019-08-22 Thread Juerg Haefliger
That's a different stack trace and looks like a different problem that
just results in the kernel dying in the same place. And 4.18 is no
longer supported.

-- 
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/1812086

Title:
  kernel BUG at /build/linux-vxxS7y/linux-4.15.0/mm/slub.c:296!

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Justification ==

  Rebooting an iSCSI target while the initiator is writing to a LUN
  leads to the following trace:

  [   59.879202] [ cut here ]
  [   59.879202] kernel BUG at /build/linux-vxxS7y/linux-4.15.0/mm/slub.c:296!
  [   59.880636] invalid opcode:  [#1] SMP PTI
  [   59.881569] Modules linked in: iscsi_target_mod target_core_pscsi 
target_core_file target_core_iblock target_core_user uio target_core_mod 
nls_iso8859_1 kvm_intel isofs kvm irqbypass joydev input_leds serio_raw 
sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp 
libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear psmouse virtio_blk virtio_net 
floppy
  [   59.891096] CPU: 0 PID: 1027 Comm: iscsi_np Not tainted 4.15.0-43-generic 
#46-Ubuntu
  [   59.892726] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.11.1-1ubuntu1 04/01/2014
  [   59.894606] RIP: 0010:kfree+0x16a/0x180
  [   59.895429] RSP: 0018:ac0d8050fe58 EFLAGS: 00010246
  [   59.896531] RAX: 9cf099475800 RBX: 9cf099475800 RCX: 
9cf099475800
  [   59.898083] RDX: 00011bbb RSI: 9cf09fc27140 RDI: 
9cf09f002000
  [   59.899627] RBP: ac0d8050fe70 R08:  R09: 
c07a329b
  [   59.901186] R10: e95780651d40 R11: a511dc90 R12: 
9cf099625600
  [   59.902769] R13: c07a329b R14: 9cf09ee07600 R15: 
9cf099475800
  [   59.904321] FS:  () GS:9cf09fc0() 
knlGS:
  [   59.906120] CS:  0010 DS:  ES:  CR0: 80050033
  [   59.907806] CR2: 7f7153b88470 CR3: 1babe000 CR4: 
06f0
  [   59.909376] DR0:  DR1:  DR2: 

  [   59.910950] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   59.913098] Call Trace:
  [   59.913783]  iscsi_target_login_sess_out+0x1fb/0x250 [iscsi_target_mod]
  [   59.915292]  iscsi_target_login_thread+0x44d/0x1060 [iscsi_target_mod]
  [   59.916775]  kthread+0x121/0x140
  [   59.917622]  ? iscsi_target_login_sess_out+0x250/0x250 [iscsi_target_mod]
  [   59.919244]  ? kthread_create_worker_on_cpu+0x70/0x70
  [   59.920483]  ? do_syscall_64+0x73/0x130
  [   59.921460]  ? SyS_exit_group+0x14/0x20
  [   59.922583]  ret_from_fork+0x35/0x40
  [   59.923523] Code: c4 80 74 04 41 8b 72 6c 4c 89 d7 e8 61 1c f9 ff eb 86 41 
b8 01 00 00 00 48 89 d9 48 89 da 4c 89 d6 e8 8b f6 ff ff e9 6d ff ff ff <0f> 0b 
48 8b 3d 6d c4 1c 01 e9 c9 fe ff ff 0f 1f 84 00 00 00 00
  [   59.927778] RIP: kfree+0x16a/0x180 RSP: ac0d8050fe58
  [   59.929063] ---[ end trace 082da4d341633d3e ]---

  == Fix ==

  Backport the following 3 commits:
   * scsi: iscsi: target: Fix conn_ops double free
   * scsi: iscsi: target: Set conn->sess to NULL when
     iscsi_login_set_conn_values fails
   * iscsi target: fix session creation failure handling

  == Regression Potential ==

  Low. Clean cherry-picks that modify a very isolated area.

  == Test ==

  Setup an iSCSI target using the scsi_target_user module and
  tcmu_runner. Setup an initiator to connect to the target and do IOs.
  Reboot the target. When the target comes back, the kernel falls over
  when the initiator tries to re-connect.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812086/+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 1831899] Re: Kernel Oops 3b in libc-2.23 unable to handle pointer dereference in kernel virtual address space

2019-08-28 Thread Juerg Haefliger
Is this easily reproducible? Can you retry with the latest released
kernel 4.15.0-58.64? I haven't been able to reproduce the problem
locally so far. It would help if you could share the container and
workload, if that's possible at all. I'm still looking through the
dumpfiles but haven't made much progress yet towards finding the root
cause.

-- 
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/1831899

Title:
  Kernel Oops 3b in libc-2.23 unable to handle pointer dereference in
  kernel virtual address space

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  New
Status in linux source package in Bionic:
  New

Bug description:
  == Comment: #0 - Robert J. Brenneman  - 2019-05-30 
11:16:45 ==
  ---Problem Description---
  Kernel Oops 3b in libc-2.23 unable to handle pointer dereference in virtual 
kernel address space

  Contact Information = rjbr...@us.ibm.com

  ---uname output---
  Linux ECOS0018 4.15.0-50-generic #54-Ubuntu SMP Tue May 7 05:57:08 UTC 2019 
s390x s390x s390x GNU/Linux

  Machine Type = z13   2964 NE1

  ---System Hang---
   z/VM took a VMDUMP and reIPLed
  (the attached and available dumps are Linux dumps)

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   boot system, start jenkins, let it run a couple days

  Stack trace output:
   05/29/19 13:24:06  Call Trace:
  05/29/19 13:24:06  (?<0012b97a>? __tlb_remove_table+0x6a/0xd0)
  05/29/19 13:24:06   ?<0012ba34>? tlb_remove_table_rcu+0x54/0x70
  05/29/19 13:24:06   ?<001f43b4>? rcu_process_callbacks+0x1d4/0x570
  05/29/19 13:24:06   ?<008e92d4>? __do_softirq+0x124/0x358
  05/29/19 13:24:06   ?<00179d52>? irq_exit+0xba/0xd0
  05/29/19 13:24:06   ?<0010c412>? do_IRQ+0x8a/0xb8
  05/29/19 13:24:06   ?<008e87f0>? ext_int_handler+0x134/0x138
  05/29/19 13:24:06   ?<00102cee>? enabled_wait+0x4e/0xe0
  05/29/19 13:24:06  (?<1201>? 0x1201)
  05/29/19 13:24:06   ?<0010303a>? arch_cpu_idle+0x32/0x48
  05/29/19 13:24:06   ?<001c5ae8>? do_idle+0xe8/0x1a8

  Oops output:
   05/29/19 13:24:06  User process fault: interruption code 003b ilc:3 in 
libc-2.23.so?3ffaca0+185000?
  05/29/19 13:24:06  Failing address:  TEID: 0800
  05/29/19 13:24:06  Fault in primary space mode while using user ASCE.
  05/29/19 13:24:06  AS:000710b241c7 R3:0024
  05/29/19 13:24:06  Unable to handle kernel pointer dereference in virtual 
kernel address space
  05/29/19 13:24:06  Failing address: 03dbe000 TEID: 03dbe403
  05/29/19 13:24:06  Fault in home space mode while using kernel ASCE.
  05/29/19 13:24:06  AS:00ea8007 R3:0024
  05/29/19 13:24:06  Oops: 003b ilc:3 ?#1? SMP
  05/29/19 13:24:06  Modules linked in: veth xt_nat xt_tcpudp ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_con
  05/29/19 13:24:06   ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 
sha256_s390 dasd_fba_mod dasd_eckd_mod sha1_s390 sha_common dasd_mod
  05/29/19 13:24:06  CPU: 7 PID: 0 Comm: swapper/7 Not tainted 
4.15.0-50-generic #54-Ubuntu
  05/29/19 13:24:06  Hardware name: IBM 2964 NE1 798 (z/VM 6.4.0)
  05/29/19 13:24:06  Krnl PSW : dcb002be 72762961 
(__tlb_remove_table+0x56/0xd0)
  05/29/19 13:24:06 R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:1 
PM:0 RI:0 EA:3
  05/29/19 13:24:06  Krnl GPRS: ffba 02b8 
02b80003 00eacac8
  05/29/19 13:24:06 ffba 00b9 
0700 000a
  05/29/19 13:24:06 0404c001 0007d2fb5c38 
0007cf71fdf0 03dbe000
  05/29/19 13:24:06 03dbe018 008fe740 
0007cf71fd08 0007cf71fcd8
  05/29/19 13:24:06  Krnl Code: 0012b956: ec2c002a027f   clij
%r2,2,12,12b9aa
  05/29/19 13:24:06 0012b95c: ec26001d037e   cij 
%r2,3,6,12b996
  05/29/19 13:24:06#0012b962: 41c0b018   la  
%r12,24(%r11)
  05/29/19 13:24:06>0012b966: e548b008   mvghi   
8(%r11),0
  05/29/19 13:24:06 0012b96c: a7390008   lghi
%r3,8
  05/29/19 13:24:06 0012b970: b904002b   lgr 
%r2,%r11
  05/29/19 13:24:06 0012b974: c0e5000e8f8a   brasl   
%r14,2fd888
  05/29/19 13:24:06 0012b97a: a718   lhi 
%r1,-1
  05/29/19 13:24:06  Call Trace:
  05/29/19 13:24:06  (?<0012b97a>? __tlb_remove_table+0x6a/0xd0)
  05/29/19 13:24:06   ?<0012ba34>? tlb_remove_table_rcu+0x54/0x70
  05/29/19 13:24:06   ?<001f43b4>? rcu_process_callba

[Kernel-packages] [Bug 1822870] Re: Backport support for software count cache flush Spectre v2 mitigation. (CVE) (required for POWER9 DD2.3)

2019-09-02 Thread Juerg Haefliger
The Disco kernel is missing:
2b57ecd0208f ("KVM: PPC: Book3S: Add count cache flush parameters to 
kvmppc_get_cpu_char()")

-- 
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/1822870

Title:
  Backport support for software count cache flush Spectre v2 mitigation.
  (CVE) (required for POWER9 DD2.3)

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  [IMPACT]
  Need to further address the Spectre v2 and Meltdown vulnerability in Power 
with software count cache flush Spectre v2 mitigation support for Power9 DD2.3, 
and additional Spectre/Meltdown related patches for Power9.

  [Fix]
  List of upstream patches identified by IBM in comment #4, #5, and #8.

  [Test]
  Pre-req: requires Power9 DD2.3 hardware.
  A test kernel is available in PPA ppa:ubuntu-power-triage/lp1822870 and the 
kernel was tested by IBM. Please see comment #11 and #14 for details.

  [REGRESSION POTENTIAL]
  The patches are isolated to the ppc64el architecture and does not impact 
generic code. ppc64el test kernel was tested by IBM and no regressions were 
reported.

  [OTHER INFO]
  For the different kernels:

  The HWE a563fd9c62f0 UBUNTU: Ubuntu-hwe-4.18.0-17.18~18.04.1 appears
  to have all patches.

  Disco appears to be missing only this patch:
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting

  Cosmic (which is supported until July) is missing a number of patches:
  cf175dc315f90185128fb061dc05b6fbb211aa2f powerpc/64: Disable the speculation 
barrier from the command line
  6453b532f2c8856a80381e6b9a1f5ea2f12294df powerpc/64: Make stf barrier 
PPC_BOOK3S_64 specific.
  179ab1cbf883575c3a585bcfc0f2160f1d22a149 powerpc/64: Add 
CONFIG_PPC_BARRIER_NOSPEC
  af375eefbfb27cbb5b831984e66d724a40d26b5c powerpc/64: Call 
setup_barrier_nospec() from setup_arch()
  406d2b6ae3420f5bb2b3db6986dc6f0b6dbb637b powerpc/64: Make meltdown reporting 
Book3S 64 specific
  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  dc8c6cce9a26a51fc19961accb978217a3ba8c75 powerpc/64s: Add new security 
feature flags for count cache flush
  ee13cb249fabdff8b90aaff61add347749280087 powerpc/64s: Add support for 
software count cache flush
  ba72dc171954b782a79d25e0f4b3ed91090c3b1e powerpc/pseries: Query hypervisor 
for count cache flush settings
  99d54754d3d5f896a8f616b0b6520662bc99d66b powerpc/powernv: Query firmware for 
count cache flush settings
  7d8bad99ba5a22892f0cad6881289fdc3875a930 powerpc/fsl: Fix spectre_v2 
mitigations reporting
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting
  This appears to already be in -next.

  For the bionic 18.04.1 (4.15) kernel only this patch is already part of 
master-next:
  a6b3964ad71a61bb7c61d80a60bea7d42187b2eb powerpc/64s: Add barrier_nospec

  The others are ported, there were only 3 that were not clean.  Those are:
  2eea7f067f495e33b8b116b35b5988ab2b8aec55 powerpc/64s: Add support for ori 
barrier_nospec patching
  This failed because commit a048a07d7f4535baa4cbad6bc024f175317ab938 is 
missing, but it does not look like that is required here.

  cb3d6759a93c6d0aea1c10deb6d00e111c29c19c powerpc/64s: Enable barrier_nospec 
based on firmware settings
  This failed because debugfs was already included, I can see that previously 
added, I didn't see where it was previously removed.

  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  This failed because 8183d99f4a22c is not included - but doesn't seem 
necessary.

  All other patches applied with, at most, some fuzz.

  Has had a little testing - boots, check debugfs, etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1822870/+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 1822870] Re: Backport support for software count cache flush Spectre v2 mitigation. (CVE) (required for POWER9 DD2.3)

2019-09-02 Thread Juerg Haefliger
** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
   Status: New

-- 
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/1822870

Title:
  Backport support for software count cache flush Spectre v2 mitigation.
  (CVE) (required for POWER9 DD2.3)

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  New

Bug description:
  [IMPACT]
  Need to further address the Spectre v2 and Meltdown vulnerability in Power 
with software count cache flush Spectre v2 mitigation support for Power9 DD2.3, 
and additional Spectre/Meltdown related patches for Power9.

  [Fix]
  List of upstream patches identified by IBM in comment #4, #5, and #8.

  [Test]
  Pre-req: requires Power9 DD2.3 hardware.
  A test kernel is available in PPA ppa:ubuntu-power-triage/lp1822870 and the 
kernel was tested by IBM. Please see comment #11 and #14 for details.

  [REGRESSION POTENTIAL]
  The patches are isolated to the ppc64el architecture and does not impact 
generic code. ppc64el test kernel was tested by IBM and no regressions were 
reported.

  [OTHER INFO]
  For the different kernels:

  The HWE a563fd9c62f0 UBUNTU: Ubuntu-hwe-4.18.0-17.18~18.04.1 appears
  to have all patches.

  Disco appears to be missing only this patch:
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting

  Cosmic (which is supported until July) is missing a number of patches:
  cf175dc315f90185128fb061dc05b6fbb211aa2f powerpc/64: Disable the speculation 
barrier from the command line
  6453b532f2c8856a80381e6b9a1f5ea2f12294df powerpc/64: Make stf barrier 
PPC_BOOK3S_64 specific.
  179ab1cbf883575c3a585bcfc0f2160f1d22a149 powerpc/64: Add 
CONFIG_PPC_BARRIER_NOSPEC
  af375eefbfb27cbb5b831984e66d724a40d26b5c powerpc/64: Call 
setup_barrier_nospec() from setup_arch()
  406d2b6ae3420f5bb2b3db6986dc6f0b6dbb637b powerpc/64: Make meltdown reporting 
Book3S 64 specific
  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  dc8c6cce9a26a51fc19961accb978217a3ba8c75 powerpc/64s: Add new security 
feature flags for count cache flush
  ee13cb249fabdff8b90aaff61add347749280087 powerpc/64s: Add support for 
software count cache flush
  ba72dc171954b782a79d25e0f4b3ed91090c3b1e powerpc/pseries: Query hypervisor 
for count cache flush settings
  99d54754d3d5f896a8f616b0b6520662bc99d66b powerpc/powernv: Query firmware for 
count cache flush settings
  7d8bad99ba5a22892f0cad6881289fdc3875a930 powerpc/fsl: Fix spectre_v2 
mitigations reporting
  92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 
reporting
  This appears to already be in -next.

  For the bionic 18.04.1 (4.15) kernel only this patch is already part of 
master-next:
  a6b3964ad71a61bb7c61d80a60bea7d42187b2eb powerpc/64s: Add barrier_nospec

  The others are ported, there were only 3 that were not clean.  Those are:
  2eea7f067f495e33b8b116b35b5988ab2b8aec55 powerpc/64s: Add support for ori 
barrier_nospec patching
  This failed because commit a048a07d7f4535baa4cbad6bc024f175317ab938 is 
missing, but it does not look like that is required here.

  cb3d6759a93c6d0aea1c10deb6d00e111c29c19c powerpc/64s: Enable barrier_nospec 
based on firmware settings
  This failed because debugfs was already included, I can see that previously 
added, I didn't see where it was previously removed.

  06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro 
& helpers for patching instructions
  This failed because 8183d99f4a22c is not included - but doesn't seem 
necessary.

  All other patches applied with, at most, some fuzz.

  Has had a little testing - boots, check debugfs, etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1822870/+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 1832622] Re: QEMU - count cache flush Spectre v2 mitigation (CVE) (required for POWER9 DD2.3)

2019-09-02 Thread Juerg Haefliger
Confirmed that the Disco kernel is only missing 2b57ecd0208f ("KVM: PPC:
Book3S: Add count cache flush parameters to kvmppc_get_cpu_char()") from
the patchset referenced in bug 1822870.

-- 
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/1832622

Title:
  QEMU -  count cache flush Spectre v2 mitigation (CVE) (required for
  POWER9 DD2.3)

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released
Status in qemu source package in Xenial:
  Won't Fix
Status in linux source package in Bionic:
  Fix Released
Status in qemu source package in Bionic:
  Fix Committed
Status in qemu source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Confirmed
Status in qemu source package in Disco:
  Fix Committed
Status in qemu source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * This belongs to the overall context of spectre mitigations and even 
 more the try to minimize the related performance impacts.
 On ppc64el there is a new chip revision (DD 2.3) which provides
 a facility that helps to better mitigate some of this.

   * Backport the patches that will make the feature (if supported by the 
 HW) will pass the capability to the guest - to allow guests that 
 support the improved mitigation to use it.

  [Test Case]

   * Start guests with and without this capability
 * Check if the capability is guest visible as intented
 * Check if there are any issues on pre DD2.3 HW
   * Test migrations (IBM outlined the intented paths that will work 
 below)
   * The problem with the above (and also the reasons I didn't add a list 
 of commands this time) is that it needs special HW (mentioned DD2.3 
 revision) of the chips which aren't available to us right now.
 Due to that testing / verification of this on all releases is on IBM

  [Regression Potential]

   * Adding new capabilities usually works fine, there are three common 
 pitfalls which here are the regression potential.
 - (severe) the code would announce a capability that isn't really 
   available. The guest tries to use it and crashes
 - (medium) several migration paths especially from systems with the 
   new cap to older (un-updated systems) will fail. But that applies 
   to any "from machine with Feature to machine without that feature" 
   and isn't really a new regression. As outlined by IBM below they 
   even tried to make it somewhat compatible (by being a new value in 
   an existing cap)
 - (low) the guest will see new caps and or facilities. A really odd
   guest could stumble due to that (would actually be a guest bug 
   then)
Overall all of the above was considered by IBM when developing this 
and should be ok. For archive wide SRU considerations, this has NO 
effect on non ppc64el.

  [Other Info]
   
   * n/a

  ---

  Power9 DD 2.3  CPUs  running updated firmware will use a new Spectre
  v2 mitigation. The new mitigation improves performance of branch heavy
  workloads, but also requires kernel support in order to be fully
  secure.

  Without the kernel support there is a risk of a Spectre v2 attack
  across a process context switch, though it has not been demonstrated
  in practice.

  QEMU portion - platform definition needs to account for this new
  mitigation action.. so attribute for this needs to be added.

  In terms of support for virtualisation there are 2 sides, kvm and qemu
  support. Patch list for each,

  KVM:
  2b57ecd0208f KVM: PPC: Book3S: Add count cache flush parameters to 
kvmppc_get_cpu_char()
  This is part of LP1822870 already.

  QEMU:
  8ff43ee404 target/ppc/spapr: Add SPAPR_CAP_CCF_ASSIST
  399b2896d4 target/ppc/spapr: Add workaround option to SPAPR_CAP_IBS

  The KVM side is upstream as of v5.1-rc1.
  The QEMU side is upstream as of v4.0.0-rc0.

  In terms of migration the state is as follows.

  In order to specify to the guest to use the count cache flush
  workaround we use the spapr-cap cap-ibs (indirect branch speculation)
  with the value workaround. Previously the only valid values were
  broken, fixed-ibs (indirect branch serialisation) and fixed-ccd (count
  cache disabled). And add a new cap cap-ccf-assist (count cache flush
  assist) to specify the availability of the hardware assisted flush
  variant.

  Note the the way spapr caps work you can migrate to a host that supports a 
higher value, but not to one which doesn't support the current value (i.e. only 
supports lower values). Where for cap-ibs these are defined as:
  0 - Broken
  1 - Workaround
  2 - fixed-ibs
  3 - fixed-ccd

  So the following migrations would be valid for example:
  broken -> fixed-ccd, broken -> workaround, workaround -> fixed-ccd

  While the following would be invalid:
  fixed-ccd -> work

[Kernel-packages] [Bug 1822760] Re: Bionic: Sync to Xenial (Spectre)

2019-05-08 Thread Juerg Haefliger
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

-- 
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/1822760

Title:
  Bionic: Sync to Xenial (Spectre)

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification ==

  There are a couple of Spectre related commits in Xenial that never
  landed in Bionic. Fix that to prevent a regression when upgrading from
  Xenial to Bionic.

  == Regression Potential ==

  Low. These are not very intrusive commits that have been in upstream
  for quite a while.

  == Fix ==

  Backport the relevant commits from upstream.

  == Test Case ==

  TBD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822760/+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 1820872] Re: Xenial: Sync to upstream v4.9 (Spectre)

2019-05-08 Thread Juerg Haefliger
** Tags removed: verification-needed-xenial
** Tags added: verification-done-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/1820872

Title:
  Xenial: Sync to upstream v4.9 (Spectre)

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  == SRU Justification ==

  Reduce the delta between Xenial 4.4 and upstream stable 4.9 in the
  Spectre-related areas.

  == Regression Potential ==

  Low. These are cosmetic cleanups (non-functional changes) and
  backports of low-risk commits that have been in upstream stable for
  quite a while already.

  == Fix ==

  Backport the relevant commits.

  == Test Case ==

  TBD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820872/+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 1828350] [NEW] Add support for Intel I210 NIC

2019-05-09 Thread Juerg Haefliger
Private bug reported:

== SRU Justification ==

The Precise 3.2 kernel doesn't support the Intel I210 NIC. It's a fairly
old and common NIC which is also in my test system. It would help with
testing Precise if that NIC was supported.

== Fix ==

Backport the following 3 commits wich add I210 support:
  - igb: Fix incorrect RAR address entries for i210/i211 device.
  - igb: Add Support for new i210/i211 devices.
  - igb: Add function and pointers for 82580 low power state settings.

== Regression Potential ==

Low. This is mostly new code that is only exercised when an I210 NIC is
present. There is some shuffling around and the introduction of low
power settings handling for other NIC types as well so there is some
risk. But it's isolated to the igb NIC driver.

== Test Case ==

Boot a patched kernel and verify the NIC is recognized and the network
comes up.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Precise)
 Importance: Undecided
 Status: Confirmed

** Also affects: linux (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Precise)
   Status: New => Confirmed

** Information type changed from Public to Private

** Information type changed from Private to Private Security

** Information type changed from Private Security to Private

** Information type changed from Private to Public

** Information type changed from Public to Private

-- 
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/1828350

Title:
  Add support for Intel I210 NIC

Status in linux package in Ubuntu:
  New
Status in linux source package in Precise:
  Confirmed

Bug description:
  == SRU Justification ==

  The Precise 3.2 kernel doesn't support the Intel I210 NIC. It's a
  fairly old and common NIC which is also in my test system. It would
  help with testing Precise if that NIC was supported.

  == Fix ==

  Backport the following 3 commits wich add I210 support:
- igb: Fix incorrect RAR address entries for i210/i211 device.
- igb: Add Support for new i210/i211 devices.
- igb: Add function and pointers for 82580 low power state settings.

  == Regression Potential ==

  Low. This is mostly new code that is only exercised when an I210 NIC
  is present. There is some shuffling around and the introduction of low
  power settings handling for other NIC types as well so there is some
  risk. But it's isolated to the igb NIC driver.

  == Test Case ==

  Boot a patched kernel and verify the NIC is recognized and the network
  comes up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828350/+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 1788098] Re: Avoid migration issues with aligned 2MB THB

2019-05-10 Thread Juerg Haefliger
Leonardo, can you elaborate on the 'other possible issues'? We're
hesitant to pull 18 patches into a stable kernel under the assumption
that they *might* fix some *potential* issues, without clear evidence.
If you can test the single-patch kernel and report back that there are
still issues then that's a much stronger case for the other patches.

Commit 'KVM: PPC: Book3S HV: Avoid crash from THP collapse during radix
page fault' that you're asking for requires all these additional
backports to apply cleanly. Which makes me wonder if we're not actually
introducing a problem with these backports just to fix it again later.
Not saying that's the case, just wondering...

Also, the following seem to be totally unrelated and unnecessary:
  - KVM: PPC: Remove unused kvm_unmap_hva callback
  - powerpc/mm/radix: Remove unused code

While looking through the patches I also noticed that the following is the 
second patch of a series of 11 but it's the only one from the series that 
you're backporting.
  - powerpc/kvm: Switch kvm pmd allocator to custom allocator
Its commit message mentions subsequent patches of that series so I'm wondering 
why we need/want only this single patch??

Remember that we have to support this kernel for years and years to come
so we only want to backport the absolute necessary.

Lastly and FYI, the following is the minimal subset of your patches that all 
cherry-pick cleanly:
  - KVM: PPC: Book3S HV: Avoid crash from THP collapse during radix page fault
  - KVM: PPC: Book3S HV: Don't use compound_order to determine host mapping size
  - KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()
  - KVM: PPC: Book3S HV: radix: Refine IO region partition scope attributes
  - KVM: PPC: Book3S HV: Use __gfn_to_pfn_memslot() in page fault handler
  - KVM: PPC: Book3S HV: Handle 1GB pages in radix page fault handler
  - KVM: PPC: Book3S HV: Streamline setting of reference and change bits
  - KVM: PPC: Book3S HV: Radix page fault handler optimizations

Please provide some context why we need all the above (and potentially
more).

-- 
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/1788098

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next&id=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+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 1828632] Re: bionic i386 kernel crashes in memory pressure situations

2019-05-13 Thread Juerg Haefliger
** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Juerg Haefliger (juergh)

-- 
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/1828632

Title:
  bionic i386 kernel crashes in memory pressure situations

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  New

Bug description:
  The linux-image-4.15.0-49-generic (currently in bionic-proposed) can
  be made to crash in a kvm guest with memory pressure. The reproducer
  used is to attempt to run netbeans with openjdk-8-jre installed as the
  only jvm. It will fail to run, and when it fails, it also causes
  gnome-shell to crash. After 3 to 5 repeats of this, the kernel will
  crash with the following oops in dmesg:

  [  545.926175] rfkill: input handler enabled
  [  546.117550] [ cut here ]
  [  546.117552] kernel BUG at 
/build/linux-S9wgEU/linux-4.15.0/arch/x86/mm/fault.c:268!
  [  546.117564] invalid opcode:  [#1] SMP PTI
  [  546.117565] Modules linked in: snd_hda_codec_generic snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep snd_pcm kvm_intel kvm snd_seq_midi 
snd_seq_midi_e
  vent snd_rawmidi irqbypass snd_seq snd_seq_device input_leds joydev snd_timer 
serio_raw snd soundcore qemu_fw_cfg mac_hid binfmt_misc sch_fq_codel ib_iser r
  dma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 
btrfs zstd_compress r
  aid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid crc32_pc
  lmul pcbc qxl ttm drm_kms_helper syscopyarea aesni_intel aes_i586 sysfillrect 
sysimgblt crypto_simd cryptd fb_sys_fops psmouse virtio_blk virtio_net floppy
  drm pata_acpi i2c_piix4
  [  546.117600] CPU: 0 PID: 1335 Comm: Xorg Not tainted 4.15.0-49-generic 
#53-Ubuntu
  [  546.117600] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [  546.117618] EIP: vmalloc_fault+0x229/0x240
  [  546.117618] EFLAGS: 00010086 CPU: 0
  [  546.117619] EAX: 026c EBX: c3e20c50 ECX: f8eb EDX: 
  [  546.117620] ESI: f140 EDI: f800 EBP: eddc1934 ESP: eddc1918
  [  546.117621]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [  546.117621] CR0: 80050033 CR2: f140 CR3: 25f16000 CR4: 001406f0
  [  546.117624] Call Trace:
  [  546.117637]  ? kvm_async_pf_task_wait+0x1b0/0x1b0
  [  546.117638]  __do_page_fault+0x39d/0x510
  [  546.117640]  ? kvm_async_pf_task_wait+0x1b0/0x1b0
  [  546.117641]  do_page_fault+0x27/0xf0
  [  546.117644]  ? kvm_async_pf_task_wait+0x1b0/0x1b0
  [  546.117645]  do_async_page_fault+0x55/0x90
  [  546.117655]  common_exception+0x130/0x136
  [  546.117659] EIP: qxl_image_init+0x338/0x390 [qxl]
  [  546.117659] EFLAGS: 00010286 CPU: 0
  [  546.117660] EAX: fffbb000 EBX: 0fec ECX: fffbb014 EDX: 0030
  [  546.117661] ESI: f140 EDI: fffbb018 EBP: eddc1a18 ESP: eddc19e4
  [  546.117661]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [  546.117663]  ? ioremap_nocache+0x12/0x20
  [  546.117665]  qxl_draw_dirty_fb+0x1cd/0x3d0 [qxl]
  [  546.117668]  qxl_primary_atomic_update+0x159/0x2c0 [qxl]
  [  546.117680]  drm_atomic_helper_commit_planes+0xe8/0x240 [drm_kms_helper]
  [  546.117684]  drm_atomic_helper_commit_tail+0x23/0x50 [drm_kms_helper]
  [  546.117688]  commit_tail+0x5d/0x60 [drm_kms_helper]
  [  546.117691]  drm_atomic_helper_commit+0xf7/0x100 [drm_kms_helper]
  [  546.117695]  ? drm_atomic_helper_setup_commit+0x3f0/0x3f0 [drm_kms_helper]
  [  546.117715]  drm_atomic_commit+0x3f/0x50 [drm]
  [  546.117719]  restore_fbdev_mode_atomic+0x16b/0x1c0 [drm_kms_helper]
  [  546.117723]  restore_fbdev_mode+0x2c/0x150 [drm_kms_helper]
  [  546.117725]  ? _cond_resched+0x17/0x40
  [  546.117729]  drm_fb_helper_restore_fbdev_mode_unlocked.part.32+0x21/0x70 
[drm_kms_helper]
  [  546.117732]  drm_fb_helper_set_par+0x45/0x80 [drm_kms_helper]
  [  546.117743]  fb_set_var+0x1a9/0x440
  [  546.117750]  ? wakeup_preempt_entity+0x73/0x80
  [  546.117752]  ? check_preempt_wakeup+0x108/0x230
  [  546.117753]  ? check_cfs_rq_runtime+0x70/0x70
  [  546.117755]  ? check_preempt_curr+0x27/0x80
  [  546.117757]  ? ttwu_do_wakeup+0x17/0x190
  [  546.117760]  fbcon_blank+0x29e/0x370
  [  546.117772]  ? __switch_to_asm+0x27/0x4c
  [  546.117774]  ? fbcon_cursor+0x1b0/0x1b0
  [  546.117782]  do_unblank_screen+0xaa/0x1b0
  [  546.117784]  vt_ioctl+0x4e3/0x11e0
  [  546.117786]  ? complete_change_console+0xe0/0xe0
  [  546.117788]  tty_ioctl+0xec/0x910
  [  546.117793]  ? jbd2_journal_stop+0xd7/0x3e0
  [  546.117797]  ? ext4_free_inode+0x3c7/0x560
  [  546.117798]  ? ext4_free_inode+0x1f2/0x560
  [  546.117812]  ? intel_pmu_lbr_init_atom+0x46/0x50
  [  546.117819]  ? call_rcu_sched+0

[Kernel-packages] [Bug 1828632] Re: bionic i386 kernel crashes in memory pressure situations

2019-05-13 Thread Juerg Haefliger
I'm unable to reproduce this issue. Can you share your libvirt domain
xml? And what version of netbeans are you using?

-- 
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/1828632

Title:
  bionic i386 kernel crashes in memory pressure situations

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  New

Bug description:
  The linux-image-4.15.0-49-generic (currently in bionic-proposed) can
  be made to crash in a kvm guest with memory pressure. The reproducer
  used is to attempt to run netbeans with openjdk-8-jre installed as the
  only jvm. It will fail to run, and when it fails, it also causes
  gnome-shell to crash. After 3 to 5 repeats of this, the kernel will
  crash with the following oops in dmesg:

  [  545.926175] rfkill: input handler enabled
  [  546.117550] [ cut here ]
  [  546.117552] kernel BUG at 
/build/linux-S9wgEU/linux-4.15.0/arch/x86/mm/fault.c:268!
  [  546.117564] invalid opcode:  [#1] SMP PTI
  [  546.117565] Modules linked in: snd_hda_codec_generic snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep snd_pcm kvm_intel kvm snd_seq_midi 
snd_seq_midi_e
  vent snd_rawmidi irqbypass snd_seq snd_seq_device input_leds joydev snd_timer 
serio_raw snd soundcore qemu_fw_cfg mac_hid binfmt_misc sch_fq_codel ib_iser r
  dma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 
btrfs zstd_compress r
  aid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid crc32_pc
  lmul pcbc qxl ttm drm_kms_helper syscopyarea aesni_intel aes_i586 sysfillrect 
sysimgblt crypto_simd cryptd fb_sys_fops psmouse virtio_blk virtio_net floppy
  drm pata_acpi i2c_piix4
  [  546.117600] CPU: 0 PID: 1335 Comm: Xorg Not tainted 4.15.0-49-generic 
#53-Ubuntu
  [  546.117600] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [  546.117618] EIP: vmalloc_fault+0x229/0x240
  [  546.117618] EFLAGS: 00010086 CPU: 0
  [  546.117619] EAX: 026c EBX: c3e20c50 ECX: f8eb EDX: 
  [  546.117620] ESI: f140 EDI: f800 EBP: eddc1934 ESP: eddc1918
  [  546.117621]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [  546.117621] CR0: 80050033 CR2: f140 CR3: 25f16000 CR4: 001406f0
  [  546.117624] Call Trace:
  [  546.117637]  ? kvm_async_pf_task_wait+0x1b0/0x1b0
  [  546.117638]  __do_page_fault+0x39d/0x510
  [  546.117640]  ? kvm_async_pf_task_wait+0x1b0/0x1b0
  [  546.117641]  do_page_fault+0x27/0xf0
  [  546.117644]  ? kvm_async_pf_task_wait+0x1b0/0x1b0
  [  546.117645]  do_async_page_fault+0x55/0x90
  [  546.117655]  common_exception+0x130/0x136
  [  546.117659] EIP: qxl_image_init+0x338/0x390 [qxl]
  [  546.117659] EFLAGS: 00010286 CPU: 0
  [  546.117660] EAX: fffbb000 EBX: 0fec ECX: fffbb014 EDX: 0030
  [  546.117661] ESI: f140 EDI: fffbb018 EBP: eddc1a18 ESP: eddc19e4
  [  546.117661]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [  546.117663]  ? ioremap_nocache+0x12/0x20
  [  546.117665]  qxl_draw_dirty_fb+0x1cd/0x3d0 [qxl]
  [  546.117668]  qxl_primary_atomic_update+0x159/0x2c0 [qxl]
  [  546.117680]  drm_atomic_helper_commit_planes+0xe8/0x240 [drm_kms_helper]
  [  546.117684]  drm_atomic_helper_commit_tail+0x23/0x50 [drm_kms_helper]
  [  546.117688]  commit_tail+0x5d/0x60 [drm_kms_helper]
  [  546.117691]  drm_atomic_helper_commit+0xf7/0x100 [drm_kms_helper]
  [  546.117695]  ? drm_atomic_helper_setup_commit+0x3f0/0x3f0 [drm_kms_helper]
  [  546.117715]  drm_atomic_commit+0x3f/0x50 [drm]
  [  546.117719]  restore_fbdev_mode_atomic+0x16b/0x1c0 [drm_kms_helper]
  [  546.117723]  restore_fbdev_mode+0x2c/0x150 [drm_kms_helper]
  [  546.117725]  ? _cond_resched+0x17/0x40
  [  546.117729]  drm_fb_helper_restore_fbdev_mode_unlocked.part.32+0x21/0x70 
[drm_kms_helper]
  [  546.117732]  drm_fb_helper_set_par+0x45/0x80 [drm_kms_helper]
  [  546.117743]  fb_set_var+0x1a9/0x440
  [  546.117750]  ? wakeup_preempt_entity+0x73/0x80
  [  546.117752]  ? check_preempt_wakeup+0x108/0x230
  [  546.117753]  ? check_cfs_rq_runtime+0x70/0x70
  [  546.117755]  ? check_preempt_curr+0x27/0x80
  [  546.117757]  ? ttwu_do_wakeup+0x17/0x190
  [  546.117760]  fbcon_blank+0x29e/0x370
  [  546.117772]  ? __switch_to_asm+0x27/0x4c
  [  546.117774]  ? fbcon_cursor+0x1b0/0x1b0
  [  546.117782]  do_unblank_screen+0xaa/0x1b0
  [  546.117784]  vt_ioctl+0x4e3/0x11e0
  [  546.117786]  ? complete_change_console+0xe0/0xe0
  [  546.117788]  tty_ioctl+0xec/0x910
  [  546.117793]  ? jbd2_journal_stop+0xd7/0x3e0
  [  546.117797]  ? ext4_free_inode+0x3c7/0x560
  [  546.117798]  ? ext4_free_inode+0x1f2/0x560
  [  546.117812]  ? intel_pmu_lbr_init_atom+0x46/0x50
  [  546.117819]  ? call_rcu_sched+0x14/0x20
  [  546.117821]  ? tty_vhangup+0x20/0x20
  [  546.11782

[Kernel-packages] [Bug 1828632] Re: bionic i386 kernel crashes in memory pressure situations

2019-05-14 Thread Juerg Haefliger
Thanks Steve, but I'm still not able to reproduce the kernel crash. If I
start netbeans, the current session is killed and I'm thrown back to the
login screen. If I do this multiple times the VM eventually simply dies.
But no kernel crash.

kernel: 4.15.0-49-generic
netbeans: 10.0-3~18.04.1ubuntu1
openjdk-11-jre: 11.0.3+7-1ubuntu2~18.04.1

qemu-system-x86_64: /build/qemu-VBsewI/qemu-3.1+dfsg/hw/display/qxl.c:1230: 
qxl_check_state: Assertion `!spice_display_running || 
SPICE_RING_IS_EMPTY(&ram->cmd_ring)' failed.
2019-05-14 07:32:36.996+: shutting down, reason=crashed

I'm on a Disco host, are you running on Bionic?

-- 
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/1828632

Title:
  bionic i386 kernel crashes in memory pressure situations

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  New

Bug description:
  The linux-image-4.15.0-49-generic (currently in bionic-proposed) can
  be made to crash in a kvm guest with memory pressure. The reproducer
  used is to attempt to run netbeans with openjdk-8-jre installed as the
  only jvm. It will fail to run, and when it fails, it also causes
  gnome-shell to crash. After 3 to 5 repeats of this, the kernel will
  crash with the following oops in dmesg:

  [  545.926175] rfkill: input handler enabled
  [  546.117550] [ cut here ]
  [  546.117552] kernel BUG at 
/build/linux-S9wgEU/linux-4.15.0/arch/x86/mm/fault.c:268!
  [  546.117564] invalid opcode:  [#1] SMP PTI
  [  546.117565] Modules linked in: snd_hda_codec_generic snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep snd_pcm kvm_intel kvm snd_seq_midi 
snd_seq_midi_e
  vent snd_rawmidi irqbypass snd_seq snd_seq_device input_leds joydev snd_timer 
serio_raw snd soundcore qemu_fw_cfg mac_hid binfmt_misc sch_fq_codel ib_iser r
  dma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi parport_pc ppdev lp parport ip_tables x_tables autofs4 
btrfs zstd_compress r
  aid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid crc32_pc
  lmul pcbc qxl ttm drm_kms_helper syscopyarea aesni_intel aes_i586 sysfillrect 
sysimgblt crypto_simd cryptd fb_sys_fops psmouse virtio_blk virtio_net floppy
  drm pata_acpi i2c_piix4
  [  546.117600] CPU: 0 PID: 1335 Comm: Xorg Not tainted 4.15.0-49-generic 
#53-Ubuntu
  [  546.117600] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [  546.117618] EIP: vmalloc_fault+0x229/0x240
  [  546.117618] EFLAGS: 00010086 CPU: 0
  [  546.117619] EAX: 026c EBX: c3e20c50 ECX: f8eb EDX: 
  [  546.117620] ESI: f140 EDI: f800 EBP: eddc1934 ESP: eddc1918
  [  546.117621]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [  546.117621] CR0: 80050033 CR2: f140 CR3: 25f16000 CR4: 001406f0
  [  546.117624] Call Trace:
  [  546.117637]  ? kvm_async_pf_task_wait+0x1b0/0x1b0
  [  546.117638]  __do_page_fault+0x39d/0x510
  [  546.117640]  ? kvm_async_pf_task_wait+0x1b0/0x1b0
  [  546.117641]  do_page_fault+0x27/0xf0
  [  546.117644]  ? kvm_async_pf_task_wait+0x1b0/0x1b0
  [  546.117645]  do_async_page_fault+0x55/0x90
  [  546.117655]  common_exception+0x130/0x136
  [  546.117659] EIP: qxl_image_init+0x338/0x390 [qxl]
  [  546.117659] EFLAGS: 00010286 CPU: 0
  [  546.117660] EAX: fffbb000 EBX: 0fec ECX: fffbb014 EDX: 0030
  [  546.117661] ESI: f140 EDI: fffbb018 EBP: eddc1a18 ESP: eddc19e4
  [  546.117661]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [  546.117663]  ? ioremap_nocache+0x12/0x20
  [  546.117665]  qxl_draw_dirty_fb+0x1cd/0x3d0 [qxl]
  [  546.117668]  qxl_primary_atomic_update+0x159/0x2c0 [qxl]
  [  546.117680]  drm_atomic_helper_commit_planes+0xe8/0x240 [drm_kms_helper]
  [  546.117684]  drm_atomic_helper_commit_tail+0x23/0x50 [drm_kms_helper]
  [  546.117688]  commit_tail+0x5d/0x60 [drm_kms_helper]
  [  546.117691]  drm_atomic_helper_commit+0xf7/0x100 [drm_kms_helper]
  [  546.117695]  ? drm_atomic_helper_setup_commit+0x3f0/0x3f0 [drm_kms_helper]
  [  546.117715]  drm_atomic_commit+0x3f/0x50 [drm]
  [  546.117719]  restore_fbdev_mode_atomic+0x16b/0x1c0 [drm_kms_helper]
  [  546.117723]  restore_fbdev_mode+0x2c/0x150 [drm_kms_helper]
  [  546.117725]  ? _cond_resched+0x17/0x40
  [  546.117729]  drm_fb_helper_restore_fbdev_mode_unlocked.part.32+0x21/0x70 
[drm_kms_helper]
  [  546.117732]  drm_fb_helper_set_par+0x45/0x80 [drm_kms_helper]
  [  546.117743]  fb_set_var+0x1a9/0x440
  [  546.117750]  ? wakeup_preempt_entity+0x73/0x80
  [  546.117752]  ? check_preempt_wakeup+0x108/0x230
  [  546.117753]  ? check_cfs_rq_runtime+0x70/0x70
  [  546.117755]  ? check_preempt_curr+0x27/0x80
  [  546.117757]  ? ttwu_do_wakeup+0x17/0x190
  [  546.117760]  fbcon_blank+0x29e/0x370
  [  546.117772]  ? __switch_to_asm+0x27/0x4c
  [  546.117774]

[Kernel-packages] [Bug 1804149] Re: Kernel panic, Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi]

2019-05-14 Thread Juerg Haefliger
IBM, have you had any luck with the test kernel?

-- 
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/1804149

Title:
  Kernel panic,Oops: 0004 ilc:3 [#1] SMP,  iscsi_q_20 iscsi_xmitworker
  [libiscsi]

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Michael Finnegan  - 2018-11-19 14:14:40 
==
  ---Problem Description---
  Kernel panic,Oops: 0004 ilc:3 [#1] SMP,  iscsi_q_20 iscsi_xmitworker 
[libiscsi]
   
  ---uname output---
  Linux ilabg3 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 
s390x s390x s390x GNU/Linux
   
  Machine Type = IBM 3906 M05 7G4 (z/VM 7.1.0) 
   
  ---Debugger---
  A debugger is not configured
   
  Contact Information = Michael Finnegan/finne...@us.ibm.com 
   
  Stack trace output:
   dmesg.201811161956
  [1363037.322472] Unable to handle kernel pointer dereference in virtual 
kernel address space
  [1363037.322481] Failing address:  TEID: 0483
  [1363037.322483] Fault in home space mode while using kernel ASCE.
  [1363037.322486] AS:00ea0007 R3:f37d0007 S:f37ff000 
P:013d
  [1363037.322524] Oops: 0004 ilc:3 [#1] SMP
  [1363037.322529] Modules linked in: iptable_filter binfmt_misc 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache qeth_l3 qeth_l2 
s390_trng ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 
sha1_s390 sha_common qeth vmur ccwgroup vfio_ccw vfio_mdev mdev 
vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core sunrpc 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables 
dm_round_robin dm_service_time crc32_vx_s390 dasd_eckd_mod zfcp qdio 
scsi_transport_fc dasd_fba_mod dasd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua 
dm_multipath
  [1363037.322567] CPU: 3 PID: 37970 Comm: kworker/u128:19 Not tainted 
4.15.0-36-generic #39-Ubuntu
  [1363037.322573] Hardware name: IBM 3906 M05 7G4 (z/VM 7.1.0)
  [1363037.322581] Workqueue: iscsi_q_20 iscsi_xmitworker [libiscsi]
  [1363037.322583] Krnl PSW : c8051cf6 e49a28f4 
(__iscsi_get_task+0x6/0x18 [libiscsi])
  [1363037.322587]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 
PM:0 RI:0 EA:3
  [1363037.322589] Krnl GPRS:  02923ce0 
 0400
  [1363037.322591]03ff80277640 0008 
788efc00 03ff802777cc
  [1363037.322592]03ff8027769c  
 78ce8310
  [1363037.322594]f3689800 78ce83a2 
03ff80272e8e 02923c90
  [1363037.322601] Krnl Code: 03ff80272624: c0f4fcf6  brcl
15,3ff80272010
  03ff8027262a: c0f4377b  brcl
15,3ff80279520
 #03ff80272630: c004  brcl
0,3ff80272630
 >03ff80272636: eb012078006a  asi 
120(%r2),1
  03ff8027263c: c0f43772  brcl
15,3ff80279520
  03ff80272642: 0707  bcr 0,%r7
  03ff80272644: 0707  bcr 0,%r7
  03ff80272646: 0707  bcr 0,%r7
  [1363037.322618] Call Trace:
  [1363037.322621] ([<03ff80272ec6>] iscsi_xmit_task+0x86/0x138 [libiscsi])
  [1363037.322625]  [<03ff8027769c>] iscsi_data_xmit+0x44c/0x548 [libiscsi]
  [1363037.322636]  [<03ff802777cc>] iscsi_xmitworker+0x34/0x58 [libiscsi]
  [1363037.322642]  [<001918f2>] process_one_work+0x262/0x4d8
  [1363037.322644]  [<00191bc0>] worker_thread+0x58/0x4e8
  [1363037.322648]  [<00198d24>] kthread+0x14c/0x168
  [1363037.322652]  [<008e3eb2>] kernel_thread_starter+0xa/0x10
  [1363037.322654]  [<008e3ea8>] kernel_thread_starter+0x0/0x10
  [1363037.322655] Last Breaking-Event-Address:
  [1363037.322657]  [<03ff80272e88>] iscsi_xmit_task+0x48/0x138 [libiscsi]
  [1363037.322658]
  [1363037.322660] Kernel panic - not syncing: Fatal exception in interrupt

  
   
  Oops output:
Oops: 0004 ilc:3 [#1] SMP


  *Additional Instructions for Michael Finnegan/finne...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1804149/+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 1819493] Re: network loss and traffic loss problems with i40e 2.1.14-k in Xenial HWE Kernel 4.15

2019-05-14 Thread Juerg Haefliger
The following commits are required for 4.15:
  - 14a627313893 ("i40e: Check and correct speed values for link on open")
  - 6f0c1b41ae95 ("i40e: Set fec_config when forcing link state")
  - c3880bd159d4 ("i40e: link_down_on_close private flag support")

-- 
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/1819493

Title:
  network loss and traffic loss problems with i40e 2.1.14-k in Xenial
  HWE Kernel 4.15

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  [SRU Justification]

  = Impact =

  Network loss and traffic loss problems experienced by customer with i40e 
2.1.14-k in Xenial HWE Kernel 4.15
  The traffic issues were reported from our customer deployments and we had 
Intel helping us with the troubleshooting of the problem.

  = Fix =

  Intel recommends and customer requests application of the following
  commit e78d9a39fd06109022d11c8ca444cfcec2abb290 (upstream Linus tree)

  = Testcase =

  The issue could only be seen in customer environment. Regression
  testing only would be possible.

  = Regression Potential =

  Change is limited to a specific driver, testing should show if there
  is any negative impact.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819493/+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 1775137] Re: Prevent speculation on user controlled pointer

2019-05-14 Thread Juerg Haefliger
** Changed in: linux (Ubuntu Precise)
   Status: Fix Committed => Fix Released

-- 
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/1775137

Title:
  Prevent speculation on user controlled pointer

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  == SRU Justification ==
  Upstream's Spectre v1 mitigation prevents speculation on a user controlled 
pointer. This part of the Spectre v1 patchset was never backported to 4.4 (for 
unknown reasons) so Xenial/Trusty/Precise are lacking it as well. All the other 
stable upstream kernels include it, so add it to our older kernels.

  == Fix ==
  Backport the following patches:
  x86/uaccess: Use __uaccess_begin_nospec() and uaccess_try_nospec
  x86/usercopy: Replace open coded stac/clac with __uaccess_{begin, end}
  x86: Introduce __uaccess_begin_nospec() and uaccess_try_nospec

  == Regression Potential ==
  Low. Patches have been in upstream (and other distro kernels) for quite a 
while now and the changes only introduce a barrier on copy_from_user operations.

  == Test Case ==
  TBD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775137/+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 1774181] Re: Update to upstream's implementation of Spectre v1 mitigation

2019-05-14 Thread Juerg Haefliger
** Changed in: linux (Ubuntu Precise)
   Status: Fix Committed => Fix Released

-- 
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/1774181

Title:
  Update to upstream's implementation of Spectre v1 mitigation

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Xenial/Trusty/Precise are currently lacking full support of upstream's
  Spectre v1 mitigation. Add the missing patches and merge them with
  Ubuntu's current implementation.

  == SRU Justification ==
  Ubuntu's Spectre v1 mitigation is based on the original embargoed patchset 
which introduced a barrier macro to prevent speculation beyond array boundaries 
for user controlled indices. What eventually landed in upstream is slightly 
different and uses a barrier macro in combination with a masking solution (plus 
syscall table and user pointer sanitation). During the updates to newer stable 
upstream versions, all those patches were skipped. After reviewing them, we 
want to bring them back and merge them with the current implementation which 
brings us back in sync with upstream stable.

  == Fix ==
  Add all the missing Spectre v1 patches from upstream stable 4.4.118 to 
4.4.131. Where appropriate, replace Ubuntu's additional barriers with the 
masking macro.

  == Regression Potential ==
  Low. The patches have been in upstream for quite a while now and we keep the 
speculation barriers that are currently in Ubuntu but not in upstream.

  == Test Case ==
  TBD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774181/+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 1829206] Re: linux-ibm-gt: 4.15.0-1022.24 -proposed tracker

2019-05-17 Thread Juerg Haefliger
** Summary changed:

- linux-ibm-gt:  -proposed tracker
+ linux-ibm-gt: 4.15.0-1022.24 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger 
(juergh)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger 
(juergh)

-- 
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/1829206

Title:
  linux-ibm-gt: 4.15.0-1022.24 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  kernel-stable-master-bug: 1829219
  phase: Ready for Packaging
  phase-changed: Wednesday, 15. May 2019 15:06 UTC
  reason:
prepare-package: Pending -- version not specified

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829206/+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 1779848] Re: Cleanup Meltdown/Spectre implementation

2019-05-20 Thread Juerg Haefliger
** Also affects: linux (Ubuntu Precise)
   Importance: Undecided
   Status: New

-- 
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/1779848

Title:
  Cleanup Meltdown/Spectre implementation

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Invalid

Bug description:
  == SRU Justification ==

  Ubuntu kernels contain Meltdown and Spectre mitigations that are
  largely based on embargoed patches but what eventually landed in
  upstream is different in some places. We should clean up the different
  kernels to bring them closer in line with upstream.

  == Fix ==

  Add missing upstream patches.

  == Regression Potential ==

  Medium. The patches have been in upstream for quite a while now and
  are baked in but some of the backporting is not completely trivial and
  without risk.

  == Test Case ==

  TBD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779848/+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 1829882] [NEW] Switch getabis to the new format

2019-05-21 Thread Juerg Haefliger
Private bug reported:

All custom/private kernels are using the new getabis file format except
Precise. Fix that.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux (Ubuntu Precise)
 Importance: Undecided
 Status: Confirmed

** Information type changed from Public to Private

** Also affects: linux (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Precise)
   Status: New => Confirmed

** Changed in: linux (Ubuntu)
   Status: New => Invalid

-- 
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/1829882

Title:
  Switch getabis to the new format

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Confirmed

Bug description:
  All custom/private kernels are using the new getabis file format
  except Precise. Fix that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829882/+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 1830018] [NEW] MDS: Incorrect warning when booting with 'nosmt'

2019-05-22 Thread Juerg Haefliger
Private bug reported:

Booting a Precise or Trusty kernel on an SMT system with mds=full,nosmt
results in the following incorrect warning being emitted:

[0.076019] MDS CPU bug present and SMT on, data leak possible. See
https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for
more details.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Precise)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Trusty)
 Importance: Undecided
 Status: New

** Information type changed from Public to Private

** Also affects: linux (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Precise)
   Importance: Undecided
   Status: New

-- 
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/1830018

Title:
  MDS: Incorrect warning when booting with 'nosmt'

Status in linux package in Ubuntu:
  New
Status in linux source package in Precise:
  New
Status in linux source package in Trusty:
  New

Bug description:
  Booting a Precise or Trusty kernel on an SMT system with
  mds=full,nosmt results in the following incorrect warning being
  emitted:

  [0.076019] MDS CPU bug present and SMT on, data leak possible. See
  https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html
  for more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830018/+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 1830176] [NEW] Xenial update: 4.4.180 upstream stable release

2019-05-23 Thread Juerg Haefliger
Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   4.4.180 upstream stable release
   from git://git.kernel.org/


Linux 4.4.180
powerpc/lib: fix book3s/32 boot failure due to code patching
powerpc/booke64: set RI in default MSR
drivers/virt/fsl_hypervisor.c: prevent integer overflow in ioctl
drivers/virt/fsl_hypervisor.c: dereferencing error pointers in ioctl
bonding: fix arp_validate toggling in active-backup mode
ipv4: Fix raw socket lookup for local traffic
vrf: sit mtu should not be updated when vrf netdev is the link
vlan: disable SIOCSHWTSTAMP in container
packet: Fix error path in packet_init
net: ucc_geth - fix Oops when changing number of buffers in the ring
bridge: Fix error path for kobject_init_and_add()
powerpc/64s: Include cpu header
USB: serial: fix unthrottle races
USB: serial: use variable for status
x86/bugs: Change L1TF mitigation string to match upstream
x86/speculation/mds: Fix documentation typo
Documentation: Correct the possible MDS sysfs values
x86/mds: Add MDSUM variant to the MDS documentation
x86/speculation/mds: Add 'mitigations=' support for MDS
x86/speculation: Support 'mitigations=' cmdline option
cpu/speculation: Add 'mitigations=' cmdline option
x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off
x86/speculation/mds: Fix comment
x86/speculation/mds: Add SMT warning message
x86/speculation: Move arch_smt_update() call to after mitigation decisions
x86/cpu/bugs: Use __initconst for 'const' init data
Documentation: Add MDS vulnerability documentation
Documentation: Move L1TF to separate directory
x86/speculation/mds: Add mitigation mode VMWERV
x86/speculation/mds: Add sysfs reporting for MDS
x86/speculation/l1tf: Document l1tf in sysfs
x86/speculation/mds: Add mitigation control for MDS
x86/speculation/mds: Conditionally clear CPU buffers on idle entry
x86/speculation/mds: Clear CPU buffers on exit to user
x86/speculation/mds: Add mds_clear_cpu_buffers()
x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests
x86/speculation/mds: Add BUG_MSBDS_ONLY
x86/speculation/mds: Add basic bug infrastructure for MDS
x86/speculation: Consolidate CPU whitelists
x86/msr-index: Cleanup bit defines
kvm: x86: Report STIBP on GET_SUPPORTED_CPUID
x86/speculation: Provide IBPB always command line options
x86/speculation: Add seccomp Spectre v2 user space protection mode
x86/speculation: Enable prctl mode for spectre_v2_user
x86/speculation: Add prctl() control for indirect branch speculation
x86/speculation: Prevent stale SPEC_CTRL msr content
x86/speculation: Prepare arch_smt_update() for PRCTL mode
x86/speculation: Split out TIF update
x86/speculation: Prepare for conditional IBPB in switch_mm()
x86/speculation: Avoid __switch_to_xtra() calls
x86/process: Consolidate and simplify switch_to_xtra() code
x86/speculation: Prepare for per task indirect branch speculation control
x86/speculation: Add command line control for indirect branch speculation
x86/speculation: Unify conditional spectre v2 print functions
x86/speculataion: Mark command line parser data __initdata
x86/speculation: Mark string arrays const correctly
x86/speculation: Reorder the spec_v2 code
x86/speculation: Rework SMT state change
sched: Add sched_smt_active()
x86/Kconfig: Select SCHED_SMT if SMP enabled
x86/speculation: Reorganize speculation control MSRs update
x86/speculation: Rename SSBD update functions
x86/speculation: Disable STIBP when enhanced IBRS is in use
x86/speculation: Move STIPB/IBPB string conditionals out of cpu_show_common()
x86/speculation: Remove unnecessary ret variable in cpu_show_common()
x86/speculation: Clean up spectre_v2_parse_cmdline()
x86/speculation: Update the TIF_SSBD comment
x86/speculation: Propagate information about RSB filling mitigation to sysfs
x86/speculation: Enable cross-hyperthread spectre v2 STIBP mitigation
x86/speculation: Apply IBPB more strictly to avoid cross-process data leak
x86/mm: Use WRITE_ONCE() when setting PTEs
KVM: x86: SVM: Call x86_spec_ctrl_set_guest/host() with interrupts disabled
x86/cpu: Sanitize FAM6_ATOM naming
x86/microcode: Update the new microcode revision unconditionally
x86/microcode: Make sure boot_cpu_data.microcode is up-to-date
x86/speculation: Remove SPECTRE_V2_IBRS in enum spectre_v2_mitigation
x86/bugs: Fix the AMD SSBD usage of the SPEC_CTRL MSR
locking/atomics, asm-generic: Move some macros from  to a new 
 file
x86/bugs: Switch the selection of mitigation from CPU vendor to CPU features
x86/bugs: Add AMD's SPEC_CTRL MSR usage
x86/bugs: Add AMD's variant of SSB_NO
x86/speculation: Simplify the CPU 

[Kernel-packages] [Bug 1822810] Re: linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

2019-05-23 Thread Juerg Haefliger
*** This bug is a duplicate of bug 1829206 ***
https://bugs.launchpad.net/bugs/1829206

** This bug is no longer a duplicate of bug 1826345
   linux-ibm-gt: 4.15.0-1020.22 -proposed tracker
** This bug has been marked a duplicate of bug 1829206
   linux-ibm-gt: 4.15.0-1022.24 -proposed tracker

-- 
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/1822810

Title:
  linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Ready for Testing
  phase-changed: Monday, 22. April 2019 02:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822810/+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 1819701] Re: linux-ibm-gt: 4.15.0-1018.20 -proposed tracker

2019-05-23 Thread Juerg Haefliger
*** This bug is a duplicate of bug 1829206 ***
https://bugs.launchpad.net/bugs/1829206

** This bug is no longer a duplicate of bug 1826345
   linux-ibm-gt: 4.15.0-1020.22 -proposed tracker
** This bug has been marked a duplicate of bug 1829206
   linux-ibm-gt: 4.15.0-1022.24 -proposed tracker

-- 
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/1819701

Title:
  linux-ibm-gt: 4.15.0-1018.20 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Ready for Release
  phase-changed: Tuesday, 02. April 2019 09:48 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Pending -- ready to copy
promote-to-updates: Pending -- ready to copy

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819701/+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 1815061] Re: linux-ibm-gt: 4.15.0-1016.18 -proposed tracker

2019-05-23 Thread Juerg Haefliger
*** This bug is a duplicate of bug 1829206 ***
https://bugs.launchpad.net/bugs/1829206

** This bug is no longer a duplicate of bug 1826345
   linux-ibm-gt: 4.15.0-1020.22 -proposed tracker
** This bug has been marked a duplicate of bug 1829206
   linux-ibm-gt: 4.15.0-1022.24 -proposed tracker

-- 
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/1815061

Title:
  linux-ibm-gt: 4.15.0-1016.18 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug is for tracking the 4.15.0-1016.18 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814726
  phase: Ready for Testing
  phase-changed: Sunday, 03. March 2019 06:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1815061/+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 1811850] Re: linux-ibm-gt: 4.15.0-1015.17 -proposed tracker

2019-05-23 Thread Juerg Haefliger
*** This bug is a duplicate of bug 1829206 ***
https://bugs.launchpad.net/bugs/1829206

** This bug is no longer a duplicate of bug 1826345
   linux-ibm-gt: 4.15.0-1020.22 -proposed tracker
** This bug has been marked a duplicate of bug 1829206
   linux-ibm-gt: 4.15.0-1022.24 -proposed tracker

-- 
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/1811850

Title:
  linux-ibm-gt: 4.15.0-1015.17 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.15.0-1015.17 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  phase: Testing
  phase-changed: Monday, 28. January 2019 18:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811850/+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 1826345] Re: linux-ibm-gt: 4.15.0-1020.22 -proposed tracker

2019-05-23 Thread Juerg Haefliger
*** This bug is a duplicate of bug 1829206 ***
https://bugs.launchpad.net/bugs/1829206

** This bug has been marked a duplicate of bug 1829206
   linux-ibm-gt: 4.15.0-1022.24 -proposed tracker

-- 
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/1826345

Title:
  linux-ibm-gt: 4.15.0-1020.22 -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  phase: Ready for Testing
  phase-changed: Monday, 13. May 2019 04:41 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826345/+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 1829206] Re: linux-ibm-gt: 4.15.0-1022.24 -proposed tracker

2019-05-23 Thread Juerg Haefliger
** Tags added: kernel-unblock-ppa

-- 
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/1829206

Title:
  linux-ibm-gt: 4.15.0-1022.24 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829219
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 20. May 2019 13:10 UTC
  reason:
promote-to-proposed: Holding -- another kernel is currently pending in 
Proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829206/+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 1830176] Re: Xenial update: 4.4.180 upstream stable release

2019-05-27 Thread Juerg Haefliger
List of previously applied patches:
  * selftests/net: correct the return value for run_netsocktests
  * x86/speculation/mds: Add 'mitigations=' support for MDS
  * x86/speculation: Support 'mitigations=' cmdline option
  * cpu/speculation: Add 'mitigations=' cmdline option
  * x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off
  * x86/speculation/mds: Fix comment
  * x86/speculation/mds: Add SMT warning message
  * x86/speculation: Move arch_smt_update() call to after mitigation decisions
  * x86/speculation/mds: Add mitigation mode VMWERV
  * x86/speculation/mds: Add sysfs reporting for MDS
  * x86/speculation/mds: Add mitigation control for MDS
  * x86/speculation: Unify conditional spectre v2 print functions
  * x86/speculation: Reorder the spec_v2 code
  * x86/speculation: Rework SMT state change
  * x86/speculation/mds: Conditionally clear CPU buffers on idle entry
  * x86/speculation/mds: Clear CPU buffers on exit to user
  * locking/static_keys: Provide DECLARE and well as DEFINE macros
  * x86/speculation/mds: Add mds_clear_cpu_buffers()
  * x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests
  * x86/speculation/mds: Add BUG_MSBDS_ONLY
  * x86/speculation/mds: Add basic bug infrastructure for MDS
  * x86/speculation: Consolidate CPU whitelists
  * x86/msr-index: Cleanup bit defines
  * locking/atomics, asm-generic: Move some macros from  to a 
new  file
  * bitops: avoid integer overflow in GENMASK(_ULL)
  * kvm: x86: Report STIBP on GET_SUPPORTED_CPUID
  * x86/cpu: Sanitize FAM6_ATOM naming
  * x86/speculation: Simplify the CPU bug detection logic
  * vfio/type1: Limit DMA mappings per container
  * igb: Fix WARN_ONCE on runtime suspend
  * KVM: x86: SVM: Call x86_spec_ctrl_set_guest/host() with interrupts disabled
  * x86/speculation: Support Enhanced IBRS on future CPUs
  * x86/speculation: Remove SPECTRE_V2_IBRS in enum spectre_v2_mitigation
  * powerpc/pseries: Restore default security feature flags on setup
  * powerpc: Move default security feature flags
  * powerpc/pseries: Fix clearing of security feature flags
  * powerpc/64s: Wire up cpu_show_spectre_v2()
  * powerpc/64s: Wire up cpu_show_spectre_v1()
  * powerpc/pseries: Use the security flags in pseries_setup_rfi_flush()
  * powerpc/powernv: Use the security flags in pnv_setup_rfi_flush()
  * powerpc/64s: Enhance the information in cpu_show_meltdown()
  * powerpc/64s: Move cpu_show_meltdown()
  * powerpc/powernv: Set or clear security feature flags
  * powerpc/pseries: Set or clear security feature flags
  * powerpc: Add security feature flags for Spectre/Meltdown
  * powerpc/pseries: Add new H_GET_CPU_CHARACTERISTICS flags
  * powerpc/rfi-flush: Call setup_rfi_flush() after LPM migration
  * powerpc/rfi-flush: Differentiate enabled and patched flush types
  * powerpc/rfi-flush: Always enable fallback flush on pseries
  * powerpc/rfi-flush: Make it possible to call setup_rfi_flush() again
  * powerpc/rfi-flush: Move the logic to avoid a redo into the debugfs code
  * powerpc/powernv: Support firmware disable of RFI flush
  * powerpc/pseries: Support firmware disable of RFI flush

-- 
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/1830176

Title:
  Xenial update: 4.4.180 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  New

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 4.4.180 upstream stable release
 from git://git.kernel.org/

  
  Linux 4.4.180
  powerpc/lib: fix book3s/32 boot failure due to code patching
  powerpc/booke64: set RI in default MSR
  drivers/virt/fsl_hypervisor.c: prevent integer overflow in ioctl
  drivers/virt/fsl_hypervisor.c: dereferencing error pointers in ioctl
  bonding: fix arp_validate toggling in active-backup mode
  ipv4: Fix raw socket lookup for local traffic
  vrf: sit mtu should not be updated when vrf netdev is the link
  vlan: disable SIOCSHWTSTAMP in container
  packet: Fix error path in packet_init
  net: ucc_geth - fix Oops when changing number of buffers in the ring
  bridge: Fix error path for kobject_init_and_add()
  powerpc/64s: Include cpu header
  USB: serial: fix unthrottle races
  USB: serial: use variable for status
  x86/bugs: Change L1TF mitigation string to match upstream
  x86/speculation/mds: Fix documentation typo
  Documentation: Correct the possible MDS sysfs values
  x86/mds: Add MDSUM variant to the MDS documentation
  x86/speculation

[Kernel-packages] [Bug 1830176] Re: Xenial update: 4.4.180 upstream stable release

2019-05-27 Thread Juerg Haefliger
List of not required patches (changes applied via previous (SAUCE) patches):
  * x86/bugs: Change L1TF mitigation string to match upstream
  * x86/speculation/l1tf: Document l1tf in sysfs
  * sched: Add sched_smt_active()
  * x86/speculation: Remove unnecessary ret variable in cpu_show_common()
  * x86/cpufeatures: Hide AMD-specific speculation flags

-- 
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/1830176

Title:
  Xenial update: 4.4.180 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  New

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 4.4.180 upstream stable release
 from git://git.kernel.org/

  
  Linux 4.4.180
  powerpc/lib: fix book3s/32 boot failure due to code patching
  powerpc/booke64: set RI in default MSR
  drivers/virt/fsl_hypervisor.c: prevent integer overflow in ioctl
  drivers/virt/fsl_hypervisor.c: dereferencing error pointers in ioctl
  bonding: fix arp_validate toggling in active-backup mode
  ipv4: Fix raw socket lookup for local traffic
  vrf: sit mtu should not be updated when vrf netdev is the link
  vlan: disable SIOCSHWTSTAMP in container
  packet: Fix error path in packet_init
  net: ucc_geth - fix Oops when changing number of buffers in the ring
  bridge: Fix error path for kobject_init_and_add()
  powerpc/64s: Include cpu header
  USB: serial: fix unthrottle races
  USB: serial: use variable for status
  x86/bugs: Change L1TF mitigation string to match upstream
  x86/speculation/mds: Fix documentation typo
  Documentation: Correct the possible MDS sysfs values
  x86/mds: Add MDSUM variant to the MDS documentation
  x86/speculation/mds: Add 'mitigations=' support for MDS
  x86/speculation: Support 'mitigations=' cmdline option
  cpu/speculation: Add 'mitigations=' cmdline option
  x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off
  x86/speculation/mds: Fix comment
  x86/speculation/mds: Add SMT warning message
  x86/speculation: Move arch_smt_update() call to after mitigation decisions
  x86/cpu/bugs: Use __initconst for 'const' init data
  Documentation: Add MDS vulnerability documentation
  Documentation: Move L1TF to separate directory
  x86/speculation/mds: Add mitigation mode VMWERV
  x86/speculation/mds: Add sysfs reporting for MDS
  x86/speculation/l1tf: Document l1tf in sysfs
  x86/speculation/mds: Add mitigation control for MDS
  x86/speculation/mds: Conditionally clear CPU buffers on idle entry
  x86/speculation/mds: Clear CPU buffers on exit to user
  x86/speculation/mds: Add mds_clear_cpu_buffers()
  x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests
  x86/speculation/mds: Add BUG_MSBDS_ONLY
  x86/speculation/mds: Add basic bug infrastructure for MDS
  x86/speculation: Consolidate CPU whitelists
  x86/msr-index: Cleanup bit defines
  kvm: x86: Report STIBP on GET_SUPPORTED_CPUID
  x86/speculation: Provide IBPB always command line options
  x86/speculation: Add seccomp Spectre v2 user space protection mode
  x86/speculation: Enable prctl mode for spectre_v2_user
  x86/speculation: Add prctl() control for indirect branch speculation
  x86/speculation: Prevent stale SPEC_CTRL msr content
  x86/speculation: Prepare arch_smt_update() for PRCTL mode
  x86/speculation: Split out TIF update
  x86/speculation: Prepare for conditional IBPB in switch_mm()
  x86/speculation: Avoid __switch_to_xtra() calls
  x86/process: Consolidate and simplify switch_to_xtra() code
  x86/speculation: Prepare for per task indirect branch speculation control
  x86/speculation: Add command line control for indirect branch speculation
  x86/speculation: Unify conditional spectre v2 print functions
  x86/speculataion: Mark command line parser data __initdata
  x86/speculation: Mark string arrays const correctly
  x86/speculation: Reorder the spec_v2 code
  x86/speculation: Rework SMT state change
  sched: Add sched_smt_active()
  x86/Kconfig: Select SCHED_SMT if SMP enabled
  x86/speculation: Reorganize speculation control MSRs update
  x86/speculation: Rename SSBD update functions
  x86/speculation: Disable STIBP when enhanced IBRS is in use
  x86/speculation: Move STIPB/IBPB string conditionals out of cpu_show_common()
  x86/speculation: Remove unnecessary ret variable in cpu_show_common()
  x86/speculation: Clean up spectre_v2_parse_cmdline()
  x86/speculation: Update the TIF_SSBD comment
  x86/speculation: Propagate information about RSB filling 

[Kernel-packages] [Bug 1819701] Re: linux-ibm-gt: 4.15.0-1017.19 -proposed tracker

2019-03-14 Thread Juerg Haefliger
** Summary changed:

- linux-ibm-gt:  -proposed tracker
+ linux-ibm-gt: 4.15.0-1017.19 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger 
(juergh)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger 
(juergh)

-- 
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/1819701

Title:
  linux-ibm-gt: 4.15.0-1017.19 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  kernel-stable-master-bug: 1819716
  phase: Ready for Packaging
  phase-changed: Wednesday, 13. March 2019 11:03 UTC
  reason:
prepare-package: Pending -- version not specified

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819701/+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 1818645] Re: Ubuntu18.04.01: [Power9] power8 Compat guest(RHEL7.6) crashes during guest boot with > 256G of memory (kernel/kvm)

2019-03-19 Thread Juerg Haefliger
Nominating for Bionic as the referenced commit is a valid fix for
Bionic.

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

-- 
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/1818645

Title:
  Ubuntu18.04.01: [Power9] power8 Compat guest(RHEL7.6) crashes during
  guest boot with > 256G of memory (kernel/kvm)

Status in The Ubuntu-power-systems project:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2019-02-28 
04:38:22 ==
  ---Problem Description---
  Power8 Compat guest(RHEL 7.6) crashes during guest boot with > 256G of memory 
(kernel/kvm)
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  Host Kernel: 4.15.0-1016-ibm-gt

  ii  qemu-system-ppc1:2.11+dfsg-
  1ubuntu7.8-1ibm3   ppc64el  QEMU
  full system emulation binaries (ppc)

  ii  libvirt-bin4.0.0-1ubuntu8.6
  ppc64el  programs for the libvirt library

  Guest kernel: 3.10.0-957.5.1.el7.ppc64le (rhel7.6 zstream)
   
  Machine Type = power9 ppc64le 

   
  ---Steps to Reproduce---
   1. Boot a power8 compat guest with memory >256G
  virsh define avocado-vt-vm1;virsh start --console avocado-vt-vm1 (guest xml 
sosreport attached)
  Guest crashes while booting

  
  2019-02-28 10:36:44.752+: starting up libvirt version: 4.0.0, package: 
1ubuntu8.6 (Christian Ehrhardt  Fri, 09 Nov 
2018 07:42:01 +0100), qemu version: 2.11.1(Debian 
1:2.11+dfsg-1ubuntu7.8-1ibm3), hostname: cs-host-f37-ac922-3.pok.ibm.com
  LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 
QEMU_AUDIO_DRV=none /usr/bin/qemu-system-ppc64 -name 
guest=avocado-vt-vm1,debug-threads=on -S -object 
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-15-avocado-vt-vm1/master-key.aes
 -machine pseries-2.11,accel=kvm,usb=off,dump-guest-core=off -m 264192 
-realtime mlock=off -smp 256,sockets=256,cores=1,threads=1 -uuid 
f4e14f88-bf1b-4cc3-b6d6-958d514d6c18 -display none -no-user-config -nodefaults 
-chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-15-avocado-vt-vm1/monitor.sock,server,nowait
 -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown 
-boot strict=on -device qemu-xhci,id=usb,bus=pci.0,addr=0x3 -device 
virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x2 -device 
virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive 
file=/home/sath/avocado-fvt-wrapper/data/avocado-vt/images/rhel76-ppc64le.qcow2,format=qcow2,if=none,id=drive-scsi0-0-0-0
 -device 
scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1
 -netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=30 -device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:fc:fd:fe,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -chardev 
socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-15-avocado-vt-vm1/org.qemu.guest_agent.0,server,nowait
 -device 
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0
 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on
  2019-02-28 10:36:44.759+: 19598: info : libvirt version: 4.0.0, package: 
1ubuntu8.6 (Christian Ehrhardt  Fri, 09 Nov 
2018 07:42:01 +0100)
  2019-02-28 10:36:44.759+: 19598: info : hostname: cs-host-f37-ac922-3
  2019-02-28 10:36:44.759+: 19598: info : virObjectUnref:350 : 
OBJECT_UNREF: obj=0x76d594111710
  2019-02-28T10:36:44.781703Z qemu-system-ppc64: -chardev pty,id=charserial0: 
char device redirected to /dev/pts/3 (label charserial0)
  2019-02-28T10:36:44.781945Z qemu-system-ppc64: warning: Number of SMP cpus 
requested (256) exceeds the recommended cpus supported by KVM (128)
  2019-02-28T10:36:44.781953Z qemu-system-ppc64: warning: Number of 
hotpluggable cpus requested (256) exceeds the recommended cpus supported by KVM 
(128)
  2019-02-28 10:37:18.060+: shutting down, reason=crashed
  2019-02-28T10:37:18.071969Z qemu-system-ppc64: terminating on signal 15 from 
pid 14056 (/usr/sbin/libvirtd)

   
  *Additional Instructions for sathe...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

  
  == Comment: #3 - Satheesh Rajendran  - 2019-02-28 
04:51:45 ==
  Possible Upstream fix: 
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next&id=46dec40fb741f00f1864580130779aeeaf24fb3d

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1818645/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https:

[Kernel-packages] [Bug 1818645] Re: Ubuntu18.04.01: [Power9] power8 Compat guest(RHEL7.6) crashes during guest boot with > 256G of memory (kernel/kvm)

2019-03-19 Thread Juerg Haefliger
** Description changed:

+ == SRU Justification ==
+ 
+ Rebooting a PowerPC VM with > 256G of memory results in a guest crash.
+ 
+ == Fix ==
+ 
+ Backport commit 46dec40fb741 ("KVM: PPC: Book3S HV: Don't truncate HPTE
+ index in xlate function").
+ 
+ == Regression Potential ==
+ 
+ Low. Fix is trivial.
+ 
+ == Test Case ==
+ 
+ Create a PowerPC VM with > 256G of memory and reboot it repeatedly.
+ 
+ 
+ Original description:
+ 
  == Comment: #0 - Satheesh Rajendran  - 2019-02-28 
04:38:22 ==
  ---Problem Description---
  Power8 Compat guest(RHEL 7.6) crashes during guest boot with > 256G of memory 
(kernel/kvm)
-  
- Contact Information = sathe...@in.ibm.com 
-  
+ 
+ Contact Information = sathe...@in.ibm.com
+ 
  ---uname output---
  Host Kernel: 4.15.0-1016-ibm-gt
  
  ii  qemu-system-ppc1:2.11+dfsg-
  1ubuntu7.8-1ibm3   ppc64el  QEMU
  full system emulation binaries (ppc)
  
  ii  libvirt-bin4.0.0-1ubuntu8.6
  ppc64el  programs for the libvirt library
  
  Guest kernel: 3.10.0-957.5.1.el7.ppc64le (rhel7.6 zstream)
-  
- Machine Type = power9 ppc64le 
  
-  
+ Machine Type = power9 ppc64le
+ 
  ---Steps to Reproduce---
-  1. Boot a power8 compat guest with memory >256G
+  1. Boot a power8 compat guest with memory >256G
  virsh define avocado-vt-vm1;virsh start --console avocado-vt-vm1 (guest xml 
sosreport attached)
  Guest crashes while booting
- 
  
  2019-02-28 10:36:44.752+: starting up libvirt version: 4.0.0, package: 
1ubuntu8.6 (Christian Ehrhardt  Fri, 09 Nov 
2018 07:42:01 +0100), qemu version: 2.11.1(Debian 
1:2.11+dfsg-1ubuntu7.8-1ibm3), hostname: cs-host-f37-ac922-3.pok.ibm.com
  LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 
QEMU_AUDIO_DRV=none /usr/bin/qemu-system-ppc64 -name 
guest=avocado-vt-vm1,debug-threads=on -S -object 
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-15-avocado-vt-vm1/master-key.aes
 -machine pseries-2.11,accel=kvm,usb=off,dump-guest-core=off -m 264192 
-realtime mlock=off -smp 256,sockets=256,cores=1,threads=1 -uuid 
f4e14f88-bf1b-4cc3-b6d6-958d514d6c18 -display none -no-user-config -nodefaults 
-chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-15-avocado-vt-vm1/monitor.sock,server,nowait
 -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown 
-boot strict=on -device qemu-xhci,id=usb,bus=pci.0,addr=0x3 -device 
virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x2 -device 
virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive 
file=/home/sath/avocado-fvt-wrapper/data/avocado-vt/images/rhel76-ppc64le.qcow2,format=qcow2,if=none,id=drive-scsi0-0-0-0
 -device 
scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1
 -netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=30 -device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:fc:fd:fe,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -chardev 
socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-15-avocado-vt-vm1/org.qemu.guest_agent.0,server,nowait
 -device 
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0
 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on
  2019-02-28 10:36:44.759+: 19598: info : libvirt version: 4.0.0, package: 
1ubuntu8.6 (Christian Ehrhardt  Fri, 09 Nov 
2018 07:42:01 +0100)
  2019-02-28 10:36:44.759+: 19598: info : hostname: cs-host-f37-ac922-3
  2019-02-28 10:36:44.759+: 19598: info : virObjectUnref:350 : 
OBJECT_UNREF: obj=0x76d594111710
  2019-02-28T10:36:44.781703Z qemu-system-ppc64: -chardev pty,id=charserial0: 
char device redirected to /dev/pts/3 (label charserial0)
  2019-02-28T10:36:44.781945Z qemu-system-ppc64: warning: Number of SMP cpus 
requested (256) exceeds the recommended cpus supported by KVM (128)
  2019-02-28T10:36:44.781953Z qemu-system-ppc64: warning: Number of 
hotpluggable cpus requested (256) exceeds the recommended cpus supported by KVM 
(128)
  2019-02-28 10:37:18.060+: shutting down, reason=crashed
  2019-02-28T10:37:18.071969Z qemu-system-ppc64: terminating on signal 15 from 
pid 14056 (/usr/sbin/libvirtd)
  
-  
- *Additional Instructions for sathe...@in.ibm.com: 
+ *Additional Instructions for sathe...@in.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.
- 
  
  == Comment: #3 - Satheesh Rajendran  - 2019-02-28 
04:51:45 ==
  Possible Upstream fix: 
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next&id=46dec40fb741f00f1864580130779aeeaf24fb3d

** Description changed:

  == SRU Justification ==
  
  Rebooting a PowerPC VM with > 256G of memory results in a guest crash.
  
  == Fix ==
  
  Backport commit 46dec40fb741 ("KVM: PPC: Book3S HV: Don't truncate HPTE
  index in x

[Kernel-packages] [Bug 1818645] Re: Ubuntu18.04.01: [Power9] power8 Compat guest(RHEL7.6) crashes during guest boot with > 256G of memory (kernel/kvm)

2019-03-19 Thread Juerg Haefliger
Can you please give the following test kernel a try and let me know if that 
resolves the issue?
https://kernel.ubuntu.com/~juergh/lp1818645/

-- 
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/1818645

Title:
  Ubuntu18.04.01: [Power9] power8 Compat guest(RHEL7.6) crashes during
  guest boot with > 256G of memory (kernel/kvm)

Status in The Ubuntu-power-systems project:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New

Bug description:
  == SRU Justification ==

  Rebooting a PowerPC VM with > 256G of memory results in a guest crash.

  == Fix ==

  Backport commit 46dec40fb741 ("KVM: PPC: Book3S HV: Don't truncate
  HPTE index in xlate function").

  == Regression Potential ==

  Low. Fix is trivial.

  == Test Case ==

  Create a PowerPC VM with > 256G of memory and reboot it repeatedly.

  == Original description ==

  == Comment: #0 - Satheesh Rajendran  - 2019-02-28 
04:38:22 ==
  ---Problem Description---
  Power8 Compat guest(RHEL 7.6) crashes during guest boot with > 256G of memory 
(kernel/kvm)

  Contact Information = sathe...@in.ibm.com

  ---uname output---
  Host Kernel: 4.15.0-1016-ibm-gt

  ii  qemu-system-ppc1:2.11+dfsg-
  1ubuntu7.8-1ibm3   ppc64el  QEMU
  full system emulation binaries (ppc)

  ii  libvirt-bin4.0.0-1ubuntu8.6
  ppc64el  programs for the libvirt library

  Guest kernel: 3.10.0-957.5.1.el7.ppc64le (rhel7.6 zstream)

  Machine Type = power9 ppc64le

  ---Steps to Reproduce---
   1. Boot a power8 compat guest with memory >256G
  virsh define avocado-vt-vm1;virsh start --console avocado-vt-vm1 (guest xml 
sosreport attached)
  Guest crashes while booting

  2019-02-28 10:36:44.752+: starting up libvirt version: 4.0.0, package: 
1ubuntu8.6 (Christian Ehrhardt  Fri, 09 Nov 
2018 07:42:01 +0100), qemu version: 2.11.1(Debian 
1:2.11+dfsg-1ubuntu7.8-1ibm3), hostname: cs-host-f37-ac922-3.pok.ibm.com
  LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 
QEMU_AUDIO_DRV=none /usr/bin/qemu-system-ppc64 -name 
guest=avocado-vt-vm1,debug-threads=on -S -object 
secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-15-avocado-vt-vm1/master-key.aes
 -machine pseries-2.11,accel=kvm,usb=off,dump-guest-core=off -m 264192 
-realtime mlock=off -smp 256,sockets=256,cores=1,threads=1 -uuid 
f4e14f88-bf1b-4cc3-b6d6-958d514d6c18 -display none -no-user-config -nodefaults 
-chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-15-avocado-vt-vm1/monitor.sock,server,nowait
 -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown 
-boot strict=on -device qemu-xhci,id=usb,bus=pci.0,addr=0x3 -device 
virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x2 -device 
virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive 
file=/home/sath/avocado-fvt-wrapper/data/avocado-vt/images/rhel76-ppc64le.qcow2,format=qcow2,if=none,id=drive-scsi0-0-0-0
 -device 
scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1
 -netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=30 -device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:fc:fd:fe,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -chardev 
socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-15-avocado-vt-vm1/org.qemu.guest_agent.0,server,nowait
 -device 
virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0
 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on
  2019-02-28 10:36:44.759+: 19598: info : libvirt version: 4.0.0, package: 
1ubuntu8.6 (Christian Ehrhardt  Fri, 09 Nov 
2018 07:42:01 +0100)
  2019-02-28 10:36:44.759+: 19598: info : hostname: cs-host-f37-ac922-3
  2019-02-28 10:36:44.759+: 19598: info : virObjectUnref:350 : 
OBJECT_UNREF: obj=0x76d594111710
  2019-02-28T10:36:44.781703Z qemu-system-ppc64: -chardev pty,id=charserial0: 
char device redirected to /dev/pts/3 (label charserial0)
  2019-02-28T10:36:44.781945Z qemu-system-ppc64: warning: Number of SMP cpus 
requested (256) exceeds the recommended cpus supported by KVM (128)
  2019-02-28T10:36:44.781953Z qemu-system-ppc64: warning: Number of 
hotpluggable cpus requested (256) exceeds the recommended cpus supported by KVM 
(128)
  2019-02-28 10:37:18.060+: shutting down, reason=crashed
  2019-02-28T10:37:18.071969Z qemu-system-ppc64: terminating on signal 15 from 
pid 14056 (/usr/sbin/libvirtd)

  *Additional Instructions for sathe...@in.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Satheesh Rajendran  - 2019-02-28 
04:51:45 ==
  Possible Upstream fix: 
https://git.kernel.org/pub/scm/linu

[Kernel-packages] [Bug 1804149] Re: Kernel panic, Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi]

2019-03-19 Thread Juerg Haefliger
Can you please test the test kernel at:
https://kernel.ubuntu.com/~juergh/lp1804149/

-- 
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/1804149

Title:
  Kernel panic,Oops: 0004 ilc:3 [#1] SMP,  iscsi_q_20 iscsi_xmitworker
  [libiscsi]

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Michael Finnegan  - 2018-11-19 14:14:40 
==
  ---Problem Description---
  Kernel panic,Oops: 0004 ilc:3 [#1] SMP,  iscsi_q_20 iscsi_xmitworker 
[libiscsi]
   
  ---uname output---
  Linux ilabg3 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 
s390x s390x s390x GNU/Linux
   
  Machine Type = IBM 3906 M05 7G4 (z/VM 7.1.0) 
   
  ---Debugger---
  A debugger is not configured
   
  Contact Information = Michael Finnegan/finne...@us.ibm.com 
   
  Stack trace output:
   dmesg.201811161956
  [1363037.322472] Unable to handle kernel pointer dereference in virtual 
kernel address space
  [1363037.322481] Failing address:  TEID: 0483
  [1363037.322483] Fault in home space mode while using kernel ASCE.
  [1363037.322486] AS:00ea0007 R3:f37d0007 S:f37ff000 
P:013d
  [1363037.322524] Oops: 0004 ilc:3 [#1] SMP
  [1363037.322529] Modules linked in: iptable_filter binfmt_misc 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache qeth_l3 qeth_l2 
s390_trng ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 
sha1_s390 sha_common qeth vmur ccwgroup vfio_ccw vfio_mdev mdev 
vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core sunrpc 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables 
dm_round_robin dm_service_time crc32_vx_s390 dasd_eckd_mod zfcp qdio 
scsi_transport_fc dasd_fba_mod dasd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua 
dm_multipath
  [1363037.322567] CPU: 3 PID: 37970 Comm: kworker/u128:19 Not tainted 
4.15.0-36-generic #39-Ubuntu
  [1363037.322573] Hardware name: IBM 3906 M05 7G4 (z/VM 7.1.0)
  [1363037.322581] Workqueue: iscsi_q_20 iscsi_xmitworker [libiscsi]
  [1363037.322583] Krnl PSW : c8051cf6 e49a28f4 
(__iscsi_get_task+0x6/0x18 [libiscsi])
  [1363037.322587]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 
PM:0 RI:0 EA:3
  [1363037.322589] Krnl GPRS:  02923ce0 
 0400
  [1363037.322591]03ff80277640 0008 
788efc00 03ff802777cc
  [1363037.322592]03ff8027769c  
 78ce8310
  [1363037.322594]f3689800 78ce83a2 
03ff80272e8e 02923c90
  [1363037.322601] Krnl Code: 03ff80272624: c0f4fcf6  brcl
15,3ff80272010
  03ff8027262a: c0f4377b  brcl
15,3ff80279520
 #03ff80272630: c004  brcl
0,3ff80272630
 >03ff80272636: eb012078006a  asi 
120(%r2),1
  03ff8027263c: c0f43772  brcl
15,3ff80279520
  03ff80272642: 0707  bcr 0,%r7
  03ff80272644: 0707  bcr 0,%r7
  03ff80272646: 0707  bcr 0,%r7
  [1363037.322618] Call Trace:
  [1363037.322621] ([<03ff80272ec6>] iscsi_xmit_task+0x86/0x138 [libiscsi])
  [1363037.322625]  [<03ff8027769c>] iscsi_data_xmit+0x44c/0x548 [libiscsi]
  [1363037.322636]  [<03ff802777cc>] iscsi_xmitworker+0x34/0x58 [libiscsi]
  [1363037.322642]  [<001918f2>] process_one_work+0x262/0x4d8
  [1363037.322644]  [<00191bc0>] worker_thread+0x58/0x4e8
  [1363037.322648]  [<00198d24>] kthread+0x14c/0x168
  [1363037.322652]  [<008e3eb2>] kernel_thread_starter+0xa/0x10
  [1363037.322654]  [<008e3ea8>] kernel_thread_starter+0x0/0x10
  [1363037.322655] Last Breaking-Event-Address:
  [1363037.322657]  [<03ff80272e88>] iscsi_xmit_task+0x48/0x138 [libiscsi]
  [1363037.322658]
  [1363037.322660] Kernel panic - not syncing: Fatal exception in interrupt

  
   
  Oops output:
Oops: 0004 ilc:3 [#1] SMP


  *Additional Instructions for Michael Finnegan/finne...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1804149/+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 1820872] [NEW] Xenial: Sync to upstream v4.9

2019-03-19 Thread Juerg Haefliger
Public bug reported:

== SRU Justification ==

Reduce the delta between Xenial 4.4 and upstream stable 4.9 in the
Spectre-related areas.

== Regression Potential ==

Low. These are cosmetic cleanups (non-functional changes) and backports
of low-risk commits that have been in upstream stable for quite a while
already.

== Fix ==

Backport the relevant commits.

== Test Case ==

TBD.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Xenial)
 Importance: Undecided
 Status: Confirmed

** Description changed:

  == SRU Justification ==
  
  Reduce the delta between Xenial 4.4 and upstream stable 4.9 in the
  Spectre-related areas.
  
- == Regression potiential ==
+ == Regression Potential ==
  
  Low. These are cosmetic cleanups (non-functional changes) and backports
  of low-risk commits that have been in upstream stable for quite a while
  already.
  
  == Fix ==
  
  Backport the relevant commits.
  
- == Test case ==
+ == Test Case ==
  
  TBD.

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Xenial)
   Status: Confirmed => Triaged

** Changed in: linux (Ubuntu Xenial)
   Status: Triaged => Confirmed

-- 
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/1820872

Title:
  Xenial: Sync to upstream v4.9

Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  Confirmed

Bug description:
  == SRU Justification ==

  Reduce the delta between Xenial 4.4 and upstream stable 4.9 in the
  Spectre-related areas.

  == Regression Potential ==

  Low. These are cosmetic cleanups (non-functional changes) and
  backports of low-risk commits that have been in upstream stable for
  quite a while already.

  == Fix ==

  Backport the relevant commits.

  == Test Case ==

  TBD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820872/+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 1815061] Re: linux-ibm-gt: 4.15.0-1016.18 -proposed tracker

2019-03-21 Thread Juerg Haefliger
*** This bug is a duplicate of bug 1819701 ***
https://bugs.launchpad.net/bugs/1819701

** This bug has been marked a duplicate of bug 1819701
   linux-ibm-gt: 4.15.0-1017.19 -proposed tracker

-- 
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/1815061

Title:
  linux-ibm-gt: 4.15.0-1016.18 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug is for tracking the 4.15.0-1016.18 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814726
  phase: Ready for Testing
  phase-changed: Sunday, 03. March 2019 06:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1815061/+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 1811850] Re: linux-ibm-gt: 4.15.0-1015.17 -proposed tracker

2019-03-21 Thread Juerg Haefliger
*** This bug is a duplicate of bug 1819701 ***
https://bugs.launchpad.net/bugs/1819701

** This bug is no longer a duplicate of bug 1815061
   linux-ibm-gt: 4.15.0-1016.18 -proposed tracker
** This bug has been marked a duplicate of bug 1819701
   linux-ibm-gt: 4.15.0-1017.19 -proposed tracker

-- 
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/1811850

Title:
  linux-ibm-gt: 4.15.0-1015.17 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.15.0-1015.17 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  phase: Testing
  phase-changed: Monday, 28. January 2019 18:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811850/+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 1819701] Re: linux-ibm-gt: 4.15.0-1018.20 -proposed tracker

2019-03-26 Thread Juerg Haefliger
** Summary changed:

- linux-ibm-gt: 4.15.0-1017.19 -proposed tracker
+ linux-ibm-gt: 4.15.0-1018.20 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Fix Released => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: Fix Released => In Progress

-- 
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/1819701

Title:
  linux-ibm-gt: 4.15.0-1018.20 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  Incomplete
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Packaging
  phase-changed: Tuesday, 26. March 2019 10:39 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
promote-to-proposed: Stalled -- packages no longer available

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819701/+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 1819701] Re: linux-ibm-gt: 4.15.0-1018.20 -proposed tracker

2019-03-27 Thread Juerg Haefliger
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Incomplete => New

-- 
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/1819701

Title:
  linux-ibm-gt: 4.15.0-1018.20 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 27. March 2019 14:08 UTC
  reason:
promote-to-proposed: Pending -- ready for review

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819701/+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 1822760] [NEW] Bionic: Sync to Xenial (Spectre)

2019-04-02 Thread Juerg Haefliger
Public bug reported:

== SRU Justification ==

There are a couple of Spectre related commits in Xenial that never
landed in Bionic. Fix that to prevent a regression when upgrading from
Xenial to Bionic.

== Regression Potential ==

Low. These are not very intrusive commits that have been in upstream for
quite a while.

== Fix ==

Backport the relevant commits from upstream.

== Test Case ==

TBD.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Status: Incomplete


** Tags: xenial

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Summary changed:

- Bionic: Sync to Xenial
+ Bionic: Sync to Xenial (Spectre)

-- 
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/1822760

Title:
  Bionic: Sync to Xenial (Spectre)

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  == SRU Justification ==

  There are a couple of Spectre related commits in Xenial that never
  landed in Bionic. Fix that to prevent a regression when upgrading from
  Xenial to Bionic.

  == Regression Potential ==

  Low. These are not very intrusive commits that have been in upstream
  for quite a while.

  == Fix ==

  Backport the relevant commits from upstream.

  == Test Case ==

  TBD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822760/+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 1820872] Re: Xenial: Sync to upstream v4.9 (Spectre)

2019-04-02 Thread Juerg Haefliger
** Summary changed:

- Xenial: Sync to upstream v4.9
+ Xenial: Sync to upstream v4.9 (Spectre)

-- 
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/1820872

Title:
  Xenial: Sync to upstream v4.9 (Spectre)

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Confirmed

Bug description:
  == SRU Justification ==

  Reduce the delta between Xenial 4.4 and upstream stable 4.9 in the
  Spectre-related areas.

  == Regression Potential ==

  Low. These are cosmetic cleanups (non-functional changes) and
  backports of low-risk commits that have been in upstream stable for
  quite a while already.

  == Fix ==

  Backport the relevant commits.

  == Test Case ==

  TBD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820872/+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 1822760] Re: Bionic: Sync to Xenial (Spectre)

2019-04-02 Thread Juerg Haefliger
** Changed in: linux (Ubuntu Bionic)
   Status: Incomplete => Confirmed

-- 
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/1822760

Title:
  Bionic: Sync to Xenial (Spectre)

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Confirmed

Bug description:
  == SRU Justification ==

  There are a couple of Spectre related commits in Xenial that never
  landed in Bionic. Fix that to prevent a regression when upgrading from
  Xenial to Bionic.

  == Regression Potential ==

  Low. These are not very intrusive commits that have been in upstream
  for quite a while.

  == Fix ==

  Backport the relevant commits from upstream.

  == Test Case ==

  TBD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822760/+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 1711056] Re: Backport more recent Broadcom bnxt_en driver

2019-06-13 Thread Juerg Haefliger
** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

-- 
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/1711056

Title:
  Backport more recent Broadcom bnxt_en driver

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  The current Xenial bnxt_en driver only supports a limited (old) set of
  Broadcom NICs. We want to support newer NICs in Xenial without adding
  risk for existing users.

  The plan is to provide a separate driver called bnxt_en_bpo which is a
  backported driver from Broadcom. This driver will be modified to only
  support the new NICs that the current kernel driver does not support
  so that they both can co-exist.

  In other words, NICs that used to be supported by Xenial will still be
  managed by the current (unmodified) bnxt_en driver. Newer NICs will be
  managed by the new bnxt_en_bpo driver.

  [Test Case]

  Due to the unavailability of Broadcom HW, the only test that was run
  was to manually load both the bnxt_en and bnxt_en_bpo module to ensure
  that they can co-exist.

  [Regression Potential]

  There should be no regression potential, since the current driver is
  not modified and the new driver only loads for NICs that are not
  handled by the current driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711056/+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 1813532] Re: x86/mm: Found insecure W+X mapping at address (ptrval)/0xc00a0000

2019-06-13 Thread Juerg Haefliger
** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

-- 
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/1813532

Title:
  x86/mm: Found insecure W+X mapping at address (ptrval)/0xc00a

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  == SRU Justification ==

  Booting an i386 Bionic kernel in a VM with a 64-bit CPU leads to:

  [1.074702] Freeing unused kernel memory: 1092K
  [1.084027] Write protecting the kernel text: 8836k
  [1.085115] Write protecting the kernel read-only data: 3480k
  [1.086361] NX-protecting the kernel data: 7548k
  [1.087457] [ cut here ]
  [1.088400] x86/mm: Found insecure W+X mapping at address 
(ptrval)/0xc00a
  [1.089738] WARNING: CPU: 0 PID: 1 at 
/build/linux-bnzN1b/linux-4.15.0/arch/x86/mm/dump_pagetables.c:266 
note_page+0x670/0x860
  [1.091893] Modules linked in:
  [1.092522] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.0-43-generic 
#46-Ubuntu
  [1.094362] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.11.1-1ubuntu1 04/01/2014
  [1.096279] EIP: note_page+0x670/0x860
  [1.097012] EFLAGS: 00010282 CPU: 0
  [1.097807] EAX: 0041 EBX: df4fbf44 ECX: 01ba EDX: 
  [1.099083] ESI: 8000 EDI:  EBP: df4fbf10 ESP: df4fbee4
  [1.100328]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [1.101418] CR0: 80050033 CR2: b7d99092 CR3: 0ce16000 CR4: 06f0
  [1.102693] DR0:  DR1:  DR2:  DR3: 
  [1.103928] DR6: fffe0ff0 DR7: 0400
  [1.104733] Call Trace:
  [1.105316]  ptdump_walk_pgd_level_core+0x2ac/0x2e0
  [1.106266]  ptdump_walk_pgd_level_checkwx+0x18/0x20
  [1.107207]  mark_rodata_ro+0xf5/0x117
  [1.107947]  ? rest_init+0xa0/0xa0
  [1.108627]  kernel_init+0x33/0xf0
  [1.109300]  ret_from_fork+0x2e/0x38
  [1.110016] Code: cc e9 0c fb ff ff f7 c6 00 10 00 00 74 8c 68 fe ae ae cc 
e9 16 fe ff ff 52 52 68 ac af ae cc c6 05 a8 a8 cb cc 01 e8 40 74 00 00 <0f> 0b 
8b 53 0c 83 c4 0c e9 38 fa ff ff 50 6a 08 52 6a 08 68 ae
  [1.113395] ---[ end trace 0dce1996d96c40bb ]---
  [1.114324] x86/mm: Checked W+X mappings: FAILED, 96 W+X pages found.

  
  == Fix ==

  Backport commit c200dac78fec ("x86/mm: Do not warn about PCI BIOS W+X
  mappings").

  
  == Regression Potential ==

  Low. The patch only modifies debugging output.

  
  == Test Case ==

  To reproduce, boot an i386 kernel in QEMU with '-cpu qemu64' and check
  the kernel logs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813532/+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 1820872] Re: Xenial: Sync to upstream v4.9 (Spectre)

2019-06-13 Thread Juerg Haefliger
** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

-- 
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/1820872

Title:
  Xenial: Sync to upstream v4.9 (Spectre)

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  == SRU Justification ==

  Reduce the delta between Xenial 4.4 and upstream stable 4.9 in the
  Spectre-related areas.

  == Regression Potential ==

  Low. These are cosmetic cleanups (non-functional changes) and
  backports of low-risk commits that have been in upstream stable for
  quite a while already.

  == Fix ==

  Backport the relevant commits.

  == Test Case ==

  TBD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820872/+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 1775137] Re: Prevent speculation on user controlled pointer

2019-06-13 Thread Juerg Haefliger
** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

-- 
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/1775137

Title:
  Prevent speculation on user controlled pointer

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  == SRU Justification ==
  Upstream's Spectre v1 mitigation prevents speculation on a user controlled 
pointer. This part of the Spectre v1 patchset was never backported to 4.4 (for 
unknown reasons) so Xenial/Trusty/Precise are lacking it as well. All the other 
stable upstream kernels include it, so add it to our older kernels.

  == Fix ==
  Backport the following patches:
  x86/uaccess: Use __uaccess_begin_nospec() and uaccess_try_nospec
  x86/usercopy: Replace open coded stac/clac with __uaccess_{begin, end}
  x86: Introduce __uaccess_begin_nospec() and uaccess_try_nospec

  == Regression Potential ==
  Low. Patches have been in upstream (and other distro kernels) for quite a 
while now and the changes only introduce a barrier on copy_from_user operations.

  == Test Case ==
  TBD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775137/+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 1789215] Re: i40e NIC not recognized

2019-06-13 Thread Juerg Haefliger
** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

-- 
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/1789215

Title:
  i40e NIC not recognized

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Released

Bug description:
  == SRU Justification ==

  Booting Trusty with kernel 3.13.0-156-generic on a fairly new Intel
  box with a i40e NIC results in no network. The 3.13 i40e driver
  doesn't support the following HW:

  3d:00.0 Ethernet controller: Intel Corporation Device 37d2 (rev 02)
  Subsystem: Intel Corporation Device 35ce
  Flags: bus master, fast devsel, latency 0, IRQ 37
  Memory at ac00 (64-bit, prefetchable) [size=16M]
  Memory at ad808000 (64-bit, prefetchable) [size=32K]
  Expansion ROM at ad98 [disabled] [size=512K]
  Capabilities: 

  Base Board Information
  Manufacturer: Intel Corporation
  Product Name: S2600WFT

  This is a Canonical test system and having functional networking with
  a Trusty kernel would help with - well - testing :-)

  == Fix ==

  Add a backport driver in addition to the in-tree driver that supports
  newer versions of the i40e NIC.

  == Regression Potential ==

  Low. The new driver will only load for NICs that are not supported by
  the current in-tree driver.

  == Test Case ==

  Boot a patched kernel and verify the NIC is recognized and the network
  comes up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789215/+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 1818815] Re: Xenial update: 4.4.176 upstream stable release

2019-06-13 Thread Juerg Haefliger
** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

-- 
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/1818815

Title:
  Xenial update: 4.4.176 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 4.4.176 upstream stable release
 from git://git.kernel.org/

  
  Linux 4.4.176
  KVM: VMX: Fix x2apic check in vmx_msr_bitmap_mode()
  ax25: fix possible use-after-free
  mISDN: fix a race in dev_expire_timer()
  net/x25: do not hold the cpu too long in x25_new_lci()
  mfd: as3722: Mark PM functions as __maybe_unused
  mfd: as3722: Handle interrupts on suspend
  kvm: fix kvm_ioctl_create_device() reference counting (CVE-2019-6974)
  x86: livepatch: Treat R_X86_64_PLT32 as R_X86_64_PC32
  net: ipv4: use a dedicated counter for icmp_v4 redirect packets
  net: stmmac: Fix a race in EEE enable callback
  vxlan: test dev->flags & IFF_UP before calling netif_rx()
  tcp: clear icsk_backoff in tcp_write_queue_purge()
  net: Do not allocate page fragments that are not skb aligned
  tcp: tcp_v4_err() should be more careful
  net: Add header for usage of fls64()
  sky2: Increase D3 delay again
  net: Fix for_each_netdev_feature on Big endian
  hwmon: (lm80) Fix missing unlock on error in set_fan_div()
  vsock: cope with memory allocation failure at socket creation time
  net: fix IPv6 prefix route residue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818815/+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 1818806] Re: Xenial update: 4.4.174 upstream stable release

2019-06-13 Thread Juerg Haefliger
** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

-- 
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/1818806

Title:
  Xenial update: 4.4.174 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 4.4.174 upstream stable release
 from git://git.kernel.org/

  
  Linux 4.4.174
  rcu: Force boolean subscript for expedited stall warnings
  net: ipv4: do not handle duplicate fragments as overlapping
  net: fix pskb_trim_rcsum_slow() with odd trim offset
  inet: frags: better deal with smp races
  ipv4: frags: precedence bug in ip_expire()
  ip: frags: fix crash in ip_do_fragment()
  ip: process in-order fragments efficiently
  ip: add helpers to process in-order fragments faster.
  ip: use rb trees for IP frag queue.
  net: pskb_trim_rcsum() and CHECKSUM_COMPLETE are friends
  ipv6: defrag: drop non-last frags smaller than min mtu
  net: modify skb_rbtree_purge to return the truesize of all purged skbs.
  ip: discard IPv4 datagrams with overlapping segments.
  inet: frags: fix ip6frag_low_thresh boundary
  inet: frags: get rid of ipfrag_skb_cb/FRAG_CB
  inet: frags: reorganize struct netns_frags
  rhashtable: reorganize struct rhashtable layout
  ipv6: frags: rewrite ip6_expire_frag_queue()
  inet: frags: do not clone skb in ip_expire()
  inet: frags: break the 2GB limit for frags storage
  inet: frags: remove inet_frag_maybe_warn_overflow()
  inet: frags: get rif of inet_frag_evicting()
  inet: frags: remove some helpers
  ipfrag: really prevent allocation on netns exit
  net: ieee802154: 6lowpan: fix frag reassembly
  inet: frags: use rhashtables for reassembly units
  rhashtable: add schedule points
  rhashtable: Add rhashtable_lookup()
  rhashtable: add rhashtable_lookup_get_insert_key()
  inet: frags: refactor lowpan_net_frag_init()
  inet: frags: refactor ipv6_frag_init()
  inet: frags: refactor ipfrag_init()
  inet: frags: add a pointer to struct netns_frags
  inet: frags: change inet_frags_init_net() return value

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818806/+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 1818813] Re: Xenial update: 4.4.175 upstream stable release

2019-06-13 Thread Juerg Haefliger
** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

-- 
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/1818813

Title:
  Xenial update: 4.4.175 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 4.4.175 upstream stable release
 from git://git.kernel.org/

  
  Linux 4.4.175
  uapi/if_ether.h: move __UAPI_DEF_ETHHDR libc define
  pinctrl: msm: fix gpio-hog related boot issues
  usb: dwc2: Remove unnecessary kfree
  kaweth: use skb_cow_head() to deal with cloned skbs
  ch9200: use skb_cow_head() to deal with cloned skbs
  smsc95xx: Use skb_cow_head to deal with cloned skbs
  dm thin: fix bug where bio that overwrites thin block ignores FUA
  x86/a.out: Clear the dump structure initially
  signal: Restore the stop PTRACE_EVENT_EXIT
  x86/platform/UV: Use efi_runtime_lock to serialise BIOS calls
  tracing/uprobes: Fix output for multiple string arguments
  alpha: Fix Eiger NR_IRQS to 128
  alpha: fix page fault handling for r16-r18 targets
  Input: elantech - enable 3rd button support on Fujitsu CELSIUS H780
  Input: bma150 - register input device after setting private data
  ALSA: usb-audio: Fix implicit fb endpoint setup by quirk
  ALSA: hda - Add quirk for HP EliteBook 840 G5
  perf/core: Fix impossible ring-buffer sizes warning
  Input: elan_i2c - add ACPI ID for touchpad in Lenovo V330-15ISK
  Revert "Input: elan_i2c - add ACPI ID for touchpad in ASUS Aspire F5-573G"
  Documentation/network: reword kernel version reference
  cifs: Limit memory used by lock request calls to a page
  gpio: pl061: handle failed allocations
  ARM: dts: kirkwood: Fix polarity of GPIO fan lines
  ARM: dts: da850-evm: Correct the sound card name
  uapi/if_ether.h: prevent redefinition of struct ethhdr
  Revert "exec: load_script: don't blindly truncate shebang string"
  batman-adv: Force mac header to start of data on xmit
  batman-adv: Avoid WARN on net_device without parent in netns
  xfrm: refine validation of template and selector families
  libceph: avoid KEEPALIVE_PENDING races in ceph_con_keepalive()
  Revert "cifs: In Kconfig CONFIG_CIFS_POSIX needs depends on legacy (insecure 
cifs)"
  NFC: nxp-nci: Include unaligned.h instead of access_ok.h
  HID: debug: fix the ring buffer implementation
  drm/vmwgfx: Return error code from vmw_execbuf_copy_fence_user
  drm/vmwgfx: Fix setting of dma masks
  drm/modes: Prevent division by zero htotal
  mac80211: ensure that mgmt tx skbs have tailroom for encryption
  ARM: iop32x/n2100: fix PCI IRQ mapping
  MIPS: VDSO: Include $(ccflags-vdso) in o32,n32 .lds builds
  MIPS: OCTEON: don't set octeon_dma_bar_type if PCI is disabled
  mips: cm: reprime error cause
  debugfs: fix debugfs_rename parameter checking
  misc: vexpress: Off by one in vexpress_syscfg_exec()
  signal: Better detection of synchronous signals
  signal: Always notice exiting tasks
  mtd: rawnand: gpmi: fix MX28 bus master lockup problem
  perf tests evsel-tp-sched: Fix bitwise operator
  perf/core: Don't WARN() for impossible ring-buffer sizes
  x86/MCE: Initialize mce.bank in the case of a fatal error in mce_no_way_out()
  perf/x86/intel/uncore: Add Node ID mask
  KVM: nVMX: unconditionally cancel preemption timer in free_nested 
(CVE-2019-7221)
  KVM: x86: work around leak of uninitialized stack contents (CVE-2019-7222)
  usb: gadget: udc: net2272: Fix bitwise and boolean operations
  usb: phy: am335x: fix race condition in _probe
  dmaengine: imx-dma: fix wrong callback invoke
  fuse: handle zero sized retrieve correctly
  fuse: decrement NR_WRITEBACK_TEMP on the right page
  fuse: call pipe_buf_release() under pipe lock
  ALSA: hda - Serialize codec registrations
  ALSA: compress: Fix stop handling on compressed capture streams
  net: dsa: slave: Don't propagate flag changes on down slave interfaces
  net: systemport: Fix WoL with password after deep sleep
  skge: potential memory corruption in skge_get_regs()
  net: dp83640: expire old TX-skb
  enic: fix checksum validation for IPv6
  dccp: fool proof ccid_hc_[rt]x_parse_options()
  string: drop __must_check from strscpy() and restore strscpy() usages in 
cgroup
  tipc: use destination length for copy string
  test_hexdump: use memcpy instead of strncpy
  thermal: hwmon: inline helpers when CONFIG_THERMAL_HWMON is not set
  exec: load_script: don't blindly trunca

[Kernel-packages] [Bug 1755817] Re: Segmentation fault in ldt_gdt_64

2019-06-13 Thread Juerg Haefliger
** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

-- 
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/1755817

Title:
  Segmentation fault in ldt_gdt_64

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Released

Bug description:
  == SRU Justification ==
  The ldt_gdt_64 x86 selftest segfaults with the currently released Trusty 3.13 
kernel. The commit that introduced the segfault is aeb315d60afe ("x86/ldt: Make 
modify_ldt synchronous").

  == Fix ==
  Upstream commit 8ff5bd2e1e27 ("x86/signal/64: Fix SS if needed when 
delivering a 64-bit signal"). This commit was found by doing a reverse git 
bisect of the upstream kernel (i.e., when did the test stop segfaulting).
  The backport of the commit is a simple context adjustment. The second commit 
is a pre-requisite which simply renames some defines (no functional changes).

  == Regression Potential ==
  Low. The commit is very small and isolated and the code path is only executed 
in special circumstances (and for x86 only). I built a test kernel and ran the 
whole set of x86 selftests and perf NMI test for several hours to verify 
stability.

  == Test Case ==
  Run the ldt_gdt_64 x86 selftets from a current upstream kernel source. The 
test segfaults consistently.

  Original bug description:

  Trusty 3.13 segfaults when running ldt_gdt_64 from the kernel's x86
  selftests.

  git bisect revealed that the following commit introduced the issue:

  commit aeb315d60afee129d32558f4a4b356eec2e7da7b
  Author: Andy Lutomirski 
  Date:   Thu Jul 30 14:31:32 2015 -0700

  x86/ldt: Make modify_ldt synchronous

  CVE-2017-5754

  commit 37868fe113ff2ba814b3b4eb12df214df555f8dc upstream.

  modify_ldt() has questionable locking and does not synchronize
  threads.  Improve it: redesign the locking and synchronize all
  threads' LDTs using an IPI on all modifications.

  This will dramatically slow down modify_ldt in multithreaded
  programs, but there shouldn't be any multithreaded programs that
  care about modify_ldt's performance in the first place.

  This fixes some fallout from the CVE-2015-5157 fixes.

  Signed-off-by: Andy Lutomirski 
  Reviewed-by: Borislav Petkov 
  Cc: Andrew Cooper 
  Cc: Andy Lutomirski 
  Cc: Boris Ostrovsky 
  Cc: Borislav Petkov 
  Cc: Brian Gerst 
  Cc: Denys Vlasenko 
  Cc: H. Peter Anvin 
  Cc: Jan Beulich 
  Cc: Konrad Rzeszutek Wilk 
  Cc: Linus Torvalds 
  Cc: Peter Zijlstra 
  Cc: Sasha Levin 
  Cc: Steven Rostedt 
  Cc: Thomas Gleixner 
  Link: 
http://lkml.kernel.org/r/4c6978476782160600471bd865b318db34c7b628.1438291540.git.l...@kernel.org
  Signed-off-by: Ingo Molnar 
  Signed-off-by: Jiri Slaby 
  (cherry picked from commit 62fc7228f8cc8c89ecbd37008a0495ac28e41c5c)
  Signed-off-by: Juerg Haefliger 
  Signed-off-by: Stefan Bader 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755817/+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 973536] Re: kvm brings Oneiric host to a grinding halt

2019-06-13 Thread Juerg Haefliger
** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

-- 
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/973536

Title:
  kvm brings Oneiric host to a grinding halt

Status in linux package in Ubuntu:
  Invalid
Status in qemu-kvm package in Ubuntu:
  Confirmed

Bug description:
  I'm running a Windows7 guest in KVM via libvirt/virt-manager on a
  Oneiric desktop 64-bit. Every once in a while (2-3 times a week,
  sometimes daily) the CPU usage goes berserk and the host becomes very
  unresponsive and unusable. This also happened once with a Breezy guest
  so it's not strictly a Windows issue. I'm just seeing it more often
  with Windows because that's what I run daily.

  More information attached, let me know what other info I should collect, the 
next time the machine is in that state.
  --- 
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 11.10
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  KvmCmdLine:
   UIDPID  PPID  CSZ   RSS PSR STIME TTY  TIME CMD
   116   2892 1 13 327807 1062024 0 07:34 ?   00:49:31 /usr/bin/kvm 
-S -M pc-0.14 -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name 
Windows7 -uuid 63a736b8-2d14-4354-8974-83c3f0d71ea1 -nodefconfig -nodefaults 
-chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/Windows7.monitor,server,nowait 
-mon chardev=charmonitor,id=monitor,mode=readline -rtc base=localtime -boot c 
-drive 
file=/home/juergh/VirtualMachines/Windows7.img,if=none,id=drive-virtio-disk0,boot=on,format=raw,cache=none,aio=native
 -device 
virtio-blk-pci,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0 
-netdev tap,fd=19,id=hostnet0 -device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:56:6f:49,bus=pci.0,addr=0x3 
-chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 
-usb -vnc 127.0.0.1:0 -vga std -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5
  MachineType: Hewlett-Packard HP EliteBook 8530w
  NonfreeKernelModules: nvidia
  Package: qemu-kvm 0.14.1+noroms-0ubuntu6.2
  PackageArchitecture: amd64
  PccardctlIdent:
   Socket 0:
 product info: "RICOH", "Bay8Controller", "", ""
 manfid: 0x, 0x
 function: 254 (unknown)
  PccardctlStatus:
   Socket 0:
 3.3V 16-bit PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-17-generic 
root=UUID=076a3371-4882-4e13-a456-9855c6fb4caf ro
  ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22
  Tags:  oneiric running-unity
  Uname: Linux 3.0.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin mock plugdev sambashare
  dmi.bios.date: 12/08/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PDV Ver. F.11
  dmi.board.name: 30E7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 90.26
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PDVVer.F.11:bd12/08/2009:svnHewlett-Packard:pnHPEliteBook8530w:pvrF.11:rvnHewlett-Packard:rn30E7:rvrKBCVersion90.26:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8530w
  dmi.product.version: F.11
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/973536/+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 1830176] Re: Xenial update: 4.4.180 upstream stable release

2019-06-13 Thread Juerg Haefliger
** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

-- 
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/1830176

Title:
  Xenial update: 4.4.180 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 4.4.180 upstream stable release
 from git://git.kernel.org/

  
  Linux 4.4.180
  powerpc/lib: fix book3s/32 boot failure due to code patching
  powerpc/booke64: set RI in default MSR
  drivers/virt/fsl_hypervisor.c: prevent integer overflow in ioctl
  drivers/virt/fsl_hypervisor.c: dereferencing error pointers in ioctl
  bonding: fix arp_validate toggling in active-backup mode
  ipv4: Fix raw socket lookup for local traffic
  vrf: sit mtu should not be updated when vrf netdev is the link
  vlan: disable SIOCSHWTSTAMP in container
  packet: Fix error path in packet_init
  net: ucc_geth - fix Oops when changing number of buffers in the ring
  bridge: Fix error path for kobject_init_and_add()
  powerpc/64s: Include cpu header
  USB: serial: fix unthrottle races
  USB: serial: use variable for status
  x86/bugs: Change L1TF mitigation string to match upstream
  x86/speculation/mds: Fix documentation typo
  Documentation: Correct the possible MDS sysfs values
  x86/mds: Add MDSUM variant to the MDS documentation
  x86/speculation/mds: Add 'mitigations=' support for MDS
  x86/speculation: Support 'mitigations=' cmdline option
  cpu/speculation: Add 'mitigations=' cmdline option
  x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off
  x86/speculation/mds: Fix comment
  x86/speculation/mds: Add SMT warning message
  x86/speculation: Move arch_smt_update() call to after mitigation decisions
  x86/cpu/bugs: Use __initconst for 'const' init data
  Documentation: Add MDS vulnerability documentation
  Documentation: Move L1TF to separate directory
  x86/speculation/mds: Add mitigation mode VMWERV
  x86/speculation/mds: Add sysfs reporting for MDS
  x86/speculation/l1tf: Document l1tf in sysfs
  x86/speculation/mds: Add mitigation control for MDS
  x86/speculation/mds: Conditionally clear CPU buffers on idle entry
  x86/speculation/mds: Clear CPU buffers on exit to user
  x86/speculation/mds: Add mds_clear_cpu_buffers()
  x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests
  x86/speculation/mds: Add BUG_MSBDS_ONLY
  x86/speculation/mds: Add basic bug infrastructure for MDS
  x86/speculation: Consolidate CPU whitelists
  x86/msr-index: Cleanup bit defines
  kvm: x86: Report STIBP on GET_SUPPORTED_CPUID
  x86/speculation: Provide IBPB always command line options
  x86/speculation: Add seccomp Spectre v2 user space protection mode
  x86/speculation: Enable prctl mode for spectre_v2_user
  x86/speculation: Add prctl() control for indirect branch speculation
  x86/speculation: Prevent stale SPEC_CTRL msr content
  x86/speculation: Prepare arch_smt_update() for PRCTL mode
  x86/speculation: Split out TIF update
  x86/speculation: Prepare for conditional IBPB in switch_mm()
  x86/speculation: Avoid __switch_to_xtra() calls
  x86/process: Consolidate and simplify switch_to_xtra() code
  x86/speculation: Prepare for per task indirect branch speculation control
  x86/speculation: Add command line control for indirect branch speculation
  x86/speculation: Unify conditional spectre v2 print functions
  x86/speculataion: Mark command line parser data __initdata
  x86/speculation: Mark string arrays const correctly
  x86/speculation: Reorder the spec_v2 code
  x86/speculation: Rework SMT state change
  sched: Add sched_smt_active()
  x86/Kconfig: Select SCHED_SMT if SMP enabled
  x86/speculation: Reorganize speculation control MSRs update
  x86/speculation: Rename SSBD update functions
  x86/speculation: Disable STIBP when enhanced IBRS is in use
  x86/speculation: Move STIPB/IBPB string conditionals out of cpu_show_common()
  x86/speculation: Remove unnecessary ret variable in cpu_show_common()
  x86/speculation: Clean up spectre_v2_parse_cmdline()
  x86/speculation: Update the TIF_SSBD comment
  x86/speculation: Propagate information about RSB filling mitigation to sysfs
  x86/speculation: Enable cross-hyperthread spectre v2 STIBP mitigation
  x86/speculation: Apply IBPB more strictly to avoid cross-process data leak
  x86/mm: Use WRITE_ONCE() when setting PTEs
  KVM: x86: SVM: Call x86_spec_ctrl_set_guest/host() with interru

[Kernel-packages] [Bug 1777389] Re: Xenial update to 4.4.138 stable release

2019-06-13 Thread Juerg Haefliger
** Changed in: linux (Ubuntu)
   Status: Fix Committed => Invalid

-- 
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/1777389

Title:
  Xenial update to 4.4.138 stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The 4.4.138 upstream stable
 patch set is now available. It should be included in the Ubuntu
 kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.4.138 stable release shall be
  applied:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777389/+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 1776158] Re: Xenial update to 4.4.135 stable release

2019-06-13 Thread Juerg Haefliger
** Changed in: linux (Ubuntu)
   Status: Fix Committed => Invalid

-- 
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/1776158

Title:
  Xenial update to 4.4.135 stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree
     or a minimally backported form of that patch. The 4.4.135 upstream
     stable stable patch set is now available. It should be included
     in the Ubuntu kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the 4.4.135 stable release shall be
     applied:

* Linux 4.4.135
* Revert "vti4: Don't override MTU passed on link creation via IFLA_MTU"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776158/+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 1777063] Re: Xenial update to 4.4.137 stable release

2019-06-13 Thread Juerg Haefliger
** Changed in: linux (Ubuntu)
   Status: Fix Committed => Invalid

-- 
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/1777063

Title:
  Xenial update to 4.4.137 stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 4.4.137 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the 4.4.137 stable release shall be
  applied:

* Linux 4.4.137
* net: metrics: add proper netlink validation
* net: phy: broadcom: Fix bcm_write_exp()
* rtnetlink: validate attributes in do_setlink()
* team: use netdev_features_t instead of u32
* net/mlx4: Fix irq-unsafe spinlock usage
* qed: Fix mask for physical address in ILT entry
* packet: fix reserve calculation
* net: usb: cdc_mbim: add flag FLAG_SEND_ZLP
* net/packet: refine check for priv area size
* netdev-FAQ: clarify DaveM's position for stable backports
* isdn: eicon: fix a missing-check bug
* ipv4: remove warning in ip_recv_error
* ip6mr: only set ip6mr_table from setsockopt when ip6mr_new_table succeeds
* enic: set DMA mask to 47 bit
* dccp: don't free ccid2_hc_tx_sock struct in dccp_disconnect()
* bnx2x: use the right constant
* brcmfmac: Fix check for ISO3166 code
* drm: set FMODE_UNSIGNED_OFFSET for drm files
* xfs: fix incorrect log_flushed on fsync
* kconfig: Avoid format overflow warning from GCC 8.1
* mmap: relax file size limit for regular files
* mmap: introduce sane default mmap limits
* tpm: self test failure should not cause suspend to fail
* tpm: do not suspend/resume if power stays on

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777063/+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 1774181] Re: Update to upstream's implementation of Spectre v1 mitigation

2019-06-13 Thread Juerg Haefliger
** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

-- 
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/1774181

Title:
  Update to upstream's implementation of Spectre v1 mitigation

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Xenial/Trusty/Precise are currently lacking full support of upstream's
  Spectre v1 mitigation. Add the missing patches and merge them with
  Ubuntu's current implementation.

  == SRU Justification ==
  Ubuntu's Spectre v1 mitigation is based on the original embargoed patchset 
which introduced a barrier macro to prevent speculation beyond array boundaries 
for user controlled indices. What eventually landed in upstream is slightly 
different and uses a barrier macro in combination with a masking solution (plus 
syscall table and user pointer sanitation). During the updates to newer stable 
upstream versions, all those patches were skipped. After reviewing them, we 
want to bring them back and merge them with the current implementation which 
brings us back in sync with upstream stable.

  == Fix ==
  Add all the missing Spectre v1 patches from upstream stable 4.4.118 to 
4.4.131. Where appropriate, replace Ubuntu's additional barriers with the 
masking macro.

  == Regression Potential ==
  Low. The patches have been in upstream for quite a while now and we keep the 
speculation barriers that are currently in Ubuntu but not in upstream.

  == Test Case ==
  TBD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774181/+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 1776177] Re: Xenial update to 4.4.136 stable release

2019-06-13 Thread Juerg Haefliger
** Changed in: linux (Ubuntu)
   Status: Fix Committed => Invalid

-- 
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/1776177

Title:
  Xenial update to 4.4.136 stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree
     or a minimally backported form of that patch. The 4.4.136 upstream
     stable stable patch set is now available. It should be included
     in the Ubuntu kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

     The following patches from the 4.4.136 stable release shall be
     applied:

* Linux 4.4.136
* sparc64: Fix build warnings with gcc 7.
* mm: fix the NULL mapping case in __isolate_lru_page()
* fix io_destroy()/aio_complete() race
* Kbuild: change CC_OPTIMIZE_FOR_SIZE definition
* drm/i915: Disable LVDS on Radiant P845
* hwtracing: stm: fix build error on some arches
* stm class: Use vmalloc for the master map
* scsi: scsi_transport_srp: Fix shost to rport translation
* MIPS: prctl: Disallow FRE without FR with PR_SET_FP_MODE requests
* MIPS: ptrace: Fix PTRACE_PEEKUSR requests for 64-bit FGRs
* iio:kfifo_buf: check for uint overflow
* dmaengine: usb-dmac: fix endless loop in usb_dmac_chan_terminate_all()
* i2c: rcar: revoke START request early
* i2c: rcar: check master irqs before slave irqs
* i2c: rcar: don't issue stop when HW does it automatically
* i2c: rcar: init new messages in irq
* i2c: rcar: refactor setup of a msg
* i2c: rcar: remove spinlock
* i2c: rcar: remove unused IOERROR state
* i2c: rcar: rework hw init
* i2c: rcar: make sure clocks are on when doing clock calculation
* tcp: avoid integer overflows in tcp_rcv_space_adjust()
* irda: fix overly long udelay()
* ASoC: Intel: sst: remove redundant variable dma_dev_name
* rtlwifi: rtl8192cu: Remove variable self-assignment in rf.c
* cfg80211: further limit wiphy names to 64 bytes
* selinux: KASAN: slab-out-of-bounds in xattr_getsecurity
* tracing: Fix crash when freeing instances with event triggers
* Input: elan_i2c_smbus - fix corrupted stack
* Revert "ima: limit file hash setting by user to fix and log modes"
* xfs: detect agfl count corruption and reset agfl
* sh: New gcc support
* USB: serial: cp210x: use tcflag_t to fix incompatible pointer type
* powerpc/64s: Clear PCR on boot
* arm64: lse: Add early clobbers to some input/output asm operands

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776177/+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 1810806] Re: Bionic update: 4.4.163 upstream stable release

2019-06-13 Thread Juerg Haefliger
** Changed in: linux (Ubuntu)
   Status: New => Invalid

-- 
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/1810806

Title:
  Bionic update: 4.4.163 upstream stable release

Status in linux package in Ubuntu:
  Invalid

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 4.4.163 upstream stable release
 from git://git.kernel.org/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810806/+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 1818237] Re: Xenial update: 4.4.171 upstream stable release

2019-06-13 Thread Juerg Haefliger
** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

-- 
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/1818237

Title:
  Xenial update: 4.4.171 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     4.4.171 upstream stable release
     from git://git.kernel.org/

  Linux 4.4.171
  sunrpc: use-after-free in svc_process_common()
  ext4: fix a potential fiemap/page fault deadlock w/ inline_data
  crypto: cts - fix crash on short inputs
  i2c: dev: prevent adapter retries and timeout being set as minus value
  ACPI: power: Skip duplicate power resource references in _PRx
  PCI: altera: Move retrain from fixup to altera_pcie_host_init()
  PCI: altera: Rework config accessors for use without a struct pci_bus
  PCI: altera: Poll for link training status after retraining the link
  PCI: altera: Poll for link up status after retraining the link
  PCI: altera: Check link status before retrain link
  PCI: altera: Reorder read/write functions
  PCI: altera: Fix altera_pcie_link_is_up()
  slab: alien caches must not be initialized if the allocation of the alien 
cache failed
  USB: Add USB_QUIRK_DELAY_CTRL_MSG quirk for Corsair K70 RGB
  USB: storage: add quirk for SMI SM3350
  USB: storage: don't insert sane sense for SPC3+ when bad sense specified
  usb: cdc-acm: send ZLP for Telit 3G Intel based modems
  cifs: Fix potential OOB access of lock element array
  CIFS: Do not hide EINTR after sending network packets
  btrfs: tree-checker: Fix misleading group system information
  btrfs: tree-checker: Check level for leaves and nodes
  btrfs: Verify that every chunk has corresponding block group at mount time
  btrfs: Check that each block group has corresponding chunk at mount time
  btrfs: validate type when reading a chunk
  btrfs: tree-checker: Detect invalid and empty essential trees
  btrfs: tree-checker: Verify block_group_item
  btrfs: tree-check: reduce stack consumption in check_dir_item
  btrfs: tree-checker: use %zu format string for size_t
  btrfs: tree-checker: Add checker for dir item
  btrfs: tree-checker: Fix false panic for sanity test
  btrfs: tree-checker: Enhance btrfs_check_node output
  btrfs: Move leaf and node validation checker to tree-checker.c
  btrfs: Add checker for EXTENT_CSUM
  btrfs: Add sanity check for EXTENT_DATA when reading out leaf
  btrfs: Check if item pointer overlaps with the item itself
  btrfs: Refactor check_leaf function for later expansion
  btrfs: struct-funcs, constify readers
  Btrfs: fix emptiness check for dirtied extent buffers at check_leaf()
  Btrfs: memset to avoid stale content in btree leaf
  Btrfs: kill BUG_ON in run_delayed_tree_ref
  Btrfs: improve check_node to avoid reading corrupted nodes
  Btrfs: memset to avoid stale content in btree node block
  Btrfs: fix BUG_ON in btrfs_mark_buffer_dirty
  Btrfs: check btree node's nritems
  Btrfs: detect corruption when non-root leaf has zero item
  Btrfs: fix em leak in find_first_block_group
  Btrfs: check inconsistence between chunk and block group
  Btrfs: add validadtion checks for chunk loading
  btrfs: Enhance chunk validation check
  btrfs: cleanup, stop casting for extent_map->lookup everywhere
  ALSA: hda/realtek - Disable headset Mic VREF for headset mode of ALC225

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818237/+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 1818803] Re: Xenial update: 4.4.173 upstream stable release

2019-06-13 Thread Juerg Haefliger
** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

-- 
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/1818803

Title:
  Xenial update: 4.4.173 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The following upstream
 stable patches should be included in the Ubuntu kernel:

 4.4.173 upstream stable release
 from git://git.kernel.org/

  
  Linux 4.4.173
  fs: don't scan the inode cache before SB_BORN is set
  mm: migrate: don't rely on __PageMovable() of newpage after unlocking it
  drivers: core: Remove glue dirs from sysfs earlier
  cifs: Always resolve hostname before reconnecting
  mm, oom: fix use-after-free in oom_kill_process
  kernel/exit.c: release ptraced tasks before zap_pid_ns_processes
  mmc: sdhci-iproc: handle mmc_of_parse() errors during probe
  platform/x86: asus-nb-wmi: Drop mapping of 0x33 and 0x34 scan codes
  platform/x86: asus-nb-wmi: Map 0x35 to KEY_SCREENLOCK
  gfs2: Revert "Fix loop in gfs2_rbm_find"
  arm64: hyp-stub: Forbid kprobing of the hyp-stub
  ARM: cns3xxx: Fix writing to wrong PCI config registers after alignment
  fs/dcache: Fix incorrect nr_dentry_unused accounting in shrink_dcache_sb()
  CIFS: Do not count -ENODATA as failure for query directory
  l2tp: fix reading optional fields of L2TPv3
  l2tp: remove l2specific_len dependency in l2tp_core
  ucc_geth: Reset BQL queue when stopping device
  net/rose: fix NULL ax25_cb kernel panic
  netrom: switch to sock timer API
  net/mlx4_core: Add masking for a few queries on HCA caps
  l2tp: copy 4 more bytes to linear part if necessary
  ipv6: Consider sk_bound_dev_if when binding a socket to an address
  fs: add the fsnotify call to vfs_iter_write
  s390/smp: Fix calling smp_call_ipl_cpu() from ipl CPU
  Revert "loop: Fold __loop_release into loop_release"
  Revert "loop: Get rid of loop_index_mutex"
  Revert "loop: Fix double mutex_unlock(&loop_ctl_mutex) in 
loop_control_ioctl()"
  f2fs: read page index before freeing
  arm64: mm: remove page_mapping check in __sync_icache_dcache
  irqchip/gic-v3-its: Align PCI Multi-MSI allocation on their size
  perf unwind: Take pgoff into account when reporting elf to libdwfl
  perf unwind: Unwind with libdw doesn't take symfs into account
  vt: invoke notifier on screen size change
  can: bcm: check timer values before ktime conversion
  can: dev: __can_get_echo_skb(): fix bogous check for non-existing skb by 
removing it
  x86/kaslr: Fix incorrect i8254 outb() parameters
  KVM: x86: Fix single-step debugging
  Input: xpad - add support for SteelSeries Stratus Duo
  CIFS: Fix possible hang during async MTU reads and writes
  tty/n_hdlc: fix __might_sleep warning
  tty: Handle problem if line discipline does not have receive_buf
  staging: rtl8188eu: Add device code for D-Link DWA-121 rev B1
  char/mwave: fix potential Spectre v1 vulnerability
  s390/smp: fix CPU hotplug deadlock with CPU rescan
  s390/early: improve machine detection
  ARC: perf: map generic branches to correct hardware condition
  ASoC: atom: fix a missing check of snd_pcm_lib_malloc_pages
  USB: serial: pl2303: add new PID to support PL2303TB
  USB: serial: simple: add Motorola Tetra TPG2200 device id
  net: bridge: Fix ethernet header pointer before check skb forwardable
  net_sched: refetch skb protocol for each filter
  net: ipv4: Fix memory leak in network namespace dismantle
  openvswitch: Avoid OOB read when parsing flow nlattrs
  net: Fix usage of pskb_trim_rcsum

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818803/+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 1812086] Re: kernel BUG at /build/linux-vxxS7y/linux-4.15.0/mm/slub.c:296!

2019-06-13 Thread Juerg Haefliger
** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

-- 
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/1812086

Title:
  kernel BUG at /build/linux-vxxS7y/linux-4.15.0/mm/slub.c:296!

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Justification ==

  Rebooting an iSCSI target while the initiator is writing to a LUN
  leads to the following trace:

  [   59.879202] [ cut here ]
  [   59.879202] kernel BUG at /build/linux-vxxS7y/linux-4.15.0/mm/slub.c:296!
  [   59.880636] invalid opcode:  [#1] SMP PTI
  [   59.881569] Modules linked in: iscsi_target_mod target_core_pscsi 
target_core_file target_core_iblock target_core_user uio target_core_mod 
nls_iso8859_1 kvm_intel isofs kvm irqbypass joydev input_leds serio_raw 
sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp 
libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear psmouse virtio_blk virtio_net 
floppy
  [   59.891096] CPU: 0 PID: 1027 Comm: iscsi_np Not tainted 4.15.0-43-generic 
#46-Ubuntu
  [   59.892726] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.11.1-1ubuntu1 04/01/2014
  [   59.894606] RIP: 0010:kfree+0x16a/0x180
  [   59.895429] RSP: 0018:ac0d8050fe58 EFLAGS: 00010246
  [   59.896531] RAX: 9cf099475800 RBX: 9cf099475800 RCX: 
9cf099475800
  [   59.898083] RDX: 00011bbb RSI: 9cf09fc27140 RDI: 
9cf09f002000
  [   59.899627] RBP: ac0d8050fe70 R08:  R09: 
c07a329b
  [   59.901186] R10: e95780651d40 R11: a511dc90 R12: 
9cf099625600
  [   59.902769] R13: c07a329b R14: 9cf09ee07600 R15: 
9cf099475800
  [   59.904321] FS:  () GS:9cf09fc0() 
knlGS:
  [   59.906120] CS:  0010 DS:  ES:  CR0: 80050033
  [   59.907806] CR2: 7f7153b88470 CR3: 1babe000 CR4: 
06f0
  [   59.909376] DR0:  DR1:  DR2: 

  [   59.910950] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   59.913098] Call Trace:
  [   59.913783]  iscsi_target_login_sess_out+0x1fb/0x250 [iscsi_target_mod]
  [   59.915292]  iscsi_target_login_thread+0x44d/0x1060 [iscsi_target_mod]
  [   59.916775]  kthread+0x121/0x140
  [   59.917622]  ? iscsi_target_login_sess_out+0x250/0x250 [iscsi_target_mod]
  [   59.919244]  ? kthread_create_worker_on_cpu+0x70/0x70
  [   59.920483]  ? do_syscall_64+0x73/0x130
  [   59.921460]  ? SyS_exit_group+0x14/0x20
  [   59.922583]  ret_from_fork+0x35/0x40
  [   59.923523] Code: c4 80 74 04 41 8b 72 6c 4c 89 d7 e8 61 1c f9 ff eb 86 41 
b8 01 00 00 00 48 89 d9 48 89 da 4c 89 d6 e8 8b f6 ff ff e9 6d ff ff ff <0f> 0b 
48 8b 3d 6d c4 1c 01 e9 c9 fe ff ff 0f 1f 84 00 00 00 00
  [   59.927778] RIP: kfree+0x16a/0x180 RSP: ac0d8050fe58
  [   59.929063] ---[ end trace 082da4d341633d3e ]---

  == Fix ==

  Backport the following 3 commits:
   * scsi: iscsi: target: Fix conn_ops double free
   * scsi: iscsi: target: Set conn->sess to NULL when
     iscsi_login_set_conn_values fails
   * iscsi target: fix session creation failure handling

  == Regression Potential ==

  Low. Clean cherry-picks that modify a very isolated area.

  == Test ==

  Setup an iSCSI target using the scsi_target_user module and
  tcmu_runner. Setup an initiator to connect to the target and do IOs.
  Reboot the target. When the target comes back, the kernel falls over
  when the initiator tries to re-connect.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812086/+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 1795675] Re: kernel BUG at /build/linux-PygFzL/linux-3.13.0/kernel/timer.c:930!

2019-06-13 Thread Juerg Haefliger
** Changed in: linux (Ubuntu)
   Status: Triaged => Invalid

-- 
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/1795675

Title:
  kernel BUG at /build/linux-PygFzL/linux-3.13.0/kernel/timer.c:930!

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Triaged

Bug description:
  Running a set of autotests on Trusty with kernel 3.13.0-160-generic
  results in the following reproducible crash:

  [10870.247844] kernel BUG at 
/build/linux-PygFzL/linux-3.13.0/kernel/timer.c:930!
  [10870.255080] invalid opcode:  [#1] SMP 
  [10870.259339] Modules linked in: squashfs aufs quota_v2 quota_tree 
ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 
xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp 
bridge stp llc ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat 
ebtables x_tables dm_crypt snd_hda_codec_realtek x86_pkg_temp_thermal coretemp 
kvm_intel kvm dell_wmi sparse_keymap snd_hda_intel crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel snd_hda_codec aesni_intel dcdbas snd_hwdep 
aes_x86_64 snd_pcm snd_page_alloc lrw snd_timer gf128mul glue_helper 
dm_multipath e1000e(OX) snd ablk_helper cryptd scsi_dh ptp serio_raw pps_core 
joydev shpchp soundcore acpi_pad mac_hid lp parport zfs(POX) zunicode(POX) 
zcommon(POX) znvpair(POX) spl(OX) zavl(POX) nbd hid_generic usbhid hid ahci 
psmouse libahci wmi video [last unloaded: notifier_error_inject]
  [10870.341666] CPU: 3 PID: 0 Comm: swapper/3 Tainted: PW  OX 
3.13.0-160-generic #210-Ubuntu
  [10870.350483] Hardware name: Dell Inc. PowerEdge T30/07T4MC, BIOS 1.0.10 
09/28/2017
  [10870.358004] task: 880261d38000 ti: 880261d2e000 task.ti: 
880261d2e000
  [10870.365527] RIP: 0010:[]  [] 
add_timer_on+0x100/0x110
  [10870.373808] RSP: 0018:88026dd83e20  EFLAGS: 00010286
  [10870.379157] RAX:  RBX: 88026dd8f5e0 RCX: 
000100297ce1
  [10870.386321] RDX: 88026dd8 RSI: 0003 RDI: 
88026dd8f5e0
  [10870.393483] RBP: 88026dd83e50 R08: 0001002857e9 R09: 
88026dd83da0
  [10870.400648] R10: 88026dd83da4 R11: 88026dd83b2e R12: 
880261e04000
  [10870.407813] R13: 0100 R14: 0003 R15: 
88026dd8f5e0
  [10870.414977] FS:  () GS:88026dd8() 
knlGS:
  [10870.423103] CS:  0010 DS:  ES:  CR0: 80050033
  [10870.428886] CR2: 7ffef89bc3c8 CR3: 01c0e000 CR4: 
00360770
  [10870.437837] DR0:  DR1:  DR2: 

  [10870.445000] DR3:  DR6: fffe0ff0 DR7: 
0400
  [10870.452164] Stack:
  [10870.454229]  0c0a 88026dd8f5e0 000249f0 
0100
  [10870.461928]  8103ac10 0001 88026dd83e70 
8103aca4
  [10870.469630]  880261e04000 88026dc8f5e0 88026dd83ea8 
8107aab8
  [10870.477330] Call Trace:
  [10870.479828]   
  [10870.481796]  [] ? mce_cpu_restart+0x40/0x40
  [10870.487899]  [] mce_timer_fn+0x94/0x130
  [10870.493335]  [] call_timer_fn+0x38/0x150
  [10870.498856]  [] ? mce_cpu_restart+0x40/0x40
  [10870.504640]  [] run_timer_softirq+0x21f/0x310
  [10870.510602]  [] __do_softirq+0x101/0x310
  [10870.516130]  [] irq_exit+0x105/0x110
  [10870.521315]  [] smp_apic_timer_interrupt+0x53/0x70
  [10870.527709]  [] apic_timer_interrupt+0x191/0x1a0
  [10870.533927]   
  [10870.535894]  [] ? sched_clock_cpu+0xb5/0x100
  [10870.542083]  [] ? cpuidle_enter_state+0x57/0xd0
  [10870.548213]  [] ? cpuidle_enter_state+0x4d/0xd0
  [10870.554343]  [] cpuidle_idle_call+0xe4/0x240
  [10870.560212]  [] arch_cpu_idle+0xe/0x40
  [10870.565563]  [] cpu_startup_entry+0xc1/0x2c0
  [10870.571433]  [] start_secondary+0x24e/0x300
  [10870.577215] Code: 74 24 48 8b 03 66 0f 1f 44 00 00 48 8b 7b 08 48 83 c3 10 
4c 89 ea 4c 89 fe e8 2d 6f 6d 00 48 8b 03 48 85 c0 75 e5 e9 78 ff ff ff <0f> 0b 
48 8b 75 08 e8 05 fe ff ff e9 30 ff ff ff 0f 1f 44 00 00 
  [10870.600416] RIP  [] add_timer_on+0x100/0x110
  [10870.606350]  RSP 
  [10870.609887] ---[ end trace 4a4c8eb5651e9968 ]---
  [10870.619578] Kernel panic - not syncing: Fatal exception in interrupt
  [10870.626062] Kernel Offset: 0x0 from 0x8100 (relocation range: 
0x8000-0x9fff)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795675/+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 1788817] Re: BUG: soft lockup - CPU#0 stuck for 23s! [kworker/0:1:1119]

2019-06-13 Thread Juerg Haefliger
** Changed in: linux (Ubuntu)
   Status: Triaged => Invalid

-- 
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/1788817

Title:
  BUG: soft lockup - CPU#0 stuck for 23s! [kworker/0:1:1119]

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Released

Bug description:
  == SRU Justification ==

  Booting Trusty with kernel 3.13.0-156-generic on a fairly new Intel
  box results in stuck CPU warnings:

  [   33.551942] BUG: soft lockup - CPU#0 stuck for 23s! [kworker/0:1:1119]
  [   33.558560] Modules linked in: hid_generic ast(+) crct10dif_pclmul 
syscopyarea crc32_pclmul sysfillrect ghash_clmulni_intel sysimgblt aesni_intel 
i2c_algo_bit aes_x86_64 lrw ttm gf128mul glue_helper drm_kms_helper ablk_helper 
usbhid cryptd ahci drm hid libahci wmi
  [   33.583971] CPU: 0 PID: 1119 Comm: kworker/0:1 Not tainted 
3.13.0-156-generic #206-Ubuntu
  [   33.592270] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS 
SE5C620.86B.01.00.0294.101220161543 10/12/2016
  [   33.602836] Workqueue: events work_for_cpu_fn
  [   33.607351] task: 88084ddbc6b0 ti: 88084dd98000 task.ti: 
88084dd98000
  [   33.614957] RIP: 0010:[]  [] 
ioread32+0x42/0x50
  [   33.622805] RSP: 0018:88084dd99d18  EFLAGS: 0292
  [   33.628201] RAX:  RBX: 880851265000 RCX: 
28a6
  [   33.635429] RDX: c90016bd RSI: c90016bd RDI: 
c90016bd
  [   33.642653] RBP: 88084dd99d40 R08: 0092 R09: 
079e
  [   33.649877] R10: 813df570 R11: 88084dd99a46 R12: 
16bc
  [   33.657104] R13: a01b2ab0 R14: 88084dd99cc8 R15: 

  [   33.664329] FS:  () GS:88085f20() 
knlGS:
  [   33.672541] CS:  0010 DS:  ES:  CR0: 80050033
  [   33.678380] CR2: 7f3613be4000 CR3: 01c0e000 CR4: 
00360770
  [   33.685605] DR0:  DR1:  DR2: 

  [   33.692829] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   33.700052] Stack:
  [   33.702150]  a01a89e0 880851265000  

  [   33.709948]  a01b4100 88084dd99d68 a0073e88 
880851265000
  [   33.717751]  880850dee000 880850dee098 88084dd99db8 
a0075d92
  [   33.725550] Call Trace:
  [   33.728085]  [] ? ast_driver_load+0x320/0x540 [ast]
  [   33.734634]  [] drm_dev_register+0xa8/0x1f0 [drm]
  [   33.741000]  [] drm_get_pci_dev+0x92/0x140 [drm]
  [   33.747268]  [] ast_pci_probe+0x15/0x20 [ast]
  [   33.753282]  [] local_pci_probe+0x4a/0xb0
  [   33.758947]  [] work_for_cpu_fn+0x1a/0x30
  [   33.764613]  [] process_one_work+0x17e/0x480
  [   33.770536]  [] worker_thread+0x29b/0x410
  [   33.776205]  [] ? rescuer_thread+0x430/0x430
  [   33.782130]  [] kthread+0xcb/0xf0
  [   33.787101]  [] ? kthread_create_on_node+0x1c0/0x1c0
  [   33.793721]  [] ret_from_fork+0x6e/0xa0
  [   33.799211]  [] ? kthread_create_on_node+0x1c0/0x1c0
  [   33.805828] Code: 66 0f 1f 84 00 00 00 00 00 55 48 c7 c6 80 57 a9 81 48 89 
e5 e8 f0 fe ff ff b8 ff ff ff ff 5d c3 66 0f 1f 84 00 00 00 00 00 8b 07  66 
66 66 66 2e 0f 1f 84 00 00 00 00 00 48 81 fe ff ff 03 00

  == Fix ==

  Backport commit 6c971c09f387 ("drm/ast: Fixed system hanged if disable
  P2A")

  
  == Regression Potential ==

  Low. The patch only touches the ast driver and the modifications are
  fairly small. The patch is also in Xenial (via a stable upstream
  update) and received testing there.

  == Test Case ==

  Booted a patched kernel on HW to verify it comes up without stuck CPU
  warnings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788817/+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 1833047] [NEW] MDS: CPU buffers are not cleared on all paths from kernel to userspace

2019-06-17 Thread Juerg Haefliger
Private bug reported:

The current implementation is incomplete and there are paths from kernel
to userspace on which the CPU buffers are not cleared.

Fix that by backporting the MDS_USER_CLEAR_CPU_BUFFERS macro from stable
3.16 and use that in assembly entry/exit code.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux (Ubuntu Precise)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Trusty)
 Importance: Undecided
 Status: New

** Information type changed from Public to Private

** Also affects: linux (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: New => Invalid

-- 
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/1833047

Title:
  MDS: CPU buffers are not cleared on all paths from kernel to userspace

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  New
Status in linux source package in Trusty:
  New

Bug description:
  The current implementation is incomplete and there are paths from
  kernel to userspace on which the CPU buffers are not cleared.

  Fix that by backporting the MDS_USER_CLEAR_CPU_BUFFERS macro from
  stable 3.16 and use that in assembly entry/exit code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833047/+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 1832591] Re: linux-aws: 4.4.0-1047.51 -proposed tracker

2019-06-18 Thread Juerg Haefliger
** Summary changed:

- linux-aws:  -proposed tracker
+ linux-aws: 4.4.0-1047.51 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger 
(juergh)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger 
(juergh)

-- 
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/1832591

Title:
  linux-aws: 4.4.0-1047.51 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  kernel-stable-master-bug: 1832593
  phase: Ready for Packaging
  phase-changed: Monday, 17. June 2019 22:40 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832591/+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 1826345] Re: linux-ibm-gt: 4.15.0-1020.22 -proposed tracker

2019-04-30 Thread Juerg Haefliger
** Summary changed:

- linux-ibm-gt:  -proposed tracker
+ linux-ibm-gt: 4.15.0-1020.22 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger 
(juergh)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Juerg Haefliger 
(juergh)

-- 
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/1826345

Title:
  linux-ibm-gt: 4.15.0-1020.22 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  kernel-stable-master-bug: 1826358
  phase: Ready for Packaging
  phase-changed: Thursday, 25. April 2019 10:40 UTC
  reason:
prepare-package: Pending -- version not specified

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1826345/+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 1815061] Re: linux-ibm-gt: 4.15.0-1016.18 -proposed tracker

2019-04-30 Thread Juerg Haefliger
*** This bug is a duplicate of bug 1826345 ***
https://bugs.launchpad.net/bugs/1826345

** This bug is no longer a duplicate of bug 1822810
   linux-ibm-gt: 4.15.0-1019.21 -proposed tracker
** This bug has been marked a duplicate of bug 1826345
   linux-ibm-gt: 4.15.0-1020.22 -proposed tracker

-- 
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/1815061

Title:
  linux-ibm-gt: 4.15.0-1016.18 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug is for tracking the 4.15.0-1016.18 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814726
  phase: Ready for Testing
  phase-changed: Sunday, 03. March 2019 06:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1815061/+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 1822810] Re: linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

2019-04-30 Thread Juerg Haefliger
*** This bug is a duplicate of bug 1826345 ***
https://bugs.launchpad.net/bugs/1826345

** This bug has been marked a duplicate of bug 1826345
   linux-ibm-gt: 4.15.0-1020.22 -proposed tracker

-- 
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/1822810

Title:
  linux-ibm-gt: 4.15.0-1019.21 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Ready for Testing
  phase-changed: Monday, 22. April 2019 02:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822810/+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 1819701] Re: linux-ibm-gt: 4.15.0-1018.20 -proposed tracker

2019-04-30 Thread Juerg Haefliger
*** This bug is a duplicate of bug 1826345 ***
https://bugs.launchpad.net/bugs/1826345

** This bug is no longer a duplicate of bug 1822810
   linux-ibm-gt: 4.15.0-1019.21 -proposed tracker
** This bug has been marked a duplicate of bug 1826345
   linux-ibm-gt: 4.15.0-1020.22 -proposed tracker

-- 
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/1819701

Title:
  linux-ibm-gt: 4.15.0-1018.20 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Ready for Release
  phase-changed: Tuesday, 02. April 2019 09:48 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Pending -- ready to copy
promote-to-updates: Pending -- ready to copy

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819701/+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 1811850] Re: linux-ibm-gt: 4.15.0-1015.17 -proposed tracker

2019-04-30 Thread Juerg Haefliger
*** This bug is a duplicate of bug 1826345 ***
https://bugs.launchpad.net/bugs/1826345

** This bug is no longer a duplicate of bug 1822810
   linux-ibm-gt: 4.15.0-1019.21 -proposed tracker
** This bug has been marked a duplicate of bug 1826345
   linux-ibm-gt: 4.15.0-1020.22 -proposed tracker

-- 
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/1811850

Title:
  linux-ibm-gt: 4.15.0-1015.17 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.15.0-1015.17 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  phase: Testing
  phase-changed: Monday, 28. January 2019 18:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811850/+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 1788098] Re: Avoid migration issues with aligned 2MB THB

2019-05-06 Thread Juerg Haefliger
Leonardo, we're evaluating the patch series for inclusion.

-- 
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/1788098

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next&id=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+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


  1   2   3   4   5   6   7   8   9   10   >