[Kernel-packages] [Bug 1834925] Re: linux-snapdragon: 4.15.0-1058.64 -proposed tracker

[Khaled El Mously]

** Summary changed:

- linux-snapdragon: 4.15.0-1058.63 -proposed tracker
+ linux-snapdragon: 4.15.0-1058.64 -proposed tracker

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

Title:
  linux-snapdragon: 4.15.0-1058.64 -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:
  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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon 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

  derivatives: bug 1834924 (dragonboard-kernel)

  -- swm properties --
  kernel-stable-master-bug: 1834954
  phase: Holding before Promote to Proposed
  phase-changed: Wednesday, 10. July 2019 09:41 UTC
  reason:
promote-to-proposed: Pending -- builds not complete in ppa main:failed
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834925/+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 1836020] Re: Sometimes touchpad(goodix) can't use tap function

[Khaled El Mously]

** Also affects: linux
   Importance: Undecided
   Status: New

** No longer affects: linux

** Also affects: linux
   Importance: Undecided
   Status: New

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

** No longer affects: linux

** No longer affects: linux (Ubuntu Bionic)

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

** Also affects: linux-oem-osp1 (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Disco)
   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/1836020

Title:
  Sometimes touchpad(goodix) can't use tap function

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem-osp1 source package in Disco:
  New

Bug description:
  [Impact]
  Wake up from runtime suspend, Goodix doesn't report correct Tap event by 
tapping it the first time, so if you double tap the touchpad, the system only 
got one tap.

  [Fix]
  Adding the platforms which uses Goodix touchpad IC to the i2c designware 
quirk list.

  [Test]
  Verified on the buggy machines.

  [Regression Potential]
  Low, this quirk doesn't hurt anything and do little or none to power 
consumption.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1836020/+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 1829378] Re: Kernel 4.15.0-50 or newer wont boot as Xen-DomU with PVH

[Khaled El Mously]

** 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/1829378

Title:
  Kernel 4.15.0-50 or newer wont boot as Xen-DomU with PVH

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

Bug description:
  === SRU Justification ===
  [Impact]
  NULL pointer dereference in acpi_quirk_matches_bios_ids() renders kernel
  unbootable.

  [Fix]
  It's a regression caused by commit abd273f52766 ("UBUNTU: SAUCE: ACPI /
  bus: Add some Lenovo laptops in list of acpi table term list").

  When both bios_vendor and bios_ver are NULL then a NULL string is passed
  to strncmp() and the issue occurs.

  VMs may not provides string bios_vendor or bios_ver, so bail out early
  when either bios_vendor or bios_ver is NULL.

  [Test]
  User reported the test kernel with proposed fix solves the issue.

  [Regression Potenial]
  Low. It's quite trivial so I don't think it'll regress anything.

  === Original Bug Report ===
  After upgrading HWE-16.04-kernel from 4.15.0-48 to 4.15.0-50 the kernel 
crashes while booting as PVH-Guest with Xen 4.12 (booting as PV works).
  Kernel 4.15.0-48 and prior did boot without any problems as PVH.

  We have the same problem for Ubuntu 18.04 with Kernel 4.15.0-50.
  Ubunutu 18.04 with HWE-Kernel 4.18.0-20 boots without problems as PVH-
  DomU.

  See also https://lists.xenproject.org/archives/html/xen-
  users/2019-05/msg00010.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829378/+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 1836287] Re: Bionic update: upstream stable patchset 2019-07-11

[Khaled El Mously]

** Changed in: linux (Ubuntu Bionic)
   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/1836287

Title:
  Bionic update: upstream stable patchset 2019-07-11

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  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:

     upstream stable patchset 2019-07-11

 Ported from the following upstream stable releases:
  v4.14.73, v4.18.11,
  v4.14.74, v4.18.12

     from git://git.kernel.org/

  perf tools: Fix undefined symbol scnprintf in libperf-jvmti.so
  gso_segment: Reset skb->mac_len after modifying network header
  ipv6: fix possible use-after-free in ip6_xmit()
  net/appletalk: fix minor pointer leak to userspace in SIOCFINDIPDDPRT
  net: hp100: fix always-true check for link up state
  pppoe: fix reception of frames with no mac header
  qmi_wwan: set DTR for modems in forced USB2 mode
  udp4: fix IP_CMSG_CHECKSUM for connected sockets
  neighbour: confirm neigh entries when ARP packet is received
  udp6: add missing checks on edumux packet processing
  net/sched: act_sample: fix NULL dereference in the data path
  tls: don't copy the key out of tls12_crypto_info_aes_gcm_128
  tls: zero the crypto information from tls_context before freeing
  tls: clear key material from kernel memory when do_tls_setsockopt_conf fails
  NFC: Fix possible memory corruption when handling SHDLC I-Frame commands
  NFC: Fix the number of pipes
  ASoC: cs4265: fix MMTLR Data switch control
  ASoC: rsnd: fixup not to call clk_get/set under non-atomic
  ALSA: bebob: fix memory leak for M-Audio FW1814 and ProjectMix I/O at error 
path
  ALSA: bebob: use address returned by kmalloc() instead of kernel stack for 
streaming DMA mapping
  ALSA: emu10k1: fix possible info leak to userspace on SNDRV_EMU10K1_IOCTL_INFO
  ALSA: fireface: fix memory leak in ff400_switch_fetching_mode()
  ALSA: firewire-digi00x: fix memory leak of private data
  ALSA: firewire-tascam: fix memory leak of private data
  ALSA: fireworks: fix memory leak of response buffer at error path
  ALSA: oxfw: fix memory leak for model-dependent data at error path
  ALSA: oxfw: fix memory leak of discovered stream formats at error path
  ALSA: oxfw: fix memory leak of private data
  platform/x86: alienware-wmi: Correct a memory leak
  xen/netfront: don't bug in case of too many frags
  xen/x86/vpmu: Zero struct pt_regs before calling into sample handling code
  spi: fix IDR collision on systems with both fixed and dynamic SPI bus numbers
  ring-buffer: Allow for rescheduling when removing pages
  mm: shmem.c: Correctly annotate new inodes for lockdep
  scsi: target: iscsi: Use bin2hex instead of a re-implementation
  ocfs2: fix ocfs2 read block panic
  drm/nouveau: Fix deadlocks in nouveau_connector_detect()
  drm/nouveau/drm/nouveau: Don't forget to cancel hpd_work on suspend/unload
  drm/nouveau/drm/nouveau: Fix bogus drm_kms_helper_poll_enable() placement
  drm/nouveau/drm/nouveau: Use pm_runtime_get_noresume() in connector_detect()
  drm/nouveau/drm/nouveau: Prevent handling ACPI HPD events too early
  drm/vc4: Fix the "no scaling" case on multi-planar YUV formats
  drm: udl: Destroy framebuffer only if it was initialized
  drm/amdgpu: add new polaris pci id
  ext4: check to make sure the rename(2)'s destination is not freed
  ext4: avoid divide by zero fault when deleting corrupted inline directories
  ext4: avoid arithemetic overflow that can trigger a BUG
  ext4: recalucate superblock checksum after updating free blocks/inodes
  ext4: fix online resize's handling of a too-small final block group
  ext4: fix online resizing for bigalloc file systems with a 1k block size
  ext4: don't mark mmp buffer head dirty
  ext4: show test_dummy_encryption mount option in /proc/mounts
  sched/fair: Fix vruntime_normalized() for remote non-migration wakeup
  PCI: aardvark: Size bridges before resources allocation
  vmw_balloon: include asm/io.h
  iw_cxgb4: only allow 1 flush on user qps
  tick/nohz: Prevent bogus softirq pending warning
  spi: Fix double IDR allocation with DT aliases
  hv_netvsc: fix schedule in RCU context
  bnxt_en: Fix VF mac address regression.
  net: rtnl_configure_link: fix dev flags changes arg to __dev_notify_flags
  mtd: rawnand: denali: fix a race condition when DMA is kicked
  platform/x86: dell-smbios-wmi: Correct a memory leak
  spi: fix IDR co

[Kernel-packages] [Bug 1836668] [NEW] Xenial update: 4.4.185 upstream stable release

[Khaled El Mously]

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.185 upstream stable release
   from git://git.kernel.org/

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

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


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Xenial)
   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/1836668

Title:
  Xenial update: 4.4.185 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.185 upstream stable release
 from git://git.kernel.org/

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

[Khaled El Mously]

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.183 upstream stable release
   from git://git.kernel.org/

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

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


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Xenial)
   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/183

Title:
  Xenial update: 4.4.183 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.183 upstream stable release
 from git://git.kernel.org/

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

[Khaled El Mously]

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.182 upstream stable release
   from git://git.kernel.org/

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

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


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Xenial)
   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/1836665

Title:
  Xenial update: 4.4.182 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.182 upstream stable release
 from git://git.kernel.org/

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

[Khaled El Mously]

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.184 upstream stable release
   from git://git.kernel.org/

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

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


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Xenial)
   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/1836667

Title:
  Xenial update: 4.4.184 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.184 upstream stable release
 from git://git.kernel.org/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836667/+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 1836585] Re: Xenial kernel 4.4.0-155.182 fails to build perf with libnuma

[Khaled El Mously]

** Changed in: linux (Ubuntu Xenial)
   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/1836585

Title:
  Xenial kernel 4.4.0-155.182 fails to build perf with libnuma

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

Bug description:
  [Impact] 
  When libnuma-dev is installed on the build environment, tools/perf tries to 
build bench/numa.c, but in the current Xenial kernel in -proposed it fails:

CC   bench/numa.o
  bench/numa.c: In function 'lfsr_32':
  bench/numa.c:729:24: error: implicit declaration of function 'BIT' 
[-Werror=implicit-function-declaration]
const uint32_t taps = BIT(1) | BIT(5) | BIT(6) | BIT(31);
  ^
  bench/numa.c:729:2: error: nested extern declaration of 'BIT' 
[-Werror=nested-externs]
const uint32_t taps = BIT(1) | BIT(5) | BIT(6) | BIT(31);
^

  
  [Fix]
  Commit "UBUNTU: SAUCE: perf/bench: Drop definition of BIT in numa.c", applied 
for "Xenial update: 4.4.180 upstream stable release (LP: #1830176)" is causing 
build failures on tools/perf/bench after stable upstream commit "perf tools: No 
need to include bitops.h in util.h" removed the inclusion of the header file 
where the BIT() macro is defined.

  The fix is to revert the SAUCE patch and keep the definition of BIT()
  in loco in numa.c as done in 4.4 stable upstream.

  
  [Test Case]
  1. Install libnuma-dev package on the build environment.
  2. cd xenial/linux source directory.
  3. fakeroot debian/rules clean
  4. cd tools/perf
  5. make

  
  [Regression Potential] 
  Low. The fix is to revert a SAUCE patch that was applied to fix a build 
failure that has been fixed upstream and it's not needed anymore.

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

[Khaled El Mously]

** Changed in: linux (Ubuntu Disco)
   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/1836577

Title:
  Disco update: 5.0.17 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  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:

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

  The following patches were applied:
  * bfq: update internal depth state when queue depth changes
  * platform/x86: sony-laptop: Fix unintentional fall-through
  * platform/x86: thinkpad_acpi: Disable Bluetooth for some machines
  * platform/x86: dell-laptop: fix rfkill functionality
  * hwmon: (pwm-fan) Disable PWM if fetching cooling data fails
  * hwmon: (occ) Fix extended status bits
  * selftests/seccomp: Handle namespace failures gracefully
  * kernfs: fix barrier usage in __kernfs_new_node()
  * virt: vbox: Sanity-check parameter types for hgcm-calls coming from 
userspace
  * USB: serial: fix unthrottle races
  * iio: adc: xilinx: fix potential use-after-free on remove
  * iio: adc: xilinx: fix potential use-after-free on probe
  * iio: adc: xilinx: prevent touching unclocked h/w on remove
  * acpi/nfit: Always dump _DSM output payload
  * libnvdimm/namespace: Fix a potential NULL pointer dereference
  * HID: input: add mapping for Expose/Overview key
  * HID: input: add mapping for keyboard Brightness Up/Down/Toggle keys
  * HID: input: add mapping for "Toggle Display" key
  * libnvdimm/btt: Fix a kmemdup failure check
  * s390/dasd: Fix capacity calculation for large volumes
  * mac80211: fix unaligned access in mesh table hash function
  * mac80211: Increase MAX_MSG_LEN
  * cfg80211: Handle WMM rules in regulatory domain intersection
  * mac80211: fix memory accounting with A-MSDU aggregation
  * nl80211: Add NL80211_FLAG_CLEAR_SKB flag for other NL commands
  * libnvdimm/security: provide fix for secure-erase to use zero-key
  * libnvdimm/pmem: fix a possible OOB access when read and write pmem
  * tools/testing/nvdimm: Retain security state after overwrite
  * s390/3270: fix lockdep false positive on view->lock
  * drm/ttm: fix dma_fence refcount imbalance on error path
  * drm/amd/display: extending AUX SW Timeout
  * clocksource/drivers/npcm: select TIMER_OF
  * clocksource/drivers/oxnas: Fix OX820 compatible
  * selftests: fib_tests: Fix 'Command line is not complete' errors
  * drm/amdgpu: shadow in shadow_list without tbo.mem.start cause page fault
in sriov TDR
  * mISDN: Check address length before reading address family
  * vxge: fix return of a free'd memblock on a failed dma mapping
  * qede: fix write to free'd pointer error and double free of ptp
  * afs: Unlock pages for __pagevec_release()
  * afs: Fix in-progess ops to ignore server-level callback invalidation
  * qed: Delete redundant doorbell recovery types
  * qed: Fix the doorbell address sanity check
  * qed: Fix missing DORQ attentions
  * qed: Fix the DORQ's attentions handling
  * drm/amd/display: If one stream full updates, full update all planes
  * s390/pkey: add one more argument space for debug feature entry
  * x86/build/lto: Fix truncated .bss with -fdata-sections
  * x86/mm: Prevent bogus warnings with "noexec=off"
  * x86/reboot, efi: Use EFI reboot for Acer TravelMate X514-51T
  * KVM: nVMX: always use early vmcs check when EPT is disabled
  * KVM: fix spectrev1 gadgets
  * KVM: x86: avoid misreporting level-triggered irqs as edge-triggered in 
tracing
  * tools lib traceevent: Fix missing equality check for strcmp
  * perf top: Always sample time to satisfy needs of use of ordered queuing
  * ipmi: ipmi_si_hardcode.c: init si_type array to fix a crash
  * ocelot: Don't sleep in atomic context (irqs_disabled())
  * perf tools: Fix map reference counting
  * scsi: aic7xxx: fix EISA support
  * slab: store tagged freelist for off-slab slabmgmt
  * mm/hotplug: treat CMA pages as unmovable
  * mm: fix inactive list balancing between NUMA nodes and cgroups
  * init: initialize jump labels before command line option parsing
  * drm: bridge: dw-hdmi: Fix overflow workaround for Rockchip SoCs
  * selftests: netfilter: check icmp pkttoobig errors are set as related
  * ipvs: do not schedule icmp errors from tunnels
  * netfilter: ctnetlink: don't use conntrack/expect object addresses as id
  * netfilter: nf_tables: prevent shift wrap in nft_chain_parse_hook()
  * netfilter

[Kernel-packages] [Bug 1836667] Re: Xenial update: 4.4.184 upstream stable release

[Khaled El Mously]

Applied patches:

* Linux 4.4.184

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

Title:
  Xenial update: 4.4.184 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.184 upstream stable release
 from git://git.kernel.org/

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

[Khaled El Mously]

All patches from this updated were already applied.

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

Title:
  Xenial update: 4.4.182 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
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.182 upstream stable release
 from git://git.kernel.org/

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

[Khaled El Mously]

Applied patches:

* Linux 4.4.182

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

Title:
  Xenial update: 4.4.182 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
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.182 upstream stable release
 from git://git.kernel.org/

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

[Khaled El Mously]

Applied patches:

* fs/fat/file.c: issue flush after the writeback of FAT
* sysctl: return -EINVAL if val violates minmax
* ipc: prevent lockup on alloc_msg and free_msg
* hugetlbfs: on restore reserve error path retain subpool reservation
* mm/cma.c: fix crash on CMA allocation if bitmap allocation fails
* mm/cma_debug.c: fix the break condition in cma_maxchunk_get()
* kernel/sys.c: prctl: fix false positive in validate_prctl_map()
* mfd: intel-lpss: Set the device in reset state when init
* mfd: twl6040: Fix device init errors for ACCCTL register
* perf/x86/intel: Allow PEBS multi-entry in watermark mode
* drm/bridge: adv7511: Fix low refresh rate selection
* ntp: Allow TAI-UTC offset to be set to zero
* f2fs: fix to avoid panic in do_recover_data()
* f2fs: fix to do sanity check on valid block count of segment
* iommu/vt-d: Set intel_iommu_gfx_mapped correctly
* ALSA: hda - Register irq handler after the chip initialization
* nvmem: core: fix read buffer in place
* fuse: retrieve: cap requested size to negotiated max_write
* nfsd: allow fh_want_write to be called twice
* x86/PCI: Fix PCI IRQ routing table memory leak
* platform/chrome: cros_ec_proto: check for NULL transfer function
* soc: mediatek: pwrap: Zero initialize rdata in pwrap_init_cipher
* clk: rockchip: Turn on "aclk_dmac1" for suspend on rk3288
* ARM: dts: imx6sx: Specify IMX6SX_CLK_IPG as "ahb" clock to SDMA
* ARM: dts: imx6sx: Specify IMX6SX_CLK_IPG as "ipg" clock to SDMA
* ARM: dts: imx6qdl: Specify IMX6QDL_CLK_IPG as "ipg" clock to SDMA
* PCI: rpadlpar: Fix leaked device_node references in add/remove paths
* PCI: rcar: Fix a potential NULL pointer dereference
* video: hgafb: fix potential NULL pointer dereference
* video: imsttfb: fix potential NULL pointer dereferences
* PCI: xilinx: Check for __get_free_pages() failure
* gpio: gpio-omap: add check for off wake capable gpios
* dmaengine: idma64: Use actual device for DMA transfers
* pwm: tiehrpwm: Update shadow register for disabling PWMs
* ARM: dts: exynos: Always enable necessary APIO_1V8 and ABB_1V8 regulators on 
Arndale Octa
* pwm: Fix deadlock warning when removing PWM device
* ARM: exynos: Fix undefined instruction during Exynos5422 resume
* futex: Fix futex lock the wrong page
* ALSA: seq: Cover unsubscribe_port() in list_mutex
* libata: Extend quirks for the ST1000LM024 drives with NOLPM quirk
* mm/list_lru.c: fix memory leak in __memcg_init_list_lru_node
* fs/ocfs2: fix race in ocfs2_dentry_attach_lock()
* signal/ptrace: Don't leak unitialized kernel memory with PTRACE_PEEK_SIGINFO
* ptrace: restore smp_rmb() in __ptrace_may_access()
* i2c: acorn: fix i2c warning
* bcache: fix stack corruption by PRECEDING_KEY()
* cgroup: Use css_tryget() instead of css_tryget_online() in task_get_css()
* ASoC: cs42xx8: Add regcache mask dirty
* Drivers: misc: fix out-of-bounds access in function param_set_kgdbts_var
* scsi: lpfc: add check for loss of ndlp when sending RRQ
* scsi: bnx2fc: fix incorrect cast to u64 on shift operation
* usbnet: ipheth: fix racing condition
* KVM: x86/pmu: do not mask the value that is written to fixed PMUs
* KVM: s390: fix memory slot handling for KVM_SET_USER_MEMORY_REGION
* drm/vmwgfx: integer underflow in vmw_cmd_dx_set_shader() leading to an 
invalid read
* drm/vmwgfx: NULL pointer dereference from vmw_cmd_dx_view_define()
* USB: Fix chipmunk-like voice when using Logitech C270 for recording audio.
* USB: usb-storage: Add new ID to ums-realtek
* USB: serial: pl2303: add Allied Telesis VT-Kit3
* USB: serial: option: add support for Simcom SIM7500/SIM7600 RNDIS mode
* USB: serial: option: add Telit 0x1260 and 0x1261 compositions
* ax25: fix inconsistent lock state in ax25_destroy_timer
* be2net: Fix number of Rx queues used for flow hashing
* ipv6: flowlabel: fl6_sock_lookup() must use atomic_inc_not_zero
* lapb: fixed leak of control-blocks.
* neigh: fix use-after-free read in pneigh_get_next
* sunhv: Fix device naming inconsistency between sunhv_console and sunhv_reg
* mISDN: make sure device name is NUL terminated
* x86/CPU/AMD: Don't force the CPB cap when running under a hypervisor
* perf/ring_buffer: Fix exposing a temporarily decreased data_head
* perf/ring_buffer: Add ordering to rb->nest increment
* gpio: fix gpio-adp5588 build errors
* net: tulip: de4x5: Drop redundant MODULE_DEVICE_TABLE()
* i2c: dev: fix potential memory leak in i2cdev_ioctl_rdwr
* configfs: Fix use-after-free when accessing sd->s_dentry
* ia64: fix build errors by exporting paddr_to_nid()
* KVM: PPC: Book3S: Use new mutex to synchronize access to rtas token list
* net: sh_eth: fix mdio access in sh_eth_close() for R-Car Gen2 and RZ/A1 SoCs
* scsi: libcxgbi: add a check for NULL pointer in cxgbi_check_route()
* scsi: libsas: delete sas port if expander discover failed
* Revert "crypto: crypto4xx - properly set IV after de- and encrypt"
* coredump: fix race condition between mmget_not_zero()/get_task_mm() and core 
dumping
* Abort file_remove_privs() for non-reg. files
* Linux 4.4

[Kernel-packages] [Bug 1836667] Re: Xenial update: 4.4.184 upstream stable release

[Khaled El Mously]

All patches from this updated were already applied.

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

Title:
  Xenial update: 4.4.184 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.184 upstream stable release
 from git://git.kernel.org/

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

[Khaled El Mously]

One patch was skipped as it was already present:

0039-Revert-Bluetooth-Align-minimum-encryption-key-size-f.patch

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

Title:
  Xenial update: 4.4.183 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.183 upstream stable release
 from git://git.kernel.org/

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

[Khaled El Mously]

Applied patches:

* fs/binfmt_flat.c: make load_flat_shared_library() work
* scsi: vmw_pscsi: Fix use-after-free in pvscsi_queue_lck()
* tracing: Silence GCC 9 array bounds warning
* gcc-9: silence 'address-of-packed-member' warning
* usb: chipidea: udc: workaround for endpoint conflict issue
* Input: uinput - add compat ioctl number translation for UI_*_FF_UPLOAD
* apparmor: enforce nullbyte at end of tag string
* parport: Fix mem leak in parport_register_dev_model
* parisc: Fix compiler warnings in float emulation code
* IB/hfi1: Insure freeze_work work_struct is canceled on shutdown
* MIPS: uprobes: remove set but not used variable 'epc'
* net: hns: Fix loopback test failed at copper ports
* sparc: perf: fix updated event period in response to PERF_EVENT_IOC_PERIOD
* scripts/checkstack.pl: Fix arm64 wrong or unknown architecture
* scsi: ufs: Check that space was properly alloced in copy_query_response
* s390/qeth: fix VLAN attribute in bridge_hostnotify udev event
* hwmon: (pmbus/core) Treat parameters as paged if on multiple pages
* Btrfs: fix race between readahead and device replace/removal
* btrfs: start readahead also in seed devices
* can: flexcan: fix timeout when set small bitrate
* can: purge socket error queue on sock destruct
* ARM: imx: cpuidle-imx6sx: Restrict the SW2ISO increase to i.MX6SX
* Bluetooth: Align minimum encryption key size for LE and BR/EDR connections
* Bluetooth: Fix regression with minimum encryption key size alignment
* SMB3: retry on STATUS_INSUFFICIENT_RESOURCES instead of failing write
* cfg80211: fix memory leak of wiphy device name
* mac80211: drop robust management frames from unknown TA
* perf ui helpline: Use strlcpy() as a shorter form of strncpy() + explicit set 
nul
* perf help: Remove needless use of strncpy()
* 9p/rdma: do not disconnect on down_interruptible EAGAIN
* 9p: acl: fix uninitialized iattr access
* 9p/rdma: remove useless check in cm_event_handler
* 9p: p9dirent_read: check network-provided name length
* net/9p: include trans_common.h to fix missing prototype warning.
* ovl: modify ovl_permission() to do checks on two inodes
* x86/speculation: Allow guests to use SSBD even if host does not
* cpu/speculation: Warn on unsupported mitigations= parameter
* sctp: change to hold sk after auth shkey is created successfully
* tipc: change to use register_pernet_device
* tipc: check msg->req data len in tipc_nl_compat_bearer_disable
* team: Always enable vlan tx offload
* ipv4: Use return value of inet_iif() for __raw_v4_lookup in the while loop
* bonding: Always enable vlan tx offload
* net: check before dereferencing netdev_ops during busy poll
* Bluetooth: Fix faulty expression for minimum encryption key size check
* um: Compile with modern headers
* ASoC : cs4265 : readable register too low
* spi: bitbang: Fix NULL pointer dereference in spi_unregister_master
* ASoC: max98090: remove 24-bit format support if RJ is 0
* usb: gadget: fusb300_udc: Fix memory leak of fusb300->ep[i]
* usb: gadget: udc: lpc32xx: allocate descriptor with GFP_ATOMIC
* scsi: hpsa: correct ioaccel2 chaining
* ARC: Assume multiplier is always present
* ARC: fix build warning in elf.h
* MIPS: math-emu: do not use bools for arithmetic
* mfd: omap-usb-tll: Fix register offsets
* swiotlb: Make linux/swiotlb.h standalone includible
* bug.h: work around GCC PR82365 in BUG()
* MIPS: Workaround GCC __builtin_unreachable reordering bug
* ptrace: Fix ->ptracer_cred handling for PTRACE_TRACEME
* crypto: user - prevent operating on larval algorithms
* ALSA: seq: fix incorrect order of dest_client/dest_ports arguments
* ALSA: firewire-lib/fireworks: fix miss detection of received MIDI messages
* ALSA: usb-audio: fix sign unintended sign extension on left shifts
* lib/mpi: Fix karactx leak in mpi_powm
* btrfs: Ensure replaced device doesn't have pending chunk allocation
* tty: rocket: fix incorrect forward declaration of 'rp_init()'
* ARC: handle gcc generated __builtin_trap for older compiler
* arm64, vdso: Define vdso_{start,end} as array
* KVM: x86: degrade WARN to pr_warn_ratelimited
* dmaengine: imx-sdma: remove BD_INTR for channel0
* Linux 4.4.185

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

Title:
  Xenial update: 4.4.185 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.185 upstream stable release
 fro

[Kernel-packages] [Bug 1836668] Re: Xenial update: 4.4.185 upstream stable release

[Khaled El Mously]

2 patches were skipped because they were already applied:

0002-mm-page_idle.c-fix-oops-because-end_pfn-is-larger-th.patch
0036-KVM-X86-Fix-scan-ioapic-use-before-initialization.patch

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

Title:
  Xenial update: 4.4.185 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.185 upstream stable release
 from git://git.kernel.org/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836668/+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 1767992] Re: Linux md raid-10 freezes during resync

[Khaled El Mously]

** Changed in: linux (Ubuntu Bionic)
   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/1767992

Title:
  Linux md raid-10 freezes during resync

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

Bug description:
  [Impact]

  * If regular and resync IO happen at the same time during a regular IO
split, the split bio will wait until resync IO finishes while at the
same time the resync IO is waiting for regular IO to finish. This
results in deadlock.

  * I believe this only impacts Bionic as Disco+ already contains this
commit. Xenial doesn't contain the commit that this one fixes.

  [Test Case]

  The test kernel containing this commit received positive feedback in the
  launchpad bug.

  From the launchpad bug comment #10:

  "For reproduce on 4.15.0-50-generic: Make new raid-10, add some io fio/dd, 
  unpack anaconda archives, after minute or two deadlocked"

  [Regression Potential]

  * This fix has been in mainline since December 2018 and I don't see any
fixup commits upstream referencing this one. The small number of
changes in this commit seem reasonable for managing the `nr_pending`
adjustments which preclude either regular or resync IO.


  Original bug description follows:
  -

  I'm trying to setup a few nodes with software raid-10.

  When array is created and resync is running i'm trying to install a
  few packages and frequently system stops responding, resync process
  stops, and I'm getting following errors in the kernel log.

  This looks like a deadlock for me.

  I had this problem in both 18.04 and 16.04. Reboot is the only way to
  fix the node.

  [ 2659.317256] INFO: task kworker/u24:13:343 blocked for more than 120 
seconds.
  [ 2659.317313]   Not tainted 4.15.0-20-generic #21-Ubuntu
  [ 2659.317350] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2659.317401] kworker/u24:13  D0   343  2 0x8000
  [ 2659.317414] Workqueue: writeback wb_workfn (flush-9:1)
  [ 2659.317417] Call Trace:
  [ 2659.317430]  __schedule+0x297/0x8b0
  [ 2659.317435]  schedule+0x2c/0x80
  [ 2659.317443]  wait_barrier+0x146/0x1a0 [raid10]
  [ 2659.317449]  ? wait_woken+0x80/0x80
  [ 2659.317454]  raid10_write_request+0x77/0x950 [raid10]
  [ 2659.317459]  ? r10bio_pool_alloc+0x24/0x30 [raid10]
  [ 2659.317465]  ? mempool_alloc+0x71/0x190
  [ 2659.317469]  ? ___slab_alloc+0x20a/0x4b0
  [ 2659.317475]  ? md_write_start+0xc8/0x200
  [ 2659.317480]  ? mempool_alloc_slab+0x15/0x20
  [ 2659.317484]  raid10_make_request+0xcc/0x140 [raid10]
  [ 2659.317489]  md_handle_request+0x126/0x1a0
  [ 2659.317494]  md_make_request+0x6b/0x150
  [ 2659.317501]  generic_make_request+0x124/0x300
  [ 2659.317506]  submit_bio+0x73/0x150
  [ 2659.317510]  ? submit_bio+0x73/0x150
  [ 2659.317579]  xfs_submit_ioend+0x87/0x1c0 [xfs]
  [ 2659.317626]  xfs_do_writepage+0x377/0x6a0 [xfs]
  [ 2659.317632]  write_cache_pages+0x20c/0x4e0
  [ 2659.317674]  ? xfs_vm_writepages+0xf0/0xf0 [xfs]
  [ 2659.317682]  ? intel_pstate_update_pstate+0x40/0x40
  [ 2659.317687]  ? update_load_avg+0x5c5/0x6e0
  [ 2659.317727]  xfs_vm_writepages+0xbe/0xf0 [xfs]
  [ 2659.317732]  do_writepages+0x4b/0xe0
  [ 2659.317738]  ? check_preempt_curr+0x83/0x90
  [ 2659.317742]  ? ttwu_do_wakeup+0x1e/0x150
  [ 2659.317746]  __writeback_single_inode+0x45/0x340
  [ 2659.317749]  ? __writeback_single_inode+0x45/0x340
  [ 2659.317752]  writeback_sb_inodes+0x1e1/0x510
  [ 2659.317756]  __writeback_inodes_wb+0x67/0xb0
  [ 2659.317759]  wb_writeback+0x271/0x300
  [ 2659.317764]  wb_workfn+0x180/0x410
  [ 2659.317766]  ? wb_workfn+0x180/0x410
  [ 2659.317773]  process_one_work+0x1de/0x410
  [ 2659.317776]  worker_thread+0x32/0x410
  [ 2659.317781]  kthread+0x121/0x140
  [ 2659.317784]  ? process_one_work+0x410/0x410
  [ 2659.317788]  ? kthread_create_worker_on_cpu+0x70/0x70
  [ 2659.317793]  ? do_syscall_64+0x73/0x130
  [ 2659.317797]  ? SyS_exit_group+0x14/0x20
  [ 2659.317801]  ret_from_fork+0x35/0x40
  [ 2659.317806] INFO: task md1_resync:429 blocked for more than 120 seconds.
  [ 2659.317853]   Not tainted 4.15.0-20-generic #21-Ubuntu
  [ 2659.317889] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 2659.317940] md1_resync  D0   429  2 0x8000
  [ 2659.317943] Call Trace:
  [ 2659.317949]  __schedule+0x297/0x8b0
  [ 2659.317954]  schedule+0x2c/0x80
  [ 2659.317959]  raise_barrier+0xa1/0x1a0 [raid10]
  [ 2659.317963]  ? wait_woken+0x80/0x80
  [ 2659.317968]  raid10_sync_request+0x205/0x1f10 [raid10]
  [ 2659.317975]  ? find_next_bit+0xb/0x10
  [ 2659.317980]  ? cpumask_next+0x1b/0x20
  [ 2659.317985]  ? is_mddev_idle+0x92/0xf4
  [ 2659.317990]  md_do_sync+0x8ca/0xf10
  [ 2659.317994]  ? wait_woken+0x80/0x80
  [ 2659.31800

[Kernel-packages] [Bug 1836755] Re: hda/realtek: can't detect external mic on a Dell machine

[Khaled El Mously]

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

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

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

** Changed in: linux (Ubuntu Disco)
   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/1836755

Title:
  hda/realtek: can't detect external mic on a Dell machine

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  The external can't be detected when plugging headset in the
  front audio jack.

  [Fix]
  apply the alc891 fixup to set headset-mic and headpphone-mic pins.

  [Test Case]
  apply this patch and boot with the kernel, plug the headset-mic
  and choose headset-mic from popup dialogue, the headset-mic can
  record sound very well.

  [Regression Risk]
  Low. this patch is specific to a dell machine by pin configuration
  definition.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1836755/+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 1836031] Re: [SRU][B/B-OEM]Fix resume failure on some TPM chips

[Khaled El Mously]

** Changed in: linux (Ubuntu Bionic)
   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/1836031

Title:
  [SRU][B/B-OEM]Fix resume failure on some TPM chips

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  SRU justification:

  [Impact]
  System will reboot when resume from S3 with some TPM chips installed.

  [Fix]
  stable patch is merged in 4.15 kernel:
  888d867df441 (tpm: cmd_ready command can be issued only after granting 
locality)
  it needs a fix:
  tpm: separate cmd_ready/go_idle from runtime_pm
  these 2 patches fix the issue and enable tpm resume
  after seprating cmd_ready/go_idle.

  [Test]
  Verified on hardware. resume from S3 about 30 times with positive result.

  [Regression Potential]
  Medium, stable patches backported. Verified on hardware.
  backported with minor adjustion.

  These 2 patches are included in 4.18 and 5.0 kernel, only 4.15 needs
  them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1836031/+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 1836802] Re: Bionic update: upstream stable patchset 2019-07-16

[Khaled El Mously]

** Changed in: linux (Ubuntu Bionic)
   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/1836802

Title:
  Bionic update: upstream stable patchset 2019-07-16

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  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:

     upstream stable patchset 2019-07-16

  Ported from the following upstream stable releases:
  v4.14.81, v4.18.19,
  v4.14.82, v4.18.20

     from git://git.kernel.org/

  mtd: spi-nor: fsl-quadspi: fix read error for flash size larger than 16MB
  spi: bcm-qspi: switch back to reading flash using smaller chunks
  bcache: trace missed reading by cache_missed
  bcache: fix miss key refill->end in writeback
  hwmon: (pmbus) Fix page count auto-detection.
  jffs2: free jffs2_sb_info through jffs2_kill_sb()
  cpufreq: conservative: Take limits changes into account properly
  pcmcia: Implement CLKRUN protocol disabling for Ricoh bridges
  parisc: Fix address in HPMC IVA
  parisc: Fix map_pages() to not overwrite existing pte entries
  parisc: Fix exported address of os_hpmc handler
  ALSA: hda - Add quirk for ASUS G751 laptop
  ALSA: hda - Fix headphone pin config for ASUS G751
  ALSA: hda - Add mic quirk for the Lenovo G50-30 (17aa:3905)
  ALSA: ca0106: Disable IZD on SB0570 DAC to fix audio pops
  x86/xen: Fix boot loader version reported for PVH guests
  x86/corruption-check: Fix panic in memory_corruption_check() when boot option 
without value is provided
  ARM: dts: exynos: Disable pull control for MAX8997 interrupts on Origen
  bpf: do not blindly change rlimit in reuseport net selftest
  Revert "perf tools: Fix PMU term format max value calculation"
  xfrm: policy: use hlist rcu variants on insert
  perf vendor events intel: Fix wrong filter_band* values for uncore events
  sched/fair: Fix the min_vruntime update logic in dequeue_entity()
  perf tools: Fix use of alternatives to find JDIR
  perf cpu_map: Align cpu map synthesized events properly.
  x86/fpu: Remove second definition of fpu in __fpu__restore_sig()
  net: qla3xxx: Remove overflowing shift statement
  selftests: ftrace: Add synthetic event syntax testcase
  i2c: rcar: cleanup DMA for all kinds of failure
  locking/lockdep: Fix debug_locks off performance problem
  ataflop: fix error handling during setup
  swim: fix cleanup on setup error
  nfp: devlink port split support for 1x100G CXP NIC
  tun: Consistently configure generic netdev params via rtnetlink
  s390/sthyi: Fix machine name validity indication
  hwmon: (pwm-fan) Set fan speed to 0 on suspend
  lightnvm: pblk: fix two sleep-in-atomic-context bugs
  spi: spi-ep93xx: Use dma_data_direction for ep93xx_spi_dma_{finish,prepare}
  perf tools: Free temporary 'sys' string in read_event_files()
  perf tools: Cleanup trace-event-info 'tdata' leak
  perf strbuf: Match va_{add,copy} with va_end
  cpupower: Fix coredump on VMWare
  mmc: sdhci-pci-o2micro: Add quirk for O2 Micro dev 0x8620 rev 0x01
  iwlwifi: pcie: avoid empty free RB queue
  iwlwifi: mvm: clear HW_RESTART_REQUESTED when stopping the interface
  x86/olpc: Indicate that legacy PC XO-1 platform should not register RTC
  ACPI / processor: Fix the return value of acpi_processor_ids_walk()
  cpufreq: dt: Try freeing static OPPs only if we have added them
  mtd: rawnand: atmel: Fix potential NULL pointer dereference
  signal: Introduce COMPAT_SIGMINSTKSZ for use in compat_sys_sigaltstack
  Bluetooth: btbcm: Add entry for BCM4335C0 UART bluetooth
  x86: boot: Fix EFI stub alignment
  pinctrl: qcom: spmi-mpp: Fix err handling of pmic_mpp_set_mux
  brcmfmac: fix for proper support of 160MHz bandwidth
  net: phy: phylink: ensure the carrier is off when starting phylink
  block, bfq: correctly charge and reset entity service in all cases
  kprobes: Return error if we fail to reuse kprobe instead of BUG_ON()
  ACPI / LPSS: Add alternative ACPI HIDs for Cherry Trail DMA controllers
  pinctrl: qcom: spmi-mpp: Fix drive strength setting
  pinctrl: spmi-mpp: Fix pmic_mpp_config_get() to be compliant
  pinctrl: ssbi-gpio: Fix pm8xxx_pin_config_get() to be compliant
  net: dsa: mv88e6xxx: Fix writing to a PHY page.
  iwlwifi: mvm: fix BAR seq ctrl reporting
  ixgbevf: VF2VF TCP RSS
  ath10k: schedule hardware restart if WMI command times out
  thermal: da9062/61: Prevent hardware access during system suspend
  cgro

[Kernel-packages] [Bug 1837161] Re: Bionic update: upstream stable patchset 2019-07-18

[Khaled El Mously]

** Changed in: linux (Ubuntu Bionic)
   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/1837161

Title:
  Bionic update: upstream stable patchset 2019-07-18

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  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:

     upstream stable patchset 2019-07-18

  Ported from the following upstream stable releases:
  v4.14.87, v4.19.8,
  v4.14.88, v4.19.9,
  v4.14.89, v4.19.10

     from git://git.kernel.org/

  usb: core: quirks: add RESET_RESUME quirk for Cherry G230 Stream series
  Revert "usb: dwc3: gadget: skip Set/Clear Halt when invalid"
  iio:st_magn: Fix enable device after trigger
  lib/test_kmod.c: fix rmmod double free
  mm: use swp_offset as key in shmem_replace_page()
  misc: mic/scif: fix copy-paste error in scif_create_remote_lookup
  binder: fix race that allows malicious free of live buffer
  libceph: weaken sizeof check in ceph_x_verify_authorizer_reply()
  libceph: check authorizer reply/challenge length before reading
  f2fs: fix missing up_read
  net: don't keep lonely packets forever in the gro hash
  net: phy: add workaround for issue where PHY driver doesn't bind to the device
  KVM: nVMX/nSVM: Fix bug which sets vcpu->arch.tsc_offset to L1 tsc_offset
  udf: Allow mounting volumes with incorrect identification strings
  btrfs: Always try all copies when reading extent buffers
  Btrfs: fix rare chances for data loss when doing a fast fsync
  Btrfs: fix race between enabling quotas and subvolume creation
  perf/x86/intel: Disallow precise_ip on BTS events
  ALSA: hda: Add ASRock H81M-HDS to the power_save blacklist
  ALSA: hda: Add ASRock N68C-S UCC the power_save blacklist
  function_graph: Create function_graph_enter() to consolidate architecture code
  ARM: function_graph: Simplify with function_graph_enter()
  microblaze: function_graph: Simplify with function_graph_enter()
  x86/function_graph: Simplify with function_graph_enter()
  powerpc/function_graph: Simplify with function_graph_enter()
  sh/function_graph: Simplify with function_graph_enter()
  sparc/function_graph: Simplify with function_graph_enter()
  parisc: function_graph: Simplify with function_graph_enter()
  s390/function_graph: Simplify with function_graph_enter()
  arm64: function_graph: Simplify with function_graph_enter()
  MIPS: function_graph: Simplify with function_graph_enter()
  function_graph: Make ftrace_push_return_trace() static
  function_graph: Use new curr_ret_depth to manage depth instead of 
curr_ret_stack
  function_graph: Have profiler use curr_ret_stack and not depth
  function_graph: Move return callback before update of curr_ret_stack
  function_graph: Reverse the order of pushing the ret_stack and the callback
  ext2: initialize opts.s_mount_opt as zero before using it
  ASoC: intel: cht_bsw_max98090_ti: Add quirk for boards using pmc_plt_clk_0
  staging: most: use format specifier "%s" in snprintf
  iio/hid-sensors: Fix IIO_CHAN_INFO_RAW returning wrong values for signed 
numbers
  mm: cleancache: fix corruption on missed inode invalidation
  Kbuild: suppress packed-not-aligned warning for default setting only
  disable stringop truncation warnings for now
  test_hexdump: use memcpy instead of strncpy
  kobject: Replace strncpy with memcpy
  ALSA: intel_hdmi: Use strlcpy() instead of strncpy()
  unifdef: use memcpy instead of strncpy
  kernfs: Replace strncpy with memcpy
  ip_tunnel: Fix name string concatenate in __ip_tunnel_create()
  scsi: bfa: convert to strlcpy/strlcat
  kdb: use memmove instead of overlapping memcpy
  iser: set sector for ambiguous mr status errors
  uprobes: Fix handle_swbp() vs. unregister() + register() race once more
  MIPS: ralink: Fix mt7620 nd_sd pinmux
  mips: fix mips_get_syscall_arg o32 check
  IB/mlx5: Avoid load failure due to unknown link width
  drm/ast: Fix incorrect free on ioregs
  drm: set is_master to 0 upon drm_new_set_master() failure
  drm/meson: Enable fast_io in meson_dw_hdmi_regmap_config
  drm/meson: Fix OOB memory accesses in meson_viu_set_osd_lut()
  ALSA: trident: Suppress gcc string warning
  kgdboc: Fix restrict error
  kgdboc: Fix warning with module build
  svm: Add mutex_lock to protect apic_access_page_done on AMD systems
  drm/msm: fix OF child-node lookup
  Input: xpad - quirk all PDP Xbox One gamepads
 

[Kernel-packages] [Bug 1836968] Re: Bionic update: upstream stable patchset 2019-07-17

[Khaled El Mously]

** Changed in: linux (Ubuntu Bionic)
   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/1836968

Title:
  Bionic update: upstream stable patchset 2019-07-17

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  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:

     upstream stable patchset 2019-07-17

  Ported from the following upstream stable releases:
  v4.14.83, v4.19.4,
  v4.14.84, v4.19.5,
  v4.14.85, v4.19.6,
  v4.14.86, v4.19.7

     from git://git.kernel.org/

  flow_dissector: do not dissect l4 ports for fragments
  ibmvnic: fix accelerated VLAN handling
  ip_tunnel: don't force DF when MTU is locked
  ipv6: Fix PMTU updates for UDP/raw sockets in presence of VRF
  net-gro: reset skb->pkt_type in napi_reuse_skb()
  sctp: not allow to set asoc prsctp_enable by sockopt
  tg3: Add PHY reset for 5717/5719/5720 in change ring and flow control paths
  tuntap: fix multiqueue rx
  net: systemport: Protect stop from timeout
  net: qualcomm: rmnet: Fix incorrect assignment of real_dev
  net: dsa: microchip: initialize mutex before use
  sctp: fix strchange_flags name for Stream Change Event
  net: phy: mdio-gpio: Fix working over slow can_sleep GPIOs
  sctp: not increase stream's incnt before sending addstrm_in request
  mlxsw: spectrum: Fix IP2ME CPU policer configuration
  net: smsc95xx: Fix MTU range
  usbnet: smsc95xx: disable carrier check while suspending
  inet: frags: better deal with smp races
  ARM: dts: r8a7791: Correct critical CPU temperature
  ARM: dts: r8a7793: Correct critical CPU temperature
  net: bcmgenet: protect stop from timeout
  tcp: Fix SOF_TIMESTAMPING_RX_HARDWARE to use the latest timestamp during TCP 
coalescing
  tipc: don't assume linear buffer when reading ancillary data
  tipc: fix link re-establish failure
  net/mlx5e: Claim TC hw offloads support only under a proper build config
  net/mlx5e: Adjust to max number of channles when re-attaching
  net/mlx5e: Fix selftest for small MTUs
  l2tp: fix a sock refcnt leak in l2tp_tunnel_register
  net/mlx5e: IPoIB, Reset QP after channels are closed
  net: dsa: mv88e6xxx: Fix clearing of stats counters
  net: phy: realtek: fix RTL8201F sysfs name
  sctp: define SCTP_SS_DEFAULT for Stream schedulers
  rxrpc: Fix lockup due to no error backoff after ack transmit error
  cifs: don't dereference smb_file_target before null check
  cifs: fix return value for cifs_listxattr
  arm64: kprobe: make page to RO mode when allocate it
  ixgbe: fix MAC anti-spoofing filter after VFLR
  reiserfs: propagate errors from fill_with_dentries() properly
  hfs: prevent btree data loss on root split
  hfsplus: prevent btree data loss on root split
  um: Give start_idle_thread() a return code
  drm/edid: Add 6 bpc quirk for BOE panel.
  platform/x86: intel_telemetry: report debugfs failure
  clk: fixed-rate: fix of_node_get-put imbalance
  perf symbols: Set PLT entry/header sizes properly on Sparc
  fs/exofs: fix potential memory leak in mount option parsing
  clk: samsung: exynos5420: Enable PERIS clocks for suspend
  apparmor: Fix uninitialized value in aa_split_fqname
  x86/earlyprintk: Add a force option for pciserial device
  platform/x86: acerhdf: Add BIOS entry for Gateway LT31 v1.3307
  arm64: percpu: Initialize ret in the default case
  s390/vdso: add missing FORCE to build targets
  netfilter: ipset: list:set: Decrease refcount synchronously on deletion and 
replace
  netfilter: ipset: actually allow allowable CIDR 0 in hash:net,port,net
  s390/mm: Fix ERROR: "__node_distance" undefined!
  netfilter: ipset: Correct rcu_dereference() call in ip_set_put_comment()
  netfilter: xt_IDLETIMER: add sysfs filename checking routine
  s390/qeth: fix HiperSockets sniffer
  hwmon: (ibmpowernv) Remove bogus __init annotations
  Revert "drm/exynos/decon5433: implement frame counter"
  clk: fixed-factor: fix of_node_get-put imbalance
  lib/raid6: Fix arm64 test build
  s390/perf: Change CPUM_CF return code in event init function
  sched/core: Take the hotplug lock in sched_init_smp()
  i40e: restore NETIF_F_GSO_IPXIP[46] to netdev features
  qed: Fix memory/entry leak in qed_init_sp_request()
  qed: Fix blocking/unlimited SPQ entries leak
  qed: Fix potential memory corruption
  net: stmmac: Fix RX packet size > 8191
  SUNRPC: drop pointless static qualifier

[Kernel-packages] [Bug 1824981] Re: cifs set_oplock buffer overflow in strcat

[Khaled El Mously]

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

** Changed in: linux (Ubuntu Disco)
   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/1824981

Title:
  cifs set_oplock buffer overflow in strcat

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  * We got reports of a kernel crash in cifs module with the following
  signature:

  detected buffer overflow in strcat
  kernel BUG at <...>/lib/string.c:1052!
  invalid opcode:  [#1] SMP PTI
  RIP: 0010:fortify_panic+0x13/0x1f
  Call Trace:
   smb21_set_oplock_level+0xde/0x190 [cifs]
   smb3_set_oplock_level+0x22/0x90 [cifs]
   smb2_set_fid+0x76/0xb0 [cifs]
   cifs_new_fileinfo+0x268/0x3c0 [cifs]
   ? smb2_get_lease_key+0x40/0x40 [cifs]
   ? cifs_new_fileinfo+0x268/0x3c0 [cifs]
   cifs_open+0x57c/0x8d0 [cifs]
   do_dentry_open+0x1fe/0x320
  [...]

  * By analyzing the code of smb21_set_oplock_level(), we've noticed the
  only way fortify function strcat() would get overflow was if the value
  of cinode->oplock got corrupted in a another thread leading to a
  buffer write bigger then buffer size. In this function, the 'message'
  buffer writes are governed by cinode->oplock, so only a different
  thread cleaning the oplock value would lead to 'message' overflow.

  * By the same time we worked this analysis, a fix was proposed
  upstream for this issue  in the form of commit 6a54b2e002c9 ("cifs:
  fix strcat buffer overflow and reduce raciness in
  smb21_set_oplock_level()"), by the same reporter of this LP. The fix
  is simple and directly addresses this problem, so we hereby request
  its SRU into Bionic kernel - it's already present in linux stable
  branches.

  [Test case]

  * Unfortunately we cannot reproduce the issue. The patch proposed here was
  validated by us with xfstests (instructions followed from
  https://wiki.samba.org/index.php/Xfstesting-cifs) and fio.

  * Using xfstest with the exclusions proposed in the link above we
  managed to get the same results as a non-patched kernel, i.e., the
  same tests failed in both kernels, we didn't get worse results with
  the patch. Fio also didn't show noticeable performance regression with
  the patch.

  [Regression potential]

  * The patch was validated by the cifs filesystem maintainers and by
  the aforementioned tests; also, the scope is restricted to cifs only
  so the likelihood of regressions is considered low. The commit
  introduces no functional changes and the only affected path was just
  refactored in a way to prevent overflow and reduce race potential.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824981/+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 1795659] Re: kernel panic using CIFS share in smb2_push_mandatory_locks()

[Khaled El Mously]

** Changed in: linux (Ubuntu Bionic)
   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/1795659

Title:
  kernel panic using CIFS share in smb2_push_mandatory_locks()

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]

  * We got reports of a kernel crash in cifs module with the following
  signature:

  BUG: unable to handle kernel NULL pointer dereference at 0038
  IP: smb2_push_mandatory_locks+0x10e/0x3b0 [cifs]
  PGD 0 P4D 0
  RIP: 0010:smb2_push_mandatory_locks+0x10e/0x3b0 [cifs]
  Call Trace:
   cifs_oplock_break+0x12f/0x3d0 [cifs]
   process_one_work+0x14d/0x410
   worker_thread+0x4b/0x460
   kthread+0x105/0x140
  [...]

  * Low-level analysis (decodecode script output and the objdump of the
  function) revealed that we are crashing in a NULL ptr dereference when
  trying to access "cfile->tlink"; below, a snippet of the objdump at
  function smb2_push_mandatory_locks():

  [...]
  mov0x10(%r14),%r15   # %r15 = cifsFileInfo *cfile
  mov0x18(%r14),%rbx   # %rbx = cifsLockInfo *li = (fdlocks->locks)
  lea0x18(%r14),%r12
  mov0x90(%r15),%rax   # %rax = struct tcon_link *tlink (cfile->tlink)
  cmp%r12,%rbx
  mov0x38(%rax),%rax   # <--- TRAP [trying to get cifs_tcon *tl_tcon]
  [...]

  * After discussing the issue with CIFS maintainers (Steve French and
  Pavel Shilovsky) they suggested commit b98749cac4a6 ("CIFS: keep
  FileInfo handle live during oplock break")
  [http://git.kernel.org/linus/b98749cac4a6] as a fix for multiple
  reports of this kind of crash.

  * The fix was sent to stable kernels and is present in Ubuntu kernels
  5.0 and newer. We are requesting the SRU for this patch here in order
  to fix the crashes, after reports of successful testing with the patch
  (see below section) and since the patch is restricted to the cifs
  module scope and accepted on linux stable.

  * Alternatively the issue is known to be avoided when oplocks are
  disabled using "cifs.enable_oplocks=N" module parameter.

  [Test case]

  * Unfortunately we cannot reproduce the issue. The patch proposed here was
  validated by us with xfstests (instructions followed from
  https://wiki.samba.org/index.php/Xfstesting-cifs) and fio. Also, we
  have a user report of test validation using LISA 
(https://github.com/LIS/LISAv2).

  * Using xfstest with the exclusions proposed in the link above we
  managed to get the same results as a non-patched kernel, i.e., the
  same tests failed in both kernels, we didn't get worse results with
  the patch. Fio also didn't show noticeable performance regression with
  the patch.

  [Regression potential]

  * The patch was validated by the cifs filesystem maintainers (in fact
  they suggested its inclusion in Ubuntu) and by the aforementioned
  tests; also, the scope is restricted to cifs only so the likelihood of
  regressions is considered low.

  * Due to the nature of the code modification (add a new reference of a
  file handler and manipulate it in different places), I consider that
  if we have a regression it'll manifest as deadlock/blocked tasks, not
  something more serious like crashes or data corruption.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795659/+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 1836706] Re: linux-aws builds modules which are not shipped

[Khaled El Mously]

** Changed in: linux-aws (Ubuntu Xenial)
   Status: New => Fix Committed

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

** Changed in: linux-aws (Ubuntu Disco)
   Status: New => Fix Committed

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

Title:
  linux-aws builds modules which are not shipped

Status in linux-aws package in Ubuntu:
  In Progress
Status in linux-aws source package in Xenial:
  Fix Committed
Status in linux-aws source package in Bionic:
  Fix Committed
Status in linux-aws source package in Disco:
  Fix Committed

Bug description:
  [SRU Justification]

  == Impact ==

  The build of AWS kernels currently is set up in a way that, like the
  generic kernel, builds a larger number of modules than it actually
  provides in the main modules package. However, unlike the generic
  kernel, it does not provide a linux-modules-extra which contains all
  those built modules.

  So there is no way for users to get modules which were deemed
  unnecessary in the AWS cloud space. But this also causes problems in
  cases where out of tree modules are being tried to compile. Those will
  configure themselves based on the provided config and then might
  depend on functionality which is provided in some module that is not
  part of the non-extra set.

  == Fix ==

  To fix this, but also to get all of the kernels aligned, the AWS
  kernel should start to provide a linux-modules-extra which contains
  all those modules not shipped in the main modules packages. Since the
  default linux-aws meta package is supposed to only install the minimal
  set, there needs to be a linux-modules-extra-aws meta package which
  keeps the extra modules in sync with the kernel.

  == Testcase ==

  sudo apt-get install linux-modules-extra-aws

  This should download and install additional kernel modules.

  == Risk of Regression ==

  Low, this will start to ship an additional package which is not
  installed by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1836706/+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 1836971] Re: sched: Prevent CPU lockups when task groups take longer than the period

[Khaled El Mously]

** Changed in: linux (Ubuntu Bionic)
   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/1836971

Title:
  sched: Prevent CPU lockups when task groups take longer than the
  period

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

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1836971

  [Impact]

  On machines with extremely high CPU usage, parent task groups which
  have a large number of children can make the for loop in
  sched_cfs_period_timer() run until the watchdog fires when the
  cfs_period_us setting is too short.

  In this particular case, it is unlikely that the call to
  hrtimer_forward_now() will return 0, meaning the for loop is never
  left, and tasks are never rescheduled.

  The large number of children makes do_sched_cfs_period_timer() take
  longer than the period, which impacts calls to hrtimer_forward_now().

  The kernel will produce this call trace:

  CPU: 51 PID: 0 Comm: swapper/51 Tainted: P OELK 4.15.0-50-generic
  #54-Ubuntu

  Call Trace:
  
  ? sched_clock+0x9/0x10
  walk_tg_tree_from+0x61/0xd0
  ? task_rq_unlock+0x30/0x30
  unthrottle_cfs_rq+0xcb/0x1a0
  distribute_cfs_runtime+0xd7/0x100
  sched_cfs_period_timer+0xd9/0x1a0
  ? sched_cfs_slack_timer+0xe0/0xe0
  __hrtimer_run_queues+0xdf/0x230
  hrtimer_interrupt+0xa0/0x1d0
  smp_apic_timer_interrupt+0x6f/0x130
  apic_timer_interrupt+0x84/0x90
  

  This has been hit in production in a particularly highly utilised
  hadoop cluster which is powering an analytics platform. About 30% of
  the cluster experiences this issue every week, and the machines need a
  manual reboot to get back online.

  [Fix]

  This was fixed in 5.1 upstream with the below commit:

  commit 2e8e19226398db8265a8e675fcc0118b9e80c9e8
  Author: Phil Auld 
  Date: Tue Mar 19 09:00:05 2019 -0400
  subject: sched/fair: Limit sched_cfs_period_timer() loop to avoid hard lockup

  This commit adds a check to see if the loop has run too many times, and if it
  has, scales up the period and quota, so the timer can complete before the
  next period expires, which enables the task to be rescheduled normally.

  Note, 2e8e19226398db8265a8e675fcc0118b9e80c9e8 was included in
  upstream stable versions 4.4.179, 4.9.171, 4.14.114, 4.19.37, 5.0.10.

  This patch requires minor backporting for 4.15, so please cherry pick 
  d069fe4844f8d799d771659a745fe91870c93fda from upstream stable 4.14.y, where 
the backport has been done by the original author, to all bionic kernels.

  [Testcase]

  Kind of hard to reproduce, so this was tested on a production hadoop cluster
  with extremely high CPU load.

  I built a test kernel, which is available here:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf232784-test

  For unpatched kernels, expect the machine to lockup and print the call
  trace in the impact section.

  For patched kernels, if the machine hits the condition, it will print
  a warning to the kernel log with the new period and quota which has
  been used:

  Example from the same hadoop cluster with a machine running the test
  kernel:

  % uname -a
  4.15.0-50-generic #54+hf232784v20190626b1-Ubuntu
  % sudo grep cfs /var/log/kern.log.*
  cfs_period_timer[cpu40]: period too short, scaling up (new cfs_period_us 
67872, cfs_quota_us = 3475091)
  cfs_period_timer[cpu48]: period too short, scaling up (new cfs_period_us 
22430, cfs_quota_us = 1148437)
  cfs_period_timer[cpu48]: period too short, scaling up (new cfs_period_us 
25759, cfs_quota_us = 1318908)
  cfs_period_timer[cpu68]: period too short, scaling up (new cfs_period_us 
29583, cfs_quota_us = 1514684)
  cfs_period_timer[cpu49]: period too short, scaling up (new cfs_period_us 
33974, cfs_quota_us = 1739519)
  cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 
39017, cfs_quota_us = 1997729)
  cfs_period_timer[cpu10]: period too short, scaling up (new cfs_period_us 
44809, cfs_quota_us = 2294267)
  cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 
51460, cfs_quota_us = 2634823)
  cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 
59099, cfs_quota_us = 3025929)
  cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 
67872, cfs_quota_us = 3475091)

  [Regression Potential]
  This patch was accepted into upstream stable versions 4.4.179, 4.9.171,
  4.14.114, 4.19.37, 5.0.10, and is thus treated as stable and trusted by the
  community.

  Xenial received this patch in 4.4.0-150.176, as per LP #1828420
  Disco will receive this patch in the next version, as per LP #1830922
  Eoan already has the patch, being based on 5.2.

  While this does effect a core part of the kernel, the scheduler, the
  patch has been extensively tested, and it has been proven in
  production environments, so the overall risk is low.

To

[Kernel-packages] [Bug 1836816] Re: Fix nf_conntrack races when dealing with same origin requests in NAT environments

[Khaled El Mously]

** Changed in: linux (Ubuntu Bionic)
   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/1836816

Title:
  Fix nf_conntrack races when dealing with same origin requests in NAT
  environments

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1836816

  [Impact]

  There are a number of races in nf_conntrack when multiple packets are
  sent from the same origin to the same destination at the same time,
  where there is no pre-existing confirmed conntrack entry, in a NAT
  environment.

  This is most frequently seen in users with kubernetes workloads, where dns
  requests are sent from the same socket at the same time, from different 
threads. One request is for a A record, the other . A conntrack race 
happens, which leads to one request being dropped, which leads to 5 second dns 
timeouts.

  This problem is not specific to kubernetes, as any multi-threaded process
  which sends UDP packets from the same socket at the same time from different
  threads is affected.

  Note that since UDP is connectionless, no packet is sent when connect() is
  called, so no conntrack entries are created until a packet is first sent.

  In the scenario where two UDP packets are sent at the same time from the same
  socket on different threads, there are the following possible races:

  1.) Neither of the packets find a confirmed conntrack entry. This leads to
   two conntrack entries being created with the same tuples.
  2.) Same as 1), but a conntrack entry is confirmed for one of the packets 
before the other calls get_unique_tuple(). The other packet gets a different 
reply tuple with the source port changed.

  The outcomes of the races are the same, one of the packets is dropped when it
  comes time to confirm conntrack entries with __nf_conntrack_confirm().

  For more information, read the technical blog post:
  https://www.weave.works/blog/racy-conntrack-and-dns-lookup-timeouts

  [Fix]

  The fix to race 1) was included in 4.19 upstream by this commit:

  netfilter: nf_conntrack: resolve clash for matching conntracks
  commit ed07d9a021df6da53456663a76999189badc432a
  Author: Martynas Pumputis 
  Date: Mon Jul 2 16:52:14 2018 +0200

  This commit adds an extra check to see if the two entries are the same and to
  merge the entries if they are.

  The fix to race 2) was included in 5.0 upstream by this commit:

  netfilter: nf_nat: skip nat clash resolution for same-origin entries
  commit 4e35c1cb9460240e983a01745b5f29fe3a4d8e39
  Author: Martynas Pumputis 
  Date: Tue Jan 29 15:51:42 2019 +0100

  This commit ensures that a new source port is not allocated to a duplicated
  entry, and forwards the duplicated entries to be resolved later on.

  Note that 4e35c1cb9460240e983a01745b5f29fe3a4d8e39 was also backported
  to stable releases 4.9.163, 4.14.106, 4.19.29, 4.20.16.

  Both commits cherry-pick to 4.15 bionic cleanly. Please cherry-pick
  both commits to all bionic kernels.

  [Testcase]

  The reproducer has been provided by the author of the fixes, and is
  best viewed here:

  https://github.com/brb/conntrack-race

  The dmesg logs and packet traces in the above github repo are best
  viewed while reading upstream discussion:

  https://patchwork.ozlabs.org/patch/937963/

  I have built a test kernel for xenial HWE, which can be found here:
  https://launchpad.net/~mruffell/+archive/ubuntu/sf00227747-test-kernel

  The test kernel has been tested with a kubernetes workload and aided with
  resolution of kubernetes problems.

  [Regression Potential]

  As noted previously, 4e35c1cb9460240e983a01745b5f29fe3a4d8e39 has been
  backported to stable releases 4.9.163, 4.14.106, 4.19.29, 4.20.16 and has no
  changes to the primary commit. This commit is well tested and considered 
stable by the community.

  Both commits have also been present in the -azure kernels since 
4.15.0-1030.31 and 4.18.0-1004.4, as per LP #1795493, 
http://bugs.launchpad.net/bugs/1795493
  They have received wide testing, and no problems have been reported.

  The changes are specifically limited to resolving clashes between duplicate
  conntrack entries, and any regressions will be limited to that scenario. The
  overall risk of regression is very low.

  [Notes]
  The commits in the -azure kernels will need to be reverted before importing 
the generic bionic updates, since they are the pre-upstream commits, and have 
had several revisions since they were imported. Replacing them with the
  actual upstream commits will make things easier in the future to maintain.

  http://bugs.launchpad.net/bugs/1795493

  For race 1):
  Azure: https://patchwork.ozlabs.org/patch/937963/
  Upstream: ed07d9a021df6da53456663a769

[Kernel-packages] [Bug 1836806] Re: Two crashes on raid0 error path (during a member device removal)

[Khaled El Mously]

** Changed in: linux (Ubuntu Disco)
   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/1836806

Title:
  Two crashes on raid0 error path (during a member device removal)

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  * During raid0 error path testing, by removing one member of the
  array, we've noticed after kernel 4.18 we can trigger a crash
  depending if there's I/O in-flight during the array removal. When
  debugging the issue, a second problem was found, that could cause a
  different crash.

  * For the first and more relevant problem, commit cd4a4ae4683d
  ("block: don't use blocking queue entered for recursive bio submits") 
introduced the flag BIO_QUEUE_ENTERED in order BIOs that were split do bypass 
the blocking queue entering routine and use the live non-blocking version. What 
happens with md/raid0 though is that their BIOs have their underlying device 
changed to the physical disk (array member). If we remove this physical disk 
(or if it fails), we could have one BIO that had the flag changed to 
BIO_QUEUE_ENTERED and had the device changed to the removed array member 
(before its removal); this bio then skips a lot of checks in 
generic_make_request_checks(), triggering the following crash:

  BUG: unable to handle kernel NULL pointer dereference at 0155
  PGD 0 P4D 0
  Oops:  [#1] SMP PTI
  RIP: 0010:blk_throtl_bio+0x45/0x970
  [...]
  Call Trace:
   generic_make_request_checks+0x1bf/0x690
   generic_make_request+0x64/0x3f0
   raid0_make_request+0x184/0x620 [raid0]
   ? raid0_make_request+0x184/0x620 [raid0]
   md_handle_request+0x126/0x1a0
   md_make_request+0x7b/0x180
   generic_make_request+0x19e/0x3f0
   submit_bio+0x73/0x140
  [...]

  * When debugging the above issue, by rebuilding the kernel with
  CONFIG_BLK_CGROUP=n we've noticed a different crash. Commit
  37f9579f4c31 ("blk-mq: Avoid that submitting a bio concurrently with
  device removal triggers a crash") introduced a NULL pointer
  dereference in generic_make_request(), that manifests as:

  BUG: unable to handle kernel NULL pointer dereference at 0078
  PGD 0 P4D 0
  Oops:  [#1] SMP PTI
  RIP: 0010:generic_make_request+0x32b/0x400
  Call Trace:
   submit_bio+0x73/0x140
   ext4_io_submit+0x4d/0x60
   ext4_writepages+0x626/0xe90
   do_writepages+0x4b/0xe0
  [...]

  * For both the issues, we have simple patches that are present in 
linux-stable but not in Linus tree.
  ## For issue 1 (md removal crash):
  869eec894663 ("md/raid0: Do not bypass blocking queue entered for raid0 bios")
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=869eec894663

  ## For issue 2 (generic_make_request() NULL dereference):
  c9d8d3e9d7a0 ("block: Fix a NULL pointer dereference in 
generic_make_request()")
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c9d8d3e9d7a0

  The reasoning for both patches not being present in Linus tree is
  explained in the commit messages, but in summary Ming Lei submitted a
  major clean-up series at the same time I've submitted both patches, it
  wouldn't make sense to accept my patches to soon after remove the code
  paths with his clean-up. But Ming's series rely on legacy I/O path
  removal, and so it's very hard to backport. Hence maintainers
  suggested me to submit my small fixes to stable tree only.

  [Test case]

  For both cases, the test is the same, the only change being a kernel
  config option. To reproduce issue 1 (md removal crash), a regular
  Ubuntu kernel config is enough. For the issue 2, a kernel rebuild with
  CONFIG_BLK_CGROUP=n is necessary.

  Steps to reproduce:

  a) Create a raid0 md array with 2 NVMe devices as members, and mount it with 
an ext4 filesystem.
  
  b) Run the following oneliner (supposing the raid0 is mounted in /mnt):
  (dd of=/mnt/tmp if=/dev/zero bs=1M count=999 &); sleep 0.3;\
  echo 1 > /sys/block/nvme1n1/device/device/remove
  (whereas nvme1n1 is the 2nd array member)

  [Regression potential]

  The fixes are self-contained and small, both validated by a great
  number of subsystem maintainers (including block, raid and stable).
  Commit c9d8d3e9d7a0 was also validated by the author of the offender
  patch it fixes, and has no functional change. Commit 869eec894663 has
  only raid0 driver as scope, and fall-backs raid0 to a previous
  behavior before the introduction of BIO_QUEUE_ENTERED flag (which
  indeed increases the amount of checks performed in BIOs), so the
  regression potential is low and restricted to raid0.

To manage notifications about this bug go to:
ht

[Kernel-packages] [Bug 1836715] Re: selftests: Remove broken Power9 paste tests and fix compilation issue

[Khaled El Mously]

** Changed in: linux (Ubuntu Bionic)
   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/1836715

Title:
  selftests: Remove broken Power9 paste tests and fix compilation issue

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

Bug description:
  == SRU Justification ==
  With the Power9 copy_unaligned test removed in bug 1813118,
  we can now move forward and remove the broken paste_unaligned /
  paste_last_unaligned test in selftests/powerpc.

  From the commit message:
  Paste on POWER9 only works to accelerators and not on real memory.
  So these tests just generate a SIGILL.

  Actual test output:
  test: test_paste_unaligned
  tags: git_version:unknown
  !! child died by signal 4
  failure: test_paste_unaligned
  not ok 1..2 selftests: paste_unaligned [FAIL]
  selftests: paste_last_unaligned
  
  test: test_paste_last_unaligned
  tags: git_version:unknown
  !! child died by signal 4
  failure: test_paste_last_unaligned
  not ok 1..3 selftests: paste_last_unaligned [FAIL]
  selftests: alignment_handler

  (On Power8 these two test will be skipped)

  This patchset will also address the compilation intrduced by b2d35fa
  (selftests: add headers_install to lib.mk) which landed with Bionic
  upstream stable patchset 2019-07-12 (bug 1836426)

  == Fix ==
  * 525661ef (selftests/powerpc: Remove Power9 paste tests)
  * 7e0cf1c9 (selftests/powerpc: Fix Makefiles for headers_install change)

  These has been applied in Disco.

  As Cosmic will reach EOL soon, and we don't have alignment tests in
  Xenial, we only need this for Bionic.

  == Test ==
  Patch tested on a P9 node "baltar", test build OK and these two tests
  were removed as expected.

  == Regression Potential ==
  Low.
  Code change limited to testing tools for Power9 and just removing
  broken tests, fix build error.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-54-generic 4.15.0-54.58
  ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
  Uname: Linux 4.15.0-54-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 16 07:48 seq
   crw-rw 1 root audio 116, 33 Jul 16 07:48 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Jul 16 09:25:26 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc.
   Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
   Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro 
console=hvc0
  ProcLoadAvg: 0.09 1.71 2.01 1/1354 43576
  ProcLocks:
   1: FLOCK  ADVISORY  WRITE 4640 00:17:508 0 EOF
   2: POSIX  ADVISORY  WRITE 4182 00:17:587 0 EOF
   3: POSIX  ADVISORY  WRITE 4092 00:17:578 0 EOF
   4: POSIX  ADVISORY  WRITE 1775 00:17:348 0 EOF
   5: FLOCK  ADVISORY  WRITE 4156 00:17:583 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.15.0-54-generic (buildd@bos02-ppc64el-002) (gcc 
version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #58-Ubuntu SMP Mon Jun 24 
10:54:50 UTC 2019
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-54-generic N/A
   linux-backports-modules-4.15.0-54-generic  N/A
   linux-firmware 1.173.8
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 40
  cpu_coreson: Number of cores online = 39
  cpu_dscr: DSCR is 16
  cpu_freq:
   min: 2.862 GHz (cpu 79)
   max: 2.945 GHz (cpu 81)
   avg: 2.903 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836715/+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.

[Kernel-packages] [Bug 1836760] Re: ixgbe{vf} - Physical Function gets IRQ when VF checks link state

[Khaled El Mously]

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

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

** Changed in: linux (Ubuntu Xenial)
   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/1836760

Title:
  ixgbe{vf} - Physical Function gets IRQ when VF checks link state

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:
  Won't Fix
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed
Status in linux source package in FF-Series:
  Fix Committed

Bug description:
  [Impact]

  * Intel NICs that are SR-IOV capable and are managed by ixgbe driver presents 
a potentially harmful behavior when the ixgbevf-managed VFs (Virtual Functions) 
perform an ethtool link check. The ixgbevf driver issues a mailbox command in 
the ethtool link state handler, which induces one IRQ in the PF (Physical 
Function) per link check.
   
  * This was reported as a sort of "denial-of-service" from a guest; due to 
some link check loop running inside a guest with PCI-PT of a ixgbevf-managed 
VF, the host received a huge amount of IRQs causing soft-lockups.
   
  * The patch proposed in this SRU request fix this behavior by relying in the 
saved link state (obtained in the ixgbevf's watchdog routine) instead of 
issuing a mailbox command to the PF in every link state check request. The 
commit is available on Linus tree: 1e1b0c658d9b ("ixgbevf: Use cached link 
state instead of re-reading the value for ethtool")
  http://git.kernel.org/linus/1e1b0c658d9b

  [Test case]

  Reproducing the behavior is pretty simple; having a machine with an
  Intel NIC managed by ixgbe, proceed with the following steps:

  a) Create one or more VFs
  (echo 1 > /sys/class/net//device/sriov_numvfs)

  b) In a different terminal, monitor the non-TxRx PF IRQs:
  (watch -n1 "cat /proc/interrupts | grep  | grep -v Tx")

  c) Run "ethtool " in a loop

  Without the hereby proposed patch, the PF IRQs will increase.

  [Regression potential]

  The patch scope is restricted to ixgbevf ethtool link-check procedure,
  and was developed by the vendor itself. Being a self-contained patch
  affecting only this driver's ethtool handler, the worst potential
  regression would be a wrong link state report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836760/+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 1835054] Re: Enable Armada SOCs and MVPP2 NIC driver for disco/generic arm64

[Khaled El Mously]

** Changed in: linux (Ubuntu Disco)
   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/1835054

Title:
  Enable Armada SOCs and MVPP2 NIC driver for disco/generic arm64

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  == SRU Justification ==
  The mvpp2 is a driver for network controllers(s) in Marvell SOCs,
  particularly Armada 8040.

  However this driver was neither enabled as a module or a built-in for
  Disco arm64.

  == Fix ==
  Just like what we did for armhf, set CONFIG_MVPP2 to "m" for arm64 can
  solve this problem.

  We need to enable the Armada SOCs support (CONFIG_ARCH_MVEBU) as well
  to meet the dependency requirement.

  Other configs were added by the updateconfigs process.

  == Test ==
  A test kernel for Disco ARM64 could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1835054-mvpp2/V2/

  User has confirmed that the V1 kernel can fix this missing driver
  issue (V2 is just with CONFIG_ARCH_MULTI_V7 dropped and some configs
  added explicitly, I have it tested on an ARM64 node, the mvpp2 module
  can be loaded without any issue).

  == Regression Potential ==
  Low, this patch just enable the Armada SOCs and make this mvpp2 driver
  to be built as a module on ARM64, and we already have those for armhf.


  == Original Bug Report ==

  At least in Ubuntu 19.04, the arm64 kernel (linux-image-5.0.0) is not
  building CONFIG_MVPP2 (depends on CONFIG_ARCH_MVEBU) -  a driver for
  network controllers(s) in Marvell SOCs, particularly Armada 8040 -
  neither as a module or a built-in:

  $ uname -m
  aarch64
  $ grep MVPP2 /boot/config-5.0.0-20-generic
  $

  It makes very hard (and impossible for non-advanced users) to install
  and use Ubuntu on the Macchiatobin board (http://macchiatobin.net/) -
  a reasonably priced and performant server/mini-desktop platform.

  Could it be added, please, and the installer image re-generated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835054/+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 1836308] Re: Unhide Nvidia HDA audio controller

[Khaled El Mously]

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

** Changed in: linux (Ubuntu Disco)
   Status: Confirmed => Fix Committed

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

Title:
  Unhide Nvidia HDA audio controller

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Committed
Status in linux-oem-osp1 source package in Bionic:
  New
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Invalid
Status in linux-oem-osp1 source package in Disco:
  Invalid

Bug description:
  [Impact]
  Nvidia HDA audio controller comes with Nvidia graphics cannot be found
  by PCI subsystem.

  [Fix]
  Write bit 25 at graphics' config space offset 0x488 to enable the HDA
  controller.

  [Test]
  Nvidia HDA controller is not listed under lspci.
  After applying the fix lspci can find Nvidia HDA controller.

  [Regression Potential]
  Low. This fix doesn't bring any functional change other then exposing
  HDA controller at hardware level.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1836308/+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 1834962] Re: add support for Amazon Graviton PCIe controller

[Khaled El Mously]

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

** Changed in: linux-aws (Ubuntu Disco)
   Status: In Progress => Fix Committed

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

Title:
  add support for Amazon Graviton PCIe controller

Status in linux-aws package in Ubuntu:
  In Progress
Status in linux-aws source package in Bionic:
  Fix Committed
Status in linux-aws source package in Cosmic:
  In Progress
Status in linux-aws source package in Disco:
  Fix Committed
Status in linux-aws source package in Eoan:
  In Progress
Status in linux-aws source package in FF-Series:
  New

Bug description:
  Three patches are needed to add support for Amazon / Annapurna Labs
  "Graviton" PCIe controller, which is required for future AWS instance
  types.

  The feature is to be enabled for Ubuntu kernels >= linux-aws-bionic.

  The first patch is from mainline; the other two are AWS specific
  quirks from Amazon Linux, not yet upstream.

  4166bfe530  PCI: al: Add Amazon Annapurna Labs PCIe host controller driver
  UBUNTU: SAUCE: [aws] irqchip/gic-v2m: invoke from gic-v3 initialization and 
add acpi quirk flow
  UBUNTU: SAUCE: [aws] arm64: acpi/pci: invoke _DSM whether to preserve 
firmware PCI setup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1834962/+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 1836177] Re: Intel ethernet I219 may wrongly detect connection speed as 10Mbps

[Khaled El Mously]

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

** Changed in: linux (Ubuntu Disco)
   Status: Confirmed => Fix Committed

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

Title:
  Intel ethernet I219 may wrongly detect connection speed as 10Mbps

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  New
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Invalid
Status in linux-oem-osp1 source package in Disco:
  Invalid

Bug description:
  [Impact]
  Intel I219 ethernet may wrongly detect 1Gbps network as 10Mbps after
  ethernet cable hotplugging.

  [Fix]
  Use delayed work before deciding the network speed.
  This essentially workarounds unreliable reading on MII_BMSR register.

  [Test]
  Before the patch the network operates at 10Mbps after cable gets
  plugged.
  With the fix, network always operates in 1Gbps.

  [Regression Potential]
  Low. It changes the watchdog task from timer to delayed work, the logic
  is essentially the same.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1836177/+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 1836152] Re: Intel ethernet I219 has slow RX speed

[Khaled El Mously]

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

** Changed in: linux (Ubuntu Disco)
   Status: Confirmed => Fix Committed

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

Title:
  Intel ethernet I219 has slow RX speed

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  New
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  New
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Invalid
Status in linux-oem-osp1 source package in Disco:
  Invalid

Bug description:
  [Impact]
  RX speed on Intel ethernet I219 v6 is extremely slow due to multiple RX
  CRC errors.

  [Fix]
  Disable e1000e K1 feature to make I219 and PCH operate at higher speed
  to avoid the issue.
   
  [Test]
  Before applying the patch, the RX is slower than 150Kbps. After applying
  the fix the RX speed can achive gigabits.

  [Regression Potential]
  Low. This only applies to recent I219 generations.
  I've also test several other systems with e1000e and I don't see any
  regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1836152/+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 1829563] Re: bcache: risk of data loss on I/O errors in backing or caching devices

[Khaled El Mously]

** Changed in: linux (Ubuntu Disco)
   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/1829563

Title:
  bcache: risk of data loss on I/O errors in backing or caching devices

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

   * The bcache code in Bionic lacks several fixes to handle
     I/O errors in both backing devices and caching devices.

   * Partial or permanent errors in backing or caching devices,
     specially in writeback mode, can lead to data loss and/or
     the application is not notified about failed I/O requests.

   * The bcache device might remain available for I/O requests
     even if backing device is offline, so writes are undefined.

  [Test Case]

   * Detailed test cases/steps for the behavior of many patches
     with code logic changes are provided in bug comments.

   * The patchset has been tested for regressions on each cache
     mode (writethrough, writeback, writearound, none) with the
     xfstests test suite (on ext4) and fio (sequential + random
     read-write).

  [Regression Potential]

   * The patchset is relatively large and touches several areas
     in bcache code, however, synthetic testing of the patches
     has been performed, and extensive regression/stress tests
     were run (as mentioned in Test Case section).

   * Many patches in the patchset are 'Fixes' patches to other
     patches, and no further 'Fixes' currently exist upstream.

  [Other Info]

   * Canonical Field Eng. deploys bcache+writeback extensively
     (e.g., BootStack, UA cloud, except rare all-flash cases).

  [Original Bug Description]

  This is a request for a backport of the following upstream patch from
  4.18:

  "bcache: stop bcache device when backing device is offline"
  
https://github.com/torvalds/linux/commit/0f0709e6bfc3ce4e8e1c0e8573490c45f76cfeee

  Field engineering uses bcache quite extensively and it would be good
  to have this in the GA/bionic kernel.

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

[Khaled El Mously]

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:

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

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

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


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

** 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/1837518

Title:
  Disco update: 5.0.21 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  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:

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

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

[Khaled El Mously]

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:

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

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

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


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

** 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/1837517

Title:
  Disco update: 5.0.20 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  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:

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

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

[Khaled El Mously]

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:

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

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

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


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

** 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/1837516

Title:
  Disco update: 5.0.19 upstream stable release

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  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:

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837516/+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 1822834] Re: linux: 4.4.0-146.172 -proposed tracker

[Khaled El Mously]

** Summary changed:

- linux:  -proposed tracker
+ linux: 4.4.0-146.172 -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) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  linux: 4.4.0-146.172 -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 prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
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 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 package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  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

  backports: bug 1822832 (trusty/linux-aws), bug 1822833 
(trusty/linux-lts-xenial)
  derivatives: bug 1822824 (linux-aws), bug 1822825 (linux-euclid), bug 1822826 
(linux-kvm), bug 1822828 (linux-raspi2), bug 1822829 (linux-snapdragon), bug 
1822830 (linux-fips)

  -- swm properties --
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. April 2019 15:16 UTC
  reason:
prepare-package: Pending -- version not specified

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822834/+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 1822786] Re: linux-raspi2: 4.18.0-1012.14 -proposed tracker

[Khaled El Mously]

** Summary changed:

- linux-raspi2:  -proposed tracker
+ linux-raspi2: 4.18.0-1012.14 -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) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

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

Title:
  linux-raspi2: 4.18.0-1012.14 -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:
  Invalid
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 verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Cosmic:
  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: 1822796
  phase: Packaging
  phase-changed: Wednesday, 03. April 2019 03:30 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/1822786/+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 1822794] Re: linux-kvm: 4.18.0-1010.10 -proposed tracker

[Khaled El Mously]

** Summary changed:

- linux-kvm:  -proposed tracker
+ linux-kvm: 4.18.0-1010.10 -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) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

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

Title:
  linux-kvm: 4.18.0-1010.10 -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 Cosmic:
  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: 1822796
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. April 2019 19: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/1822794/+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 1822944] [NEW] Config changes in kernel derivatives due to fixes for CVE-2017-5715

[Khaled El Mously]

Public bug reported:

Some changes were made (in cosmic, possibly others) for CVE-2017-5715
which caused config changes in the master and deriv kernels.

Using this bug to track those config changes, since CVEs don't have
launchpad bugs.

** Affects: linux (Ubuntu)
 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/1822944

Title:
  Config changes in kernel derivatives due to fixes for CVE-2017-5715

Status in linux package in Ubuntu:
  New

Bug description:
  Some changes were made (in cosmic, possibly others) for CVE-2017-5715
  which caused config changes in the master and deriv kernels.

  Using this bug to track those config changes, since CVEs don't have
  launchpad bugs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822944/+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 1822793] Re: linux-gcp: 4.18.0-1009.10 -proposed tracker

[Khaled El Mously]

** Summary changed:

- linux-gcp:  -proposed tracker
+ linux-gcp: 4.18.0-1009.10 -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) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  linux-gcp: 4.18.0-1009.10 -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 prepare-package-signed 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-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Cosmic:
  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

  backports: bug 1822792 (bionic/linux-gcp-edge)

  -- swm properties --
  kernel-stable-master-bug: 1822796
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. April 2019 19:05 UTC
  reason:
prepare-package: Pending -- version not specified

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822793/+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 1822788] Re: linux-aws: 4.18.0-1013.15 -proposed tracker

[Khaled El Mously]

** Summary changed:

- linux-aws:  -proposed tracker
+ linux-aws: 4.18.0-1013.15 -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) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

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

Title:
  linux-aws: 4.18.0-1013.15 -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-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Cosmic:
  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

  backports: bug 1822787 (bionic/linux-aws-edge)

  -- swm properties --
  kernel-stable-master-bug: 1822796
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. April 2019 19: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/1822788/+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 1822791] Re: linux-azure: 4.18.0-1015.15 -proposed tracker

[Khaled El Mously]

** Summary changed:

- linux-azure:  -proposed tracker
+ linux-azure: 4.18.0-1015.15 -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) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  linux-azure: 4.18.0-1015.15 -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 prepare-package-signed 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 stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  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

  backports: bug 1822790 (bionic/linux-azure)

  -- swm properties --
  kernel-stable-master-bug: 1822796
  phase: Ready for Packaging
  phase-changed: Tuesday, 02. April 2019 19: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/1822791/+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 1822812] Re: linux-oracle: 4.15.0-1011.13 -proposed tracker

[Khaled El Mously]

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Andrea Righi (arighi) => Khaled El Mously (kmously)

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Andrea Righi (arighi) => Khaled El Mously (kmously)

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Andrea Righi (arighi) => Khaled El Mously (kmously)

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

Title:
  linux-oracle: 4.15.0-1011.13 -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 prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
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-oracle package in Ubuntu:
  Invalid
Status in linux-oracle 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

  backports: bug 1822811 (xenial/linux-oracle)

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822812/+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

[Khaled El Mously]

** Changed in: linux (Ubuntu Trusty)
   Status: Confirmed => 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 Released
Status in linux source package in Trusty:
  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 onza kernel: [45283.037770] Call Trace:
  Jan 25 00:00:37 onza kernel: [45283.040395]  ? 
ext4_htree_store_dire

[Kernel-packages] [Bug 1819786] Re: 4.15 kernel ip_vs --ops causes performance and hang problem

[Khaled El Mously]

** 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/1819786

Title:
  4.15 kernel ip_vs --ops causes performance and hang problem

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

Bug description:
  === SRU Justification ===
  [Impact]
  From the commit message:
  "Connections in One-packet scheduling mode (-o, --ops) are
  removed with refcnt=0 because they are not hashed in conn table."

  [Fix]
  From the commit message:
  "To avoid refcount_dec reporting this as error, change them to be
  removed with refcount_dec_if_one as all other connections."

  [Test]
  The bug reporter has a reproducer and confirmed this commit fixes the
  issue.

  [Regression Potential]
  Low. Fix for a specific use case, and it's in upstream for a while.

  === Original Bug Report ===
  On our 16.04LTS (and earlier) systems we used the ipvsadm --ops UDP
  support (one-packet scheduling) to get a better distribution amongst
  our real servers behind the load-balancer for some small subset of
  applications.

  This has worked fine through the 4.4.0-xxx kernels. But when we started
  a program to upgrade systems to use the 4.15 series of kernels to take
  advantage of new facilities, the subset of systems which used the --ops
  option ran into problems. Everything else with the 4.15 kernels appeared
  to work well.

  This issue was reported in #1817247 against 16.04LTS with the HWE 4.15 kernel
  but has not received any acknowledgement after having been reported weeks
  ago.   So we have moved on to confirm that a stock 18.04LTS system with the
  latest expected/standard 4.15 kernel also has this issue as well and report
  that here.  Perhaps this will get more attention.

  The issue appears to have been the change in the ip_vs module from using
  "atomic_*()" increment/decrement functions in the 4.4 kernel to instead
  use "refcount_*()" functions in a later kernel, including the 4.15 one
  we switched to. Unfortunately, the simple refcount_dec() function was
  inadequate, in putting out a time-consuming message and handling when
  the refcount dropped to zero, which is expected in the case of --ops
  support that retains no state post packet delivery. I will upload an
  attachment with the sample messages that get put out at packet arrival
  rate, which destroys performance of course. This test VM reports the
  identical errors we see in our production servers, but at least throwing
  only a couple of test --ops packets at it doesn't crash/hang the 18.04 system
  as it did in the 16.04 VM reported earlier.   And in production, with the
  far greater packet rates, our systems fail since the attached call backtrace
  *** appears on every packet!! ***

  This issue was apparently already recognized as an error and has appeared
  as a fix in upstream kernels. This is a reference to the 4.17 version
  of the fix that we'd like to see incorporated into the next possible
  kernel maintenance release:

  
https://github.com/torvalds/linux/commit/a050d345cef0dc6249263540da1e902bba617e43
  #diff-75923493f6e3f314b196a8223b0d6342

  We have successfully used the livepatch facility to build a livepatch .ko
  with the above diffs on our 4.15.0-36 system and successfully demonstrated
  the contrast in good/bad behavior with/without the livepatch module
  loaded. But we'd rather not have to build a version of livepatch.ko for
  each kernel maintenance release, such as the 4.5.0-46 kernel here used to
  demonstrate the issue persists in the Ubuntu mainline distro.

  The problem is easy to generate, with only a couple of packets
  and a simple configuration. Here's a very basic test (addresses
  rewritten/obscured) version of an example configuration for 2 servers
  that worked on my test VM:

  ipvsadm -A -f 100 -s rr --ops
  ipvsadm -a -f 100 -r 10.129.131.227:0 -g -w 
  ipvsadm -a -f 100 -r 10.129.131.228:0 -g -w 
  iptables -t mangle -A PREROUTING -d 172.16.5.1/32 -j MARK --set-xmark 
0x64/0x
  ifconfig lo:0 172.16.5.1/32 up

  Routing and addressing to achieve the above, or adaptation for one's
  own test environment, is left to the tester.  I just added alias 10.129.131.x
  addresses on my "outbound" interface and a static route for 172.16.5.1 to my
  client system so the test packets arrived on the "inbound" interface.

  I set up routing and addresses on my 2 NIC test such that packets arrived
  on my test machine's eth1 NIC and were directed by ip_vs out the eth2. To
  test, all I did was throw a few UDP packets via traceroute at the address
  on the iptables/firewall mark rule so that the eth1 interface of the
  test system was the traceroute system's default gateway:

    traceroute -m 2 172.16.5.1

  Without the fix my test ip_vs system either hangs or puts out messages
  as per 

[Kernel-packages] [Bug 1822579] Re: Remove btrfs module after a failed fallocate attempt will cause error on 4.4 i386

[Khaled El Mously]

** Changed in: linux (Ubuntu Xenial)
   Status: Confirmed => 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/1822579

Title:
  Remove btrfs module after a failed fallocate attempt will cause error
  on 4.4 i386

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  SRU Justification:

  [Impact]

   * If fallocate() is failing on a btrfs subvolume when its qgroup
  quota limit exceeded, a previously allocated extent map isn't
  correctly released, causing a memory leak from the pool
  btrfs_extent_map.

   * Fix by correctly deallocating the object in case of failure

  [Test Case]
   
   * 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822579/+attachment/5252459/+files/btrfs-fallocate-test.sh

  [Fix]

   *
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=be2d253cc98244765323a7c94cc1ac5cd5a17072

  Fix the memory leak by adding the proper free_extent_map() call to the
  failure path.

  [Regression Potential]

   * This is an upstream fix, tested on the affected platform. The patch
  is really small, backport changes are minimal. All the other Ubuntu
  releases are including this fix already.

  [Original bug report]
  If one issues a rmmod (or modprobe -r) command after a failed fallocate 
attempt, it will cause error with call trace:

   =
   BUG btrfs_extent_map (Not tainted): Objects remaining in btrfs_extent_map on 
kmem_cache_close()
   -

   Disabling lock debugging due to kernel taint
   INFO: Slab 0xf7526fb0 objects=34 used=1 fp=0xf43fef78 flags=0x2800080
   CPU: 1 PID: 1608 Comm: rmmod Tainted: GB   4.4.0-143-generic 
#169-Ubuntu
   Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012
    c1b0d967 35a7d73c 0286 f4ed9ddc c13c034f f7526fb0 f4ed9dfc f4ed9e70
    c11ccc42 c1a164b0 f7526fb0 0022 0001 f43fef78 02800080 656a624f
    20737463 616d6572 6e696e69 6e692067 72746220 655f7366 6e657478 616d5f74
   Call Trace:
    [] dump_stack+0x58/0x79
    [] slab_err+0x82/0xa0
    [] ? __kmalloc+0x22d/0x240
    [] ? __free_slab+0xa0/0x130
    [] ? free_partial+0xa9/0x1b0
    [] ? free_partial+0xa9/0x1b0
    [] free_partial+0xce/0x1b0
    [] ? __flush_cpu_slab+0x40/0x40
    [] __kmem_cache_shutdown+0x42/0x80
    [] kmem_cache_destroy+0x162/0x1e0
    [] extent_map_exit+0x16/0x20 [btrfs]
    [] exit_btrfs_fs+0x26/0x206 [btrfs]
    [] SyS_delete_module+0x1af/0x200
    [] ? fput+0xd/0x10
    [] ? task_work_run+0x8f/0xa0
    [] ? exit_to_usermode_loop+0xb6/0xe0
    [] do_fast_syscall_32+0x9f/0x160
    [] sysenter_past_esp+0x3d/0x61
   INFO: Object 0xf43fe078 @offset=120
   kmem_cache_destroy btrfs_extent_map: Slab cache still has objects
   CPU: 1 PID: 1608 Comm: rmmod Tainted: GB   4.4.0-143-generic 
#169-Ubuntu
   Hardware name: Dell Inc. PowerEdge R310/05XKKK, BIOS 1.11.0 09/18/2012
    c1b0d967 35a7d73c 0286 f4ed9ed4 c13c034f ef34f600 ef34f674 f4ed9f0c
    c119e630 c1a14d18 f55f3220 f4ed9f04 000d96ab f4ed9eec f4ed9eec f4ed9ef4
    f4ed9ef4 35a7d73c 022ffd44 f8e46880 f4ed8000 f4ed9f14 f8dc0ac6 f4ed9f1c
   Call Trace:
    [] dump_stack+0x58/0x79
    [] kmem_cache_destroy+0x1b0/0x1e0
    [] extent_map_exit+0x16/0x20 [btrfs]
    [] exit_btrfs_fs+0x26/0x206 [btrfs]
    [] SyS_delete_module+0x1af/0x200
    [] ? fput+0xd/0x10
    [] ? task_work_run+0x8f/0xa0
    [] ? exit_to_usermode_loop+0xb6/0xe0
    [] do_fast_syscall_32+0x9f/0x160
    [] sysenter_past_esp+0x3d/0x61

  Steps to reproduce this:

  TMP=/tmp
  MNT=/tmp/mnt
  mkdir $MNT

  TMPIMG0=$TMP/test0.img
  DEV0=`losetup -f`

  truncate --size 512M $TMPIMG0
  losetup $DEV0 $TMPIMG0

  mkfs.btrfs -f $DEV0 >& /dev/null
  mount $DEV0 $MNT

  btrfs quota enable $MNT
  btrfs sub create $MNT/subv
  btrfs qgroup limit 10M $MNT/subv

  fallocate --length 20M $MNT/subv/data
  rmmod btrfs

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-143-generic 4.4.0-143.169
  ProcVersionSignature: User Name 4.4.0-143.169-generic 4.4.170
  Uname: Linux 4.4.0-143-generic i686
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr  1 11:43 seq
   crw-rw 1 root audio 116, 33 Apr  1 11:43 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Mon Apr  1 11:55:56 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Dell Inc. PowerEdge R310
  PciMultimedia:

  ProcFB

[Kernel-packages] [Bug 1822821] Re: TSC clocksource not available in nested guests

[Khaled El Mously]

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

** Changed in: linux (Ubuntu Xenial)
   Status: Confirmed => 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/1822821

Title:
  TSC clocksource not available in nested guests

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

Bug description:
  [Impact]
   * TSC clocksource not available in nested guests

  [Test Case]
   * Spin up a nested Xenial/Bionic guest and check for 'tsc' at
     /sys/devices/system/clocksource/clocksource0/available_clocksource

  [Regression Potential]
   * The regression potential is low. Upstream code still maintains this
     behaviour of skipping calibration on guests, and tsc code verifies if
     the frequency is known before registering the clocksource

   * Patches were verified against the above test case, and also tested
     with stress-ng in both nested and non-nested guest scenarios

  [Fix]
   * By applying the upstream commits [0] [1], we skip refined calibration and
     register TSC as a clocksource directly if its frequency is known (via
     MSR or CPUID)

   * Cosmic onwards (kernel 4.18+) are already fixed

  [0] For Xenial only - https://git.kernel.org/linus/47c95a46d0f
  [1] https://git.kernel.org/linus/e10f78050323

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822821/+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 1822247] Re: ubuntu_nbd_smoke_test failed on P9 with Bionic kernel

[Khaled El Mously]

** Changed in: linux (Ubuntu Bionic)
   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/1822247

Title:
  ubuntu_nbd_smoke_test failed on P9 with Bionic kernel

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == SRU Justification, BIONIC ==

  [Impact]

  Running the autotest regression test ubuntu_nbd_smoke occasionally
  trips I/O errors such as:

  [  700.668758] print_req_error: I/O error, dev nbd0, sector 0
  [  700.668840] Buffer I/O error on dev nbd0, logical block 0, async page read

  This happens when the nbd client detaches and the backing store is
  removed. The fix is to ensure a rescan occurs.

  [Fix]

  Upstream fix fe1f9e6659ca6124f500a0f829202c7c902fab0c (" nbd: fix how we set 
bd_invalidated"). If a disconnect action happens the
  partition table gets invalidated and rescanned properly.

  [Test]

  Without the fix running the Ubuntu Kernel Team nbd smoke test will
  occasionally trip the bug and the error message from the kernel
  appears and the test fails. With the fix, this test has been run tens
  of times without showing the failure.

  To test run:
  autotest/client/local-test autotest/client/tests/ubuntu_nbd_smoke_test/control

  [Regression Potential]

  This fix touches just the NBD driver and has been upstream since May
  2018 without any subsequent bug reports against it, so it is a known
  good fix. At most it sets the bd_invalidated flag more aggressively,
  so the rescan will occur, so I believe the regression potential is
  very limited just to ndb client connect/disconnect activity.

  -

  Reproduce rate: 2 out of 3 runs
  This issue can be found on other arches as well, normally it will fail with 
the first run and pass with the second attempt.

    * Command:
    
/home/ubuntu/autotest/client/tests/ubuntu_nbd_smoke_test/ubuntu_nbd_smoke
    _test.sh
    Exit status: 1
    Duration: 7.90551400185

    stdout:
    creating backing nbd image /tmp/nbd_image.img

    

    Image path:/tmp/nbd_image.img
    Mount point:   /mnt/nbd-test-13924
    Date:  Fri Mar 29 06:06:04 UTC 2019
    Host:  baltar
    Kernel:4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:48 UTC 2019
    Machine:   baltar ppc64le ppc64le
    CPUs online:   160
    CPUs total:160
    Page size: 65536
    Pages avail:   1904339
    Pages total:   2089666
    Free space:
    Filesystem  Size  Used Avail Use% Mounted on
    udev 61G 0   61G   0% /dev
    tmpfs13G   12M   13G   1% /run
    /dev/sda2   1.8T   11G  1.7T   1% /
    tmpfs64G 0   64G   0% /dev/shm
    tmpfs   5.0M 0  5.0M   0% /run/lock
    tmpfs64G 0   64G   0% /sys/fs/cgroup
    tmpfs13G 0   13G   0% /run/user/1000
    


    NBD device /dev/nbd0 created
    found nbd export
    NBD exports found:
    test
    starting client with NBD device /dev/nbd0
    Negotiation: ..size = 128MB
    creating ext4 on /dev/nbd0
    mkfs on /dev/nbd0 succeeded after 0 attempt(s)
    checking ext4 on /dev/nbd0
    fsck from util-linux 2.31.1
    /dev/nbd0: clean, 11/32768 files, 9787/131072 blocks

    mount:
    /dev/nbd0 on /mnt/nbd-test-13924 type ext4 (rw,relatime,data=ordered)
    mounted on /dev/nbd0

    free:
    Filesystem 1K-blocks  Used Available Use% Mounted on
    /dev/nbd0 122835  1550112111   2% /mnt/nbd-test-13924

    creating large file /mnt/nbd-test-13924/largefile
    -rw-r--r-- 1 root root 100M Mar 29 06:06 /mnt/nbd-test-13924/largefile

    free:
    Filesystem 1K-blocks   Used Available Use% Mounted on
    /dev/nbd0 122835 103951  9710  92% /mnt/nbd-test-13924

    removing file /mnt/nbd-test-13924/largefile
    unmounting /mnt/nbd-test-13924
    stopping client
    disconnect, sock, done
    Found kernel warning, IO error and/or call trace
    echo
    [  694.662746] creating backing nbd image /tmp/nbd_image.img
    [  695.821047] NBD device /dev/nbd0 created
    [  696.271555] found nbd export
    [  697.318393] starting client with NBD device /dev/nbd0
    [  697.323210] creating ext4 on /dev/nbd0
    [  697.589620] mkfs on /dev/nbd0 succeeded after 0 attempt(s)
    [  697.821953] checking ext4 on /dev/nbd0
    [  697.919173] EXT4-fs (nbd0): mounted filesystem with ordered data mode. 
Opts: (null)
    [  697.925418] mounted on /dev/nbd0
    [  697.927107] creating large file /mnt/nbd-test-13924/largefile
    [  698.839327] removing file /mnt/nbd-test-13924/largefile
    [  699.596736] unmounting /mnt/nbd-test-13924
    [  700.664881] stopp

[Kernel-packages] [Bug 1822692] Re: Please ship the ib_uverbs driver module in the main modules package

[Khaled El Mously]

** Changed in: linux-aws (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

** Changed in: linux-aws (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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1822692

Title:
  Please ship the ib_uverbs driver module in the main modules package

Status in linux-aws package in Ubuntu:
  Fix Released
Status in linux-aws source package in Xenial:
  Fix Committed
Status in linux-aws source package in Bionic:
  Fix Committed
Status in linux-aws source package in Cosmic:
  Fix Committed
Status in linux-aws source package in Disco:
  Fix Released

Bug description:
  Please include the module drivers/infiniband/core/ib_uverbs.ko and its
  companion ib_umad.ko in the main linux-modules-*-aws package, in order
  to support upcoming Amazon features.

  +++ b/debian.aws/control.d/aws.inclusion-list

  +drivers/infiniband/core/ib_umad.ko
  +drivers/infiniband/core/ib_uverbs.ko

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

[Khaled El Mously]

** Summary changed:

- linux-aws:  -proposed tracker
+ linux-aws: 4.15.0-1037.39 -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) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

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

Title:
  linux-aws: 4.15.0-1037.39 -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 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-aws package in Ubuntu:
  Invalid
Status in linux-aws 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

  backports: bug 1822804 (xenial/linux-aws-hwe)

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824773/+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 1824774] Re: linux-aws: 4.4.0-1081.91 -proposed tracker

[Khaled El Mously]

** Summary changed:

- linux-aws:  -proposed tracker
+ linux-aws: 4.4.0-1081.91 -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) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

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

Title:
  linux-aws: 4.4.0-1081.91 -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 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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  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: 1822834
  phase: Packaging
  phase-changed: Tuesday, 16. April 2019 01:10 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/1824774/+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 1824775] Re: linux-aws: 4.4.0-1042.45 -proposed tracker

[Khaled El Mously]

** Summary changed:

- linux-aws:  -proposed tracker
+ linux-aws: 4.4.0-1042.45 -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) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

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

Title:
  linux-aws: 4.4.0-1042.45 -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-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: 1822834
  phase: Ready for Packaging
  phase-changed: Monday, 15. April 2019 09:12 UTC
  reason:
prepare-package: Pending -- version not specified

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

[Khaled El Mously]

** Summary changed:

- bionic/linux-snapdragon:  -proposed tracker
+ bionic/linux-snapdragon: 4.15.0-1061.67 -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) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

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

Title:
  bionic/linux-snapdragon: 4.15.0-1061.67 -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-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 verification-testing series:
  New
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon 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

  derivatives: bug 1839978 (dragonboard-kernel)

  -- swm properties --
  kernel-stable-master-bug: 1840006
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Packaging
  phase-changed: Thursday, 15. August 2019 05:55 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1839978
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839979/+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 1839953] Re: disco/linux-aws: 5.0.0-1013.15 -proposed tracker

[Khaled El Mously]

** Summary changed:

- disco/linux-aws: 5.0.0-1013.14 -proposed tracker
+ disco/linux-aws: 5.0.0-1013.15 -proposed tracker

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

Title:
  disco/linux-aws: 5.0.0-1013.15 -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:
  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-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Disco:
  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

  backports: bug 1839951 (bionic/linux-aws-edge)

  -- swm properties --
  kernel-stable-master-bug: 1839972
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Packaging
  phase-changed: Wednesday, 14. August 2019 04:45 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
  trackers:
bionic/linux-aws-edge: bug 1839951
  variant: debs

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

[Khaled El Mously]

** Summary changed:

- bionic/linux-snapdragon: 4.15.0-1061.67 -proposed tracker
+ bionic/linux-snapdragon: 4.15.0-1061.68 -proposed tracker

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

Title:
  bionic/linux-snapdragon: 4.15.0-1061.68 -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:
  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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon 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

  derivatives: bug 1839978 (dragonboard-kernel)

  -- swm properties --
  kernel-stable-master-bug: 1840006
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Holding before Promote to Proposed
  phase-changed: Friday, 16. August 2019 04:38 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa main:building
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1839978
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839979/+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 1840816] Re: disco/linux: 5.0.0-27.28 -proposed tracker

[Khaled El Mously]

** Summary changed:

- disco/linux:  -proposed tracker
+ disco/linux: 5.0.0-27.28 -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) => Khaled El 
Mously (kmously)

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

** Changed in: kernel-sru-workflow/prepare-package-lrm
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  disco/linux: 5.0.0-27.28 -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-lrm series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed 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 Disco:
  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

  backports: bug 1840812 (bionic/linux-hwe), bug 1840815 (bionic/linux-oem-osp1)
  derivatives: bug 1839949 (linux-raspi2), bug 1839968 (linux-snapdragon), bug 
1840800 (linux-aws), bug 1840803 (linux-azure), bug 1840808 (linux-gcp), bug 
1840810 (linux-kvm), bug 1840811 (linux-oracle)

  -- swm properties --
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Packaging
  phase-changed: Tuesday, 20. August 2019 19:06 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-lrm: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  trackers:
bionic/linux-hwe: bug 1840812
bionic/linux-oem-osp1: bug 1840815
disco/linux-aws: bug 1840800
disco/linux-azure: bug 1840803
disco/linux-gcp: bug 1840808
disco/linux-kvm: bug 1840810
disco/linux-oracle: bug 1840811
disco/linux-raspi2: bug 1839949
disco/linux-snapdragon: bug 1839968
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840816/+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 1840750] Re: [Potential Regression] System crashes when running ftrace test in ubuntu_kernel_selftests

[Khaled El Mously]

** Changed in: linux (Ubuntu Disco)
   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/1840750

Title:
  [Potential Regression] System crashes when running ftrace test in
  ubuntu_kernel_selftests

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  ftrace test in ubuntu_kernel_selftests causes a system crash + reboot when 
testing "Register/unregister many kprobe events".

  [Fix]
  The issue has been discussed in the following LKML thread:
  https://lkml.org/lkml/2019/6/5/274

  and the following 3 upstream commits have been identified to resolve
  this issue:

  d2a68c4effd8 x86/ftrace: Do not call function graph from dynamic trampolines
  3c0dab44e227 x86/ftrace: Set trampoline pages as executable
  7298e24f9042 x86/kprobes: Set instruction page as executable

  From these commits, the Disco kernel currently in -proposed
  (5.0.0-26.27) is missing only the following commit, which has been
  already committed as part of LP: #1839887 (Disco update: upstream
  stable patchset 2019-08-12) but not yet released:

  7298e24f9042 x86/kprobes: Set instruction page as executable

  [Regression potential]
  The commit touches the x86/kprobes code so there's a chance of regression 
there which I would flag as medium. However, it has been applied upstream for 
v5.2-rc1 and there is no follow-up commits marked as fix for it. 

  --
  This issue is 100% reproducible. It looks like this has something to do with 
the Disco kernel in proposed (5.0.0-1014.14).

  Test combinations:
  kernel in updates + source code master branch = OK
  kernel in proposed + source code master-next branch = NOT OK
  kernel in proposed + source code master branch = NOT OK

  The system will crash and reboot itself when testing:
  "Register/unregister many kprobe events"

  [33] Kprobe event with comm arguments [PASS]
  [34] Kprobe event string type argument[PASS]
  [35] Kprobe event symbol argument [PASS]
  [36] Kprobe event argument syntax [PASS]
  [37] Kprobes event arguments with types   [PASS]
  [38] Kprobe event auto/manual naming  [PASS]
  [39] Kprobe dynamic event with function tracer[PASS]
  [40] Kretprobe dynamic event with arguments   [PASS]
  [41] Kretprobe dynamic event with maxactive   [PASS]
  [42] Register/unregister many kprobe events
  packet_write_wait: Connection to 35.233.208.253 port 22: Broken pipe

  Tried with use "tail -f /var/log/syslog" and "dmesg -w" to see what
  happened, but it will just disconnected and reboot itself.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-1014-gcp 5.0.0-1014.14
  ProcVersionSignature: Ubuntu 5.0.0-1014.14-gcp 5.0.21
  Uname: Linux 5.0.0-1014-gcp x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  Date: Tue Aug 20 08:13:13 2019
  SourcePackage: linux-signed-gcp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1840750/+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 1840808] Re: disco/linux-gcp: 5.0.0-1015.15 -proposed tracker

[Khaled El Mously]

** Summary changed:

- disco/linux-gcp:  -proposed tracker
+ disco/linux-gcp: 5.0.0-1015.15 -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) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  disco/linux-gcp: 5.0.0-1015.15 -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 prepare-package-signed 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-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Disco:
  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

  backports: bug 1840806 (bionic/linux-gcp), bug 1840823 (bionic/linux-
  gke-5.0)

  -- swm properties --
  kernel-stable-master-bug: 1840816
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Packaging
  phase-changed: Tuesday, 20. August 2019 20:50 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  trackers:
bionic/linux-gcp: bug 1840806
bionic/linux-gke-5.0: bug 1840823
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840808/+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 1840803] Re: disco/linux-azure: 5.0.0-1018.19 -proposed tracker

[Khaled El Mously]

** Summary changed:

- disco/linux-azure:  -proposed tracker
+ disco/linux-azure: 5.0.0-1018.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) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  disco/linux-azure: 5.0.0-1018.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 prepare-package-signed 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 stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Disco:
  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

  backports: bug 1840802 (bionic/linux-azure)

  -- swm properties --
  kernel-stable-master-bug: 1840816
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Packaging
  phase-changed: Tuesday, 20. August 2019 21:05 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  trackers:
bionic/linux-azure: bug 1840802
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840803/+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 1840810] Re: disco/linux-kvm: 5.0.0-1015.16 -proposed tracker

[Khaled El Mously]

** Summary changed:

- disco/linux-kvm:  -proposed tracker
+ disco/linux-kvm: 5.0.0-1015.16 -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) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

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

Title:
  disco/linux-kvm: 5.0.0-1015.16 -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-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Disco:
  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: 1840816
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Packaging
  phase-changed: Tuesday, 20. August 2019 21:15 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/1840810/+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 1840802] Re: bionic/linux-azure: 5.0.0-1018.19~18.04.1 -proposed tracker

[Khaled El Mously]

** Summary changed:

- bionic/linux-azure:  -proposed tracker
+ bionic/linux-azure: 5.0.0-1018.19~18.04.1 -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) => Khaled El 
Mously (kmously)

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

** Changed in: kernel-sru-workflow/prepare-package-lrm
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  bionic/linux-azure: 5.0.0-1018.19~18.04.1 -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-lrm series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed 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 stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure 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

  derivatives: bug 1840801 (azure-kernel), bug 1840821 (linux-azure-
  edge)

  -- swm properties --
  kernel-stable-master-bug: 1840803
  packages:
lrm: linux-restricted-modules-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Packaging
  phase-changed: Wednesday, 21. August 2019 04:26 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-lrm: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  trackers:
bionic/linux-azure-edge: bug 1840821
bionic/linux-azure/azure-kernel: bug 1840801
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840802/+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 1820075] Re: [Packaging] Improve config annotations check on custom kernels

[Khaled El Mously]

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

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

Title:
  [Packaging] Improve config annotations check on custom kernels

Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-gcp package in Ubuntu:
  New
Status in linux-oracle package in Ubuntu:
  New
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-gcp source package in Xenial:
  New
Status in linux-oracle source package in Xenial:
  New
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-gcp source package in Bionic:
  New
Status in linux-oracle source package in Bionic:
  New
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-gcp source package in Cosmic:
  Fix Released
Status in linux-oracle source package in Cosmic:
  New
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-gcp source package in Disco:
  New
Status in linux-oracle source package in Disco:
  New

Bug description:
  [Impact]

  Currently for custom kernels, it's necessary to keep a separate
  annotations file that often gets out of sync with the corresponding
  file in debian.master/.

  The "debian/scripts/config-check" script can be changed to allow
  additional annotations files to act as overlays over the original
  annotations file, allowing custom kernels to override the policies
  just for the relevant configs.

  The proposal is to add support for an include directive in the
  annotations file so custom kernels can include the annotations file
  from its base kernel and override policies on a config basis.

  [Test Case]

  A kernel build should complete successfully after the change.

  
  [Regression Potential] 

  Low regression potential since that's a change on the build process
  that doesn't affect the final kernel that is built.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1820075/+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 1840811] Re: disco/linux-oracle: 5.0.0-1001.1 -proposed tracker

[Khaled El Mously]

** Summary changed:

- disco/linux-oracle:  -proposed tracker
+ disco/linux-oracle: 5.0.0-1001.1 -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) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  disco/linux-oracle: 5.0.0-1001.1 -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 prepare-package-signed 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-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Disco:
  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

  backports: bug 1840826 (bionic/linux-oracle-edge)

  -- swm properties --
  kernel-stable-master-bug: 1840816
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Ready for Packaging
  phase-changed: Tuesday, 20. August 2019 20:13 UTC
  reason:
prepare-package: Pending -- version not specified
  trackers:
bionic/linux-oracle-edge: bug 1840826
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840811/+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 1840811] Re: disco/linux-oracle: 5.0.0-1001.2 -proposed tracker

[Khaled El Mously]

** Summary changed:

- disco/linux-oracle: 5.0.0-1001.1 -proposed tracker
+ disco/linux-oracle: 5.0.0-1001.2 -proposed tracker

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

Title:
  disco/linux-oracle: 5.0.0-1001.2 -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 prepare-package-signed series:
  Fix Released
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-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Disco:
  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

  backports: bug 1840826 (bionic/linux-oracle-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1840816
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 11:20 UTC
  reason:
promote-to-proposed: Stalled -- packages no longer available
  trackers:
bionic/linux-oracle-edge: bug 1840826
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840811/+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 1840811] Re: disco/linux-oracle: 5.0.0-1001.2 -proposed tracker

[Khaled El Mously]

** Changed in: kernel-sru-workflow
   Status: In Progress => New

** Changed in: kernel-sru-workflow/certification-testing
   Status: Invalid => New

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

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

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Incomplete => New

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

** Changed in: linux-oracle (Ubuntu Disco)
   Status: Confirmed => New

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

Title:
  disco/linux-oracle: 5.0.0-1001.2 -proposed tracker

Status in Kernel SRU Workflow:
  New
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:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed 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-oracle package in Ubuntu:
  New
Status in linux-oracle source package in Disco:
  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

  backports: bug 1840826 (bionic/linux-oracle-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1840816
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Promote to Proposed
  phase-changed: Tuesday, 27. August 2019 11:20 UTC
  reason:
promote-to-proposed: Stalled -- review FAILED
  trackers:
bionic/linux-oracle-edge: bug 1840826
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840811/+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 1840811] Re: disco/linux-oracle: 5.0.0-1001.2 -proposed tracker

[Khaled El Mously]

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Khaled El Mously (kmously) => Canonical Kernel Team 
(canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Khaled El Mously (kmously) => Canonical Kernel Team 
(canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Khaled El Mously (kmously) => Canonical Kernel Team 
(canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Andy Whitcroft (apw) => Ubuntu Stable Release Updates Team 
(ubuntu-sru)

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

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

Title:
  disco/linux-oracle: 5.0.0-1001.2 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
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-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Disco:
  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

  backports: bug 1840826 (bionic/linux-oracle-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1840816
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 28. August 2019 19:43 UTC
  reason:
promote-to-proposed: Stalled -- ready for review
  trackers:
bionic/linux-oracle-edge: bug 1840826
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840811/+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 1840826] Re: bionic/linux-oracle-edge: 5.0.0-1001.2~18.04.1 -proposed tracker

[Khaled El Mously]

** Summary changed:

- bionic/linux-oracle-edge:  -proposed tracker
+ bionic/linux-oracle-edge: 5.0.0-1001.2~18.04.1 -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) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  bionic/linux-oracle-edge: 5.0.0-1001.2~18.04.1 -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 prepare-package-signed 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:
  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: 1840811
  packages:
main: linux-oracle-edge
meta: linux-meta-oracle-edge
signed: linux-signed-oracle-edge
  phase: Packaging
  phase-changed: Friday, 30. August 2019 00:05 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840826/+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 1840811] Re: disco/linux-oracle: 5.0.0-1001.2 -proposed tracker

[Khaled El Mously]

*** This bug is a duplicate of bug 1842155 ***
https://bugs.launchpad.net/bugs/1842155

** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => New

** Changed in: kernel-sru-workflow/certification-testing
   Status: Confirmed => New

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Khaled El Mously (kmously) => Canonical Kernel Team 
(canonical-kernel-team)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Khaled El Mously (kmously) => Canonical Kernel Team 
(canonical-kernel-team)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
     Assignee: Khaled El Mously (kmously) => Canonical Kernel Team 
(canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Released => New

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Andy Whitcroft (apw) => Ubuntu Stable Release Updates Team 
(ubuntu-sru)

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => New

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => New

** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => New

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

Title:
  disco/linux-oracle: 5.0.0-1001.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
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 prepare-package-signed 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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Disco:
  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

  backports: bug 1840826 (bionic/linux-oracle-edge)

  -- swm properties --
  boot-testing-requested: true
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Testing
  phase-changed: Friday, 30. August 2019 17:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-oracle-edge: bug 1840826
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840811/+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 1840816] Re: disco/linux: 5.0.0-27.28 -proposed tracker

[Khaled El Mously]

** Description changed:

  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
+   https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1840812 (bionic/linux-hwe), bug 1840815 (bionic/linux-oem-osp1)
- derivatives: bug 1839949 (linux-raspi2), bug 1839968 (linux-snapdragon), bug 
1840800 (linux-aws), bug 1840803 (linux-azure), bug 1840808 (linux-gcp), bug 
1840810 (linux-kvm), bug 1840811 (linux-oracle)
+ derivatives: bug 1839949 (linux-raspi2), bug 1839968 (linux-snapdragon), bug 
1840800 (linux-aws), bug 1840803 (linux-azure), bug 1840808 (linux-gcp), bug 
1840810 (linux-kvm)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Signoff
  phase-changed: Monday, 26. August 2019 15:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe: bug 1840812
bionic/linux-oem-osp1: bug 1840815
disco/linux-aws: bug 1840800
disco/linux-azure: bug 1840803
disco/linux-gcp: bug 1840808
disco/linux-kvm: bug 1840810
disco/linux-oracle: bug 1840811
disco/linux-raspi2: bug 1839949
disco/linux-snapdragon: bug 1839968
  variant: debs

** Description changed:

  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
  
  backports: bug 1840812 (bionic/linux-hwe), bug 1840815 (bionic/linux-oem-osp1)
- derivatives: bug 1839949 (linux-raspi2), bug 1839968 (linux-snapdragon), bug 
1840800 (linux-aws), bug 1840803 (linux-azure), bug 1840808 (linux-gcp), bug 
1840810 (linux-kvm)
+ derivatives: bug 1839949 (linux-raspi2), bug 1839968 (linux-snapdragon), bug 
1840800 (linux-aws), bug 1840803 (linux-azure), bug 1840808 (linux-gcp), bug 
1840810 (linux-kvm), bug 1842155 (linux-oracle)
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Signoff
  phase-changed: Monday, 26. August 2019 15:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-hwe: bug 1840812
bionic/linux-oem-osp1: bug 1840815
disco/linux-aws: bug 1840800
disco/linux-azure: bug 1840803
disco/linux-gcp: bug 1840808
disco/linux-kvm: bug 1840810
disco/linux-oracle: bug 1840811
disco/linux-raspi2: bug 1839949
disco/linux-snapdragon: bug 1839968
  variant: debs

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

Title:
  disco/linux: 5.0.0-27.28 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed 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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  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

  backports: bug 1840812 (bionic/linux-hwe), bug 1840815 (bionic/linux-oem-osp1)
  derivatives: bug 1839949 (linux-raspi2), bug 1839968 (linux-snapdragon), bug 
1840800 (linux-aws), bug 1840803 (linux-azure), bug 1840808 (linux-gcp), bug 
1840810 (linux-kvm), bug 1842155 (linux-oracle)

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: lin

[Kernel-packages] [Bug 1840826] Re: bionic/linux-oracle-edge: 5.0.0-1001.2~18.04.1 -proposed tracker

[Khaled El Mously]

** Description changed:

  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: 1840811
+ kernel-stable-master-bug: 1842155
  packages:
main: linux-oracle-edge
meta: linux-meta-oracle-edge
signed: linux-signed-oracle-edge
  phase: Ready for Promote to Proposed
  phase-changed: Friday, 30. August 2019 14:55 UTC
  reason:
promote-to-proposed: Stalled -- ready for review
  variant: debs

** Tags removed: kernel-sru-backport-of-1840811

** Tags added: kernel-sru-backport-of-1842155

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

Title:
  bionic/linux-oracle-edge: 5.0.0-1001.2~18.04.1 -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 prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
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:
  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: 1842155
  packages:
main: linux-oracle-edge
meta: linux-meta-oracle-edge
signed: linux-signed-oracle-edge
  phase: Ready for Promote to Proposed
  phase-changed: Friday, 30. August 2019 14:55 UTC
  reason:
promote-to-proposed: Stalled -- ready for review
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840826/+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 1842155] [NEW] disco/linux-oracle: 5.0.0-1002.3 -proposed tracker

[Khaled El Mously]

Public bug reported:

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

backports: bug 1840826 (bionic/linux-oracle-edge)

-- swm properties --
kernel-stable-master-bug: 1840816
packages:
  main: linux-oracle
  meta: linux-meta-oracle
  signed: linux-signed-oracle
phase: Packaging
phase-changed: Friday, 30. August 2019 22:00 UTC
reason:
  prepare-package: Pending -- package not yet uploaded
  prepare-package-meta: Pending -- package not yet uploaded
  prepare-package-signed: Pending -- package not yet uploaded
trackers:
  bionic/linux-oracle-edge: bug 1840826
variant: debs

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: Invalid

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Khaled El Mously (kmously)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Khaled El Mously (kmously)
 Status: In Progress

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Khaled El Mously (kmously)
 Status: In Progress

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux-oracle (Ubuntu Disco)
 Importance: Medium
 Status: Confirmed


** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2019.08.12-10 kernel-sru-derivative-of-1840816

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Tags added: disco kernel-release-tracking-bug

** Also affects: linux-oracle (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Changed in: linux-oracle (Ubuntu Disco)
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

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

[Kernel-packages] [Bug 1839967] Re: disco/linux-oracle: -proposed tracker

[Khaled El Mously]

*** This bug is a duplicate of bug 1842155 ***
https://bugs.launchpad.net/bugs/1842155

** This bug is no longer a duplicate of bug 1840811
   disco/linux-oracle: 5.0.0-1001.2 -proposed tracker
** This bug has been marked a duplicate of bug 1842155
   linux-oracle:  -proposed tracker

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

Title:
  disco/linux-oracle:  -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed 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-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Disco:
  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

  backports: bug 1839966 (bionic/linux-oracle-edge)

  -- swm properties --
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Ready for Packaging
  phase-changed: Tuesday, 13. August 2019 20:14 UTC
  reason:
prepare-package: Pending -- version not specified
  trackers:
bionic/linux-oracle-edge: bug 1839966
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839967/+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 1840811] Re: disco/linux-oracle: 5.0.0-1001.2 -proposed tracker

[Khaled El Mously]

*** This bug is a duplicate of bug 1842155 ***
https://bugs.launchpad.net/bugs/1842155

** Tags removed: kernel-sru-derivative-of-1840816

** Description changed:

  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
  
  backports: bug 1840826 (bionic/linux-oracle-edge)
  
  -- swm properties --
  boot-testing-requested: true
- kernel-stable-master-bug: 1840816
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Testing
  phase-changed: Friday, 30. August 2019 17:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-oracle-edge: bug 1840826
  variant: debs

** This bug has been marked a duplicate of bug 1842155
   linux-oracle:  -proposed tracker

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

Title:
  disco/linux-oracle: 5.0.0-1001.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
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 prepare-package-signed 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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-oracle package in Ubuntu:
  Invalid
Status in linux-oracle source package in Disco:
  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

  backports: bug 1840826 (bionic/linux-oracle-edge)

  -- swm properties --
  boot-testing-requested: true
  packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
  phase: Testing
  phase-changed: Friday, 30. August 2019 17:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-oracle-edge: bug 1840826
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840811/+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 1794232] Re: Geneve tunnels don't work when ipv6 is disabled

[Khaled El Mously]

** 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/1794232

Title:
  Geneve tunnels don't work when ipv6 is disabled

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Released

Bug description:
  SRU Justification

  Impact: Cannot create geneve tunnels if ipv6 is disabled dynamically.

  Fix:
  Fixed by upstream commit in v5.0:
  Commit: cf1c9ccba7308e48a68fa77f476287d9d614e4c7
  "geneve: correctly handle ipv6.disable module parameter"

  Hence available in Disco and later; required in X,B,C.

  Testcase:
  1. Boot with "ipv6.disable=1"
  2. Then try and create a geneve tunnel using:
     # ovs-vsctl add-br br1
     # ovs-vsctl add-port br1 geneve1 -- set interface geneve1
  type=geneve options:remote_ip=192.168.x.z // ip of the other host

  Regression Potential: Low, only geneve tunnels when ipv6 dynamically
  disabled, current status is it doesn't work at all.

  Other Info:
  * Mainline commit msg includes reference to a fix for
    non-metadata tunnels (infrastructure is not yet in
    our tree prior to Disco), hence not being included
    at this time under this case.

    At this time, all geneve tunnels created as above
    are metadata-enabled.

  ---
  [Impact]

  When attempting to create a geneve tunnel on Ubuntu 16.04 Xenial, in
  an OS environment with open vswitch, where ipv6 has been disabled,
  the create fails with the error :

  “ovs-vsctl: Error detected while setting up 'geneve0': could not
  add network device geneve0 to ofproto (Address family not supported
  by protocol)."

  [Fix]
  There is an upstream commit for this in v5.0 mainline (and in Disco and later 
Ubuntu kernels).

  "geneve: correctly handle ipv6.disable module parameter"
  Commit: cf1c9ccba7308e48a68fa77f476287d9d614e4c7

  This fix is needed on all our series prior to Disco
  and the v5.0 kernel: X, C, B. It is identical to the
  fix we implemented and tested internally with, but had
  not pushed upstream yet.

  [Test Case]
  (Best to do this on a kvm guest VM so as not to interfere with
   your system's networking)

  1. On any Ubuntu Xenial kernel, disable ipv6. This example
     is shown with the 4.15.0-23-generic kernel (which differs
     slightly from 4.4.x in symptoms):

  - Edit /etc/default/grub to add the line:
  GRUB_CMDLINE_LINUX="ipv6.disable=1"
  - # update-grub
  - Reboot

  2. Install OVS
  # apt install openvswitch-switch

  3. Create a Geneve tunnel
  # ovs-vsctl add-br br1
  # ovs-vsctl add-port br1 geneve1 -- set interface geneve1
  type=geneve options:remote_ip=192.168.x.z

  (where remote_ip is the IP of the other host)

  You will see the following error message:

  "ovs-vsctl: Error detected while setting up 'geneve1'.
  See ovs-vswitchd log for details."

  From /var/log/openvswitch/ovs-vswitchd.log you will see:

  "2018-07-02T16:48:13.295Z|00026|dpif|WARN|system@ovs-system:
  failed to add geneve1 as port: Address family not supported
  by protocol"

  You will notice from the "ifconfig" output that the device
  genev_sys_6081 is not created.

  If you do not disable IPv6 (remove ipv6.disable=1 from
  /etc/default/grub + update-grub + reboot), the same
  'ovs-vsctl add-port' command completes successfully.
  You can see that it is working properly by adding an
  IP to the br1 and pinging each host.

  On kernel 4.4 (4.4.0-128-generic), the error message doesn't
  happen using the 'ovs-vsctl add-port' command, no warning is
  shown in ovs-vswitchd.log, but the device genev_sys_6081 is
  also not created and ping test won't work.

  With the fixed test kernel, the interfaces and tunnel
  is created successfully.

  [Regression Potential]
  * Low -- affects the geneve driver only, and when ipv6 is
    disabled, and since it doesn't work in that case at all,
    this fix gets the tunnel up and running for the common case.

  [Other Info]

  * Analysis

  Geneve tunnels should work with either IPv4 or IPv6 environments
  as a design and support  principle.

  Currently, however, what's in the implementation requires support
  for ipv6 for metadata-based tunnels which geneve is:

  rather than:

  a) ipv4 + metadata // whether ipv6 compiled or dynamically disabled
  b) ipv4 + metadata + ipv6

  What enforces this in the current 4.4.0-x code when opening a Geneve
  tunnel is the following in geneve_open() :

  bool ipv6 = geneve->remote.sa.sa_family == AF_INET6;
  bool metadata = geneve->collect_md;
  ...

  #if IS_ENABLED(CONFIG_IPV6)
  geneve->sock6 = NULL;
  if

[Kernel-packages] [Bug 1827972] Re: The noise keeps occurring when Headset is plugged in on a Dell machine

[Khaled El Mously]

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

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

** Changed in: linux (Ubuntu Disco)
   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/1827972

Title:
  The noise keeps occurring when Headset is plugged in on a Dell machine

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  Steps to reproduce:
  1. Plug in headset
  2. Select Headset mode

  Expected result:
  There is no noise when headset is plugged in

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1827972/+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 1827880] Re: bionic/linux: completely remove snapdragon files from sources

[Khaled El Mously]

** Changed in: linux (Ubuntu Bionic)
   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/1827880

Title:
  bionic/linux: completely remove snapdragon files from sources

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

Bug description:
  [Impact]

  As requested by bug 1820868, we have split bionic/linux-snapdragon to
  its own source package and own git branch for better maintainability.
  Functionally that split was complete, however some leftover files
  where not removed from the sources leaving some dead files on the
  tree.

  [Fix]

  Sauce patch to remove all the files that were previously used to
  produce the snapdragon binaries from the linux master source.

  [Test Case]

  Compile test bionic/linux source and verify that nothing breaks.

  [Regression potential]

  Minimum. The fix is to remove files that are not being used anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827880/+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 1822871] Re: enabling ftrace on Hi1620 CS causes an Oops

[Khaled El Mously]

** Changed in: linux (Ubuntu Disco)
   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/1822871

Title:
  enabling ftrace on Hi1620 CS causes an Oops

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  Attempting to enable the function tracer causes an Oops. This impacts the 
current disco kernel, as well as latest upstream 
(@5e7a8ca319268a70a6c7c3c1fde5bea38e1e5539).

  This is 100% reproducible on D06 CS systems, but not reproducible on
  D06 ES systems (the previous silicon rev).

  [Test Case]
  $ echo function | sudo tee /sys/kernel/debug/tracing/current_tracer

  [ 3125.651453] kernel BUG at arch/arm64/kernel/insn.c:1325!
  [ 3125.656766] Internal error: Oops - BUG: 0 [#1] SMP
  [ 3125.661551] Modules linked in: nls_iso8859_1 ipmi_ssif joydev input_leds 
tpm_tis_spi hns_roce_hw_v2 hns_roce ib_uverbs spi_dw_mmio ipmi_si spi_dw 
ipmi_devintf ipmi_msghandler cppc_cpufreq 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 xor_neon raid6_pq libcrc32c raid1 
raid0 multipath linear ses enclosure marvell aes_ce_blk aes_ce_cipher hibmc_drm 
hid_generic ttm crct10dif_ce drm_kms_helper ghash_ce sha2_ce syscopyarea 
sha256_arm64 sysfillrect ixgbe igb sha1_ce hns3 sysimgblt usbhid fb_sys_fops 
hisi_sas_v3_hw hclge i2c_algo_bit xfrm_algo hisi_sas_main mdio hid drm hnae3 
libsas ahci scsi_transport_sas hinic gpio_dwapb aes_neon_bs aes_neon_blk 
crypto_simd cryptd aes_arm64
  [ 3125.736544] CPU: 124 PID: 3306 Comm: tee Not tainted 5.0.0-rc4+ #12
  [ 3125.742802] Hardware name: Huawei TaiShan 2280 V2/BC82AMDA, BIOS TA BIOS 
2280-A CS V2.16.01 03/16/2019
  [ 3125.752099] pstate: 0049 (nzcv daif +PAN -UAO)
  [ 3125.756893] pc : aarch64_insn_adrp_get_offset+0x34/0x38
  [ 3125.762111] lr : plt_entries_equal.part.3+0x40/0x80
  [ 3125.766979] sp : 2837b9f0
  [ 3125.770286] x29: 2837b9f0 x28: bef4fd20d880
  [ 3125.775591] x27:  x26: 
  [ 3125.780896] x25: dea2a7e8 x24: 3dceb8413000
  [ 3125.786200] x23: 0002 x22: 3dce9d2289a4
  [ 3125.791504] x21: 2837ba8c x20: 2837b000
  [ 3125.796808] x19: 3dce9d228000 x18: 
  [ 3125.802112] x17:  x16: 3dceb7742780
  [ 3125.807416] x15: 3dceb7ce7c38 x14: 0001
  [ 3125.812720] x13: bef50bb9e188 x12: 
  [ 3125.818023] x11: 7efba3e79608 x10: 0a70
  [ 3125.823327] x9 : 3dceb6deeacc x8 : 
  [ 3125.828631] x7 : 0005 x6 : 3dceb8413f10
  [ 3125.833935] x5 : 002b3000 x4 : 3dceb6f4f4b8
  [ 3125.839239] x3 :  x2 : 9000
  [ 3125.844543] x1 :  x0 : 
  [ 3125.849850] Process tee (pid: 3306, stack limit = 0x262bb476)
  [ 3125.856281] Call trace:
  [ 3125.858723] aarch64_insn_adrp_get_offset+0x34/0x38
  [ 3125.863593] plt_entries_equal.part.3+0x40/0x80
  [ 3125.868115] plt_entries_equal+0x5c/0x70
  [ 3125.872031] ftrace_make_call+0xf0/0x150
  [ 3125.875950] __ftrace_replace_code+0xe8/0xf8
  [ 3125.880212] ftrace_replace_code+0x64/0xc0
  [ 3125.884301] ftrace_modify_all_code+0xb0/0x148
  [ 3125.888738] arch_ftrace_update_code+0x10/0x18
  [ 3125.893174] ftrace_run_update_code+0x20/0x70
  [ 3125.897524] ftrace_startup_enable+0x4c/0x58
  [ 3125.901788] ftrace_startup+0xa4/0x140
  [ 3125.905531] register_ftrace_function+0x64/0x80
  [ 3125.910059] function_trace_init+0x50/0x98
  [ 3125.914149] tracing_set_tracer+0xf4/0x1c0
  [ 3125.918238] tracing_set_trace_write+0x10c/0x168
  [ 3125.922852] __vfs_write+0x60/0x1a8
  [ 3125.926333] vfs_write+0xac/0x1b8
  [ 3125.929641] ksys_write+0x6c/0xd8
  [ 3125.932949] __arm64_sys_write+0x24/0x30
  [ 3125.936866] el0_svc_common+0x78/0x120
  [ 3125.940608] el0_svc_handler+0x38/0x78
  [ 3125.944349] el0_svc+0x8/0xc
  [ 3125.947224] Code: 97fffb33 53144c00 a8c17bfd d65f03c0 (d421)
  [ 3125.953312] ---[ end trace 0872d3e5933385e2 ]---

  [Fix]
  4e69ecf4da1ee arm64/module: ftrace: deal with place relative nature of PLTs
  5a3ae7b314a22 arm64/ftrace: fix inadvertent BUG() in trampoline check

  [Regression Risk]
  TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822871/+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 1813134] Re: cp_abort in powerpc/context_switch from ubunut_kernel_selftests failed on Bionic P9

[Khaled El Mously]

** Changed in: linux (Ubuntu Bionic)
   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/1813134

Title:
  cp_abort in powerpc/context_switch from ubunut_kernel_selftests failed
  on Bionic P9

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == Justification ==
  The cp_abort test in context_switch was designed for Power9, however
  this test is broken and it fails everytime as Paste on Power9 only
  works on accelerators and no longer on real memory.

  == Fix ==
  00c946a0 (selftests/powerpc: Remove redundant cp_abort test)

  This will remove the cp_abort test.
  Patch has already been applied in C and onward.

  == Test ==
  Patch verified on a Bionic P9 system, the test will no longer exist.

  == Regression Potential ==
  None.
  This patchset is just for the kernel testing tool.


  == Original Bug Report ==
  This issue can only be reproduced on Power9 with Bionic kernel.

  $ sudo ./cp_abort
  test: cp_abort
  tags: git_version:c186097-dirty
  !! killing cp_abort
  !! child died by signal 15
  failure: cp_abort

  It will get skipped on P8

  Also to note that this test was completely removed in Cosmic with
  commit 00c946a06e

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 24 07:22 seq
   crw-rw 1 root audio 116, 33 Jan 24 07:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 24 09:06:32 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc.
   Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
   Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro 
console=hvc0
  ProcLoadAvg: 0.07 0.03 0.42 1/1360 33961
  ProcLocks:
   1: FLOCK  ADVISORY  WRITE 3482 00:17:520 0 EOF
   2: POSIX  ADVISORY  WRITE 3746 00:17:580 0 EOF
   3: POSIX  ADVISORY  WRITE 1800 00:17:368 0 EOF
   4: FLOCK  ADVISORY  WRITE 3744 00:17:568 0 EOF
   5: POSIX  ADVISORY  WRITE 3831 00:17:588 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.15.0-44-generic (buildd@bos02-ppc64el-004) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #47-Ubuntu SMP Mon Jan 14 11:26:40 UTC 
2019
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 40
  cpu_coreson: Number of cores online = 40
  cpu_dscr: DSCR is 5
  cpu_freq:
   min: 2.862 GHz (cpu 159)
   max: 2.863 GHz (cpu 1)
   avg: 2.862 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1813134/+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 1813129] Re: tm-unavailable in powerpc/tm failed on Bionic Power9

[Khaled El Mously]

** Changed in: linux (Ubuntu Bionic)
   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/1813129

Title:
  tm-unavailable in powerpc/tm failed on Bionic Power9

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  == Justification ==
  The tm-unavailable test in powerpc from ubuntu_kernel_selftests will fail on 
Bionic PowerPC:
$ sudo ./tm-unavailable
Checking if FP/VEC registers are sane after a FP unavailable exception...
Illegal instruction

  This is because the Hardware Transactional Memory (HTM) is not
  supported on the revision of the processor in our PowerPC boxes.

  == Fix ==
  b395e55b (selftests/powerpc: Skip tm-unavailable if TM is not enabled)
  With a prerequisite to make it a clean cherry-pick: 
  5783ee6e (selftests/powerpc: Check for pthread errors in tm-unavailable)

  An extra check for this test:
 SKIP_IF(!have_htm())

  Will be added to ensure we have HTM support before start testing.

  This patchset has already landed in Cosmic and newer, and can be
  cherry-picked for Bionic.

  For Xenial, we don't have this test in our tree.

  == Test ==
  Patch verified on a Bionic P9 system, the test will be marked as passed 
(skipped) with these two patches applied.

  == Regression potential ==
  None.
  This patch is just for the kernel testing tool.

  
  == Original Bug Report ==
  $ sudo ./tm-unavailable
  Checking if FP/VEC registers are sane after a FP unavailable exception...
  Illegal instruction

  For Power8 it's OK:

  For P9 on Cosmic, this test will be skipped:
   selftests: tm: tm-unavailable
   
   test: tm_unavailable_test
   tags: git_version:unknown
   skip: tm_unavailable_test
   ok 1..10 selftests: tm: tm-unavailable [PASS]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 24 07:22 seq
   crw-rw 1 root audio 116, 33 Jan 24 07:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Jan 24 08:46:56 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc.
   Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
   Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:

  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro 
console=hvc0
  ProcLoadAvg: 0.15 0.10 1.47 1/1357 32937
  ProcLocks:
   1: FLOCK  ADVISORY  WRITE 3482 00:17:520 0 EOF
   2: POSIX  ADVISORY  WRITE 3746 00:17:580 0 EOF
   3: POSIX  ADVISORY  WRITE 1800 00:17:368 0 EOF
   4: FLOCK  ADVISORY  WRITE 3744 00:17:568 0 EOF
   5: POSIX  ADVISORY  WRITE 3831 00:17:588 0 EOF
  ProcSwaps:
   Filename TypeSizeUsedPriority
   /swap.img   file 8388544 0   -2
  ProcVersion: Linux version 4.15.0-44-generic (buildd@bos02-ppc64el-004) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #47-Ubuntu SMP Mon Jan 14 11:26:40 UTC 
2019
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDump_list: total 0
  cpu_cores: Number of cores present = 40
  cpu_coreson: Number of cores online = 40
  cpu_dscr: DSCR is 5
  cpu_freq:
   min: 2.862 GHz (cpu 159)
   max: 2.862 GHz (cpu 3)
   avg: 2.862 GHz
  cpu_runmode:
   Could not retrieve current diagnostics mode,
   No kernel interface to firmware
  cpu_smt: SMT=4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1813129/+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 1787775] Re: touchpad not working on lenovo yoga 530

[Khaled El Mously]

** 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/1787775

Title:
  touchpad not working on lenovo yoga 530

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

Bug description:
  === SRU Justification ===

  [Impact]
  AMD MP2 I2C driver doesn't support more than one bus.
  This makes touchpad on Lenovo Yoga 530 doensn't work as expected.

  [Fix]
  Sync the MP2 driver with upstream version.

  [Test]
  The new upstream driver doesn't break on Latitude 5495.
  Users haven't given any feedback yet, but since Disco is freezing I
  am sending this out.

  [Regression Potential]
  Low. It's from upstream, and only a subset of Raven Ridge has this
  device.

  === Original Bug Report ===

  The touchpad is not working and does not show up in cat
  /proc/bus/input/devices on multiple kernels. I've tried the newest
  kernel to date (19.08.18) and a few others.

  The touchpad works on windows.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-08-18 (0 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.18.3-041803-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to bionic on 2018-08-18 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787775/+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 1828766] [NEW] network-manager ADT tests fail to run properly on bionic

[Khaled El Mously]

Public bug reported:

The network-manager ADT tests are now failing to run on bionic kernel
4.15.0-49.53

amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/n/network-manager/20190506_063857_d8103@/log.gz
arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/n/network-manager/20190506_065519_d8103@/log.gz
armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/armhf/n/network-manager/20190506_063551_d8103@/log.gz
i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/n/network-manager/20190506_063938_d8103@/log.gz
ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/n/network-manager/20190506_064426_d8103@/log.gz
s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/n/network-manager/20190506_063740_d8103@/log.gz

This is clearly a test problem but I haven't been able to figure out
what's wrong.

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


** Tags: 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/1828766

Title:
  network-manager ADT tests fail to run properly on bionic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The network-manager ADT tests are now failing to run on bionic kernel
  4.15.0-49.53

  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/n/network-manager/20190506_063857_d8103@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/n/network-manager/20190506_065519_d8103@/log.gz
  armhf: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/armhf/n/network-manager/20190506_063551_d8103@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/i386/n/network-manager/20190506_063938_d8103@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/n/network-manager/20190506_064426_d8103@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/n/network-manager/20190506_063740_d8103@/log.gz

  This is clearly a test problem but I haven't been able to figure out
  what's wrong.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828766/+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 1826385] Re: ftrace in ubuntu_kernel_selftests hang with Cosmic kernel

[Khaled El Mously]

** 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/1826385

Title:
  ftrace in ubuntu_kernel_selftests hang with Cosmic kernel

Status in ubuntu-kernel-tests:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  == Justification ==
  Running the ftrace in ubuntu_kernel_selftests repetitively against x86 Cosmic 
kernel will cause system hang.

  When this happens, you won't be able to ssh into this system, and no
  log can be found in syslog.

  This hang is caused by one of the sub-test: kprobe/multiple_kprobes

  Masami's comment from upstream discussion 
(https://lkml.org/lkml/2018/12/3/1219):
  In arch/x86/kernel/kprobes/opt.c, copy_optimized_instructions() does a copy 
loop, but only update src and dest cursors, but not update real address which 
is used for adjusting RIP relative instruction.

  == Fix ==
  43a1b0cb4 (kprobes/x86: Fix instruction patching corruption when copying more 
than one RIP-relative instruction)

  This patch is already in D.
  For B/C, they all have this ill-commit 63fef14 and this patch can be 
cherry-picked. Note that for Bionic kernel it can only be triggered in this way 
with a kernel built with GCC-8.

  Although it's a bit difficult to trigger this on Bionic, I think it
  worth this fix as it's quite straightforward.

  For X, the ill-commit 63fef14 does not exist.

  == Test ==
  Test kernel for Cosmic and Bionic built with GCC-8:
  http://people.canonical.com/~phlin/kernel/lp-1826385-ftrace-hang/

  (To verify this for the Bionic, you will need to build a kernel with
  GCC-8.)

  Patch tested with a bare-metal and a KVM node, both of them can pass
  the beating repetitively.

  == Regression Potential ==
  Low, upstream fix specific for kprobe and limited to x86 architecture.


  == Original Bug Report ==
  This issue is a bit strange.

  The test has passed with Cosmic 4.18.0-18.19 generic kernel on AMD64
  node during our SRU testing process.

  https://pastebin.ubuntu.com/p/HN2vN6fCXn/

  However, Tyler found that this test will hang after:
  [30] Kretprobe dynamic event with maxactive   [PASS]
  [31] Register/unregister many kprobe events   [PASS]

  And this is 100% reproducible.

  No relevant output in syslog.

  This will need further investigation.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-18-generic 4.18.0-18.19
  ProcVersionSignature: User Name 4.18.0-18.19-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 25 07:16 seq
   crw-rw 1 root audio 116, 33 Apr 25 07:16 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Apr 25 07:18:51 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:

  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic 
root=UUID=2f68c627-8ab4-40d5-8c06-6563436d0f96 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-18-generic N/A
   linux-backports-modules-4.18.0-18-generic  N/A
   linux-firmware 1.175.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1826385/+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 1829214] Re: linux-azure: 4.15.0-1046.50 -proposed tracker

[Khaled El Mously]

** Summary changed:

- linux-azure:  -proposed tracker
+ linux-azure: 4.15.0-1046.50 -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) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  linux-azure: 4.15.0-1046.50 -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 prepare-package-signed 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 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 stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  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

  backports: bug 1829213 (trusty/linux-azure)
  derivatives: bug 1829212 (linux-azure-edge)

  -- 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/1829214/+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 1829210] Re: linux-oracle: 4.15.0-1013.15 -proposed tracker

[Khaled El Mously]

** Summary changed:

- linux-oracle:  -proposed tracker
+ linux-oracle: 4.15.0-1013.15 -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) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  linux-oracle: 4.15.0-1013.15 -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 prepare-package-signed 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-oracle package in Ubuntu:
  Invalid
Status in linux-oracle 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

  backports: bug 1829208 (xenial/linux-oracle)

  -- 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/1829210/+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 1829180] Re: linux-azure: 4.18.0-1019.19 -proposed tracker

[Khaled El Mously]

** Summary changed:

- linux-azure:  -proposed tracker
+ linux-azure: 4.18.0-1019.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) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  linux-azure: 4.18.0-1019.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 prepare-package-signed 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 stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  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

  backports: bug 1829179 (bionic/linux-azure)

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829180/+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 1829177] Re: linux-aws: 4.18.0-1017.19 -proposed tracker

[Khaled El Mously]

** Summary changed:

- linux-aws:  -proposed tracker
+ linux-aws: 4.18.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) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

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

Title:
  linux-aws: 4.18.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-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Cosmic:
  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

  backports: bug 1829176 (bionic/linux-aws-edge)

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

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

[Khaled El Mously]

** Summary changed:

- linux-gcp:  -proposed tracker
+ linux-gcp: 4.15.0-1033.35 -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) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  linux-gcp: 4.15.0-1033.35 -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 prepare-package-signed 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 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-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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

  backports: bug 1829196 (xenial/linux-gcp)

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829200/+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 1829168] Re: linux-gcp: 5.0.0-1007.7 -proposed tracker

[Khaled El Mously]

** Summary changed:

- linux-gcp:  -proposed tracker
+ linux-gcp: 5.0.0-1007.7 -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) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  linux-gcp: 5.0.0-1007.7 -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 prepare-package-signed 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-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Disco:
  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: 1829173
  phase: Ready for Packaging
  phase-changed: Wednesday, 15. May 2019 11:31 UTC
  reason:
prepare-package: Pending -- version not specified

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829168/+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 1829196] Re: linux-gcp: 4.15.0-1033.35~16.04.1 -proposed tracker

[Khaled El Mously]

** Summary changed:

- linux-gcp:  -proposed tracker
+ linux-gcp: 4.15.0-1033.35~16.04.1 -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) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  linux-gcp: 4.15.0-1033.35~16.04.1 -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 prepare-package-signed 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 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-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  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: 1829200
  phase: Ready for Packaging
  phase-changed: Friday, 17. May 2019 13:41 UTC
  reason:
prepare-package: Pending -- version not specified

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829196/+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 1819656] Re: linux-raspi2: 4.4.0-1105.113 -proposed tracker

[Khaled El Mously]

** Summary changed:

- linux-raspi2:  -proposed tracker
+ linux-raspi2: 4.4.0-1105.113 -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) => Khaled El 
Mously (kmously)

** 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) => Khaled El 
Mously (kmously)

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

Title:
  linux-raspi2: 4.4.0-1105.113 -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-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 Xenial:
  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: 1819660
  phase: Packaging
  phase-changed: Friday, 15. March 2019 04:01 UTC
  reason:
prepare-package: Pending -- version not specified
prepare-package-meta: Pending -- version not specified

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819656/+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 1820151] [NEW] CONFIG_CIFS_POSIX=y needs to added to xenial/raspi2 kernel config

[Khaled El Mously]

Public bug reported:

For xenial/raspi2, we need a commit equivalent to
d05fed02cb6a2e1f39748c25dcd2a00fa2c3b076 from xenial master

** Affects: linux (Ubuntu)
 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/1820151

Title:
  CONFIG_CIFS_POSIX=y needs to added to xenial/raspi2 kernel config

Status in linux package in Ubuntu:
  New

Bug description:
  For xenial/raspi2, we need a commit equivalent to
  d05fed02cb6a2e1f39748c25dcd2a00fa2c3b076 from xenial master

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820151/+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 1820151] Re: CONFIG_CIFS_POSIX=y needs to added to xenial/raspi2 kernel config

[Khaled El Mously]

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

** No longer affects: linux (Ubuntu)

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

** Changed in: linux-raspi2 (Ubuntu Xenial)
   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/1820151

Title:
  CONFIG_CIFS_POSIX=y needs to added to xenial/raspi2 kernel config

Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Xenial:
  Fix Committed

Bug description:
  For xenial/raspi2, we need a commit equivalent to
  d05fed02cb6a2e1f39748c25dcd2a00fa2c3b076 from xenial master

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1820151/+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 1820152] [NEW] CONFIG_CIFS_POSIX=y needs to added to xenial/snapdragon kernel config

[Khaled El Mously]

Public bug reported:

For xenial/snapdragon, we need a commit equivalent to
d05fed02cb6a2e1f39748c25dcd2a00fa2c3b076 from xenial master

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

** Affects: linux-raspi2 (Ubuntu Xenial)
 Importance: Undecided
 Status: Fix Committed

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

** Changed in: linux-raspi2 (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
   CONFIG_CIFS_POSIX=y needs to added to xenial/snapdragon kernel config

Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Xenial:
  Fix Committed

Bug description:
  For xenial/snapdragon, we need a commit equivalent to
  d05fed02cb6a2e1f39748c25dcd2a00fa2c3b076 from xenial master

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1820152/+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 1820152] Re: CONFIG_CIFS_POSIX=y needs to added to xenial/snapdragon kernel config

[Khaled El Mously]

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

** No longer affects: linux-raspi2 (Ubuntu)

** No longer affects: linux-raspi2 (Ubuntu Xenial)

** Changed in: linux-snapdragon (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
   CONFIG_CIFS_POSIX=y needs to added to xenial/snapdragon kernel config

Status in linux-snapdragon package in Ubuntu:
  New
Status in linux-snapdragon source package in Xenial:
  Fix Committed

Bug description:
  For xenial/snapdragon, we need a commit equivalent to
  d05fed02cb6a2e1f39748c25dcd2a00fa2c3b076 from xenial master

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-snapdragon/+bug/1820152/+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