[Kernel-packages] [Bug 1813211] Re: Allow I/O schedulers to be loaded with modprobe in linux-azure

2019-05-31 Thread Marcelo Cerri
** Also affects: linux-azure (Ubuntu Disco)
   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/1813211

Title:
  Allow I/O schedulers to be loaded with modprobe in linux-azure

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

Bug description:
  There was a previous request in bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671203 to limit
  the IO scheduler to NOOP in linux-azure. The other schedulers were
  turned off and NOOP was made the default.

  However with new upstream releases, new schedulers where added and
  linux-azure inherited the default config value for them from the
  master kernel. That's why there are some IO schedulers built as
  modules in the extra package (mq-deadline and kyber-iosched). In order
  to use those two modules, one needs to install the -extra package and
  modprobe the modules first:

  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] 

  # apt install linux-modules-extra-4.15.0-1036-azure

  # modprobe kyber-iosched
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber 

  # modprobe mq-deadline
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber mq-deadline 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber mq-deadline 

  
  The schedulers cfq and deadline have been completely disabled in LP bug 
#1671203 so they cannot be added with modprobe.

  This is a request to move back the cfq and deadline schedulers along
  with the mq-deadline and kyber-iosched schedulers to the main linux-
  azure package (in other words, not in the -extra package) and allow
  the users to be able to modprobe the schedulers when needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1813211/+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 1813211] Re: Allow I/O schedulers to be loaded with modprobe in linux-azure

2019-03-05 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-azure - 4.15.0-1040.44

---
linux-azure (4.15.0-1040.44) xenial; urgency=medium

  * linux-azure: 4.15.0-1040.44 -proposed tracker (LP: #1817038)

  * Packaging resync (LP: #1786013)
- [Packaging] resync retpoline extraction

  * CONFIG_SECURITY_SELINUX_DISABLE should be disabled on 4.15/4.18 Azure
(LP: #1813866)
- [Config]: disable CONFIG_SECURITY_SELINUX_DISABLE
- [Config] Update configs

  * Allow I/O schedulers to be loaded with modprobe in linux-azure
(LP: #1813211)
- [Config] linux-azure: Enable all IO schedulers as modules

  * [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() (LP: #1802021)
- srcu: Prohibit call_srcu() use under raw spinlocks
- srcu: Lock srcu_data structure in srcu_gp_start()

  [ Ubuntu: 4.15.0-46.49 ]

  * linux: 4.15.0-46.49 -proposed tracker (LP: #1814726)
  * mprotect fails on ext4 with dax (LP: #1799237)
- x86/speculation/l1tf: Exempt zeroed PTEs from inversion
  * kernel BUG at /build/linux-vxxS7y/linux-4.15.0/mm/slub.c:296! (LP: #1812086)
- iscsi target: fix session creation failure handling
- scsi: iscsi: target: Set conn->sess to NULL when 
iscsi_login_set_conn_values
  fails
- scsi: iscsi: target: Fix conn_ops double free
  * user_copy in user from ubuntu_kernel_selftests failed on KVM kernel
(LP: #1812198)
- selftests: user: return Kselftest Skip code for skipped tests
- selftests: kselftest: change KSFT_SKIP=4 instead of KSFT_PASS
- selftests: kselftest: Remove outdated comment
  * RTL8822BE WiFi Disabled in Kernel 4.18.0-12 (LP: #1806472)
- SAUCE: staging: rtlwifi: allow RTLWIFI_DEBUG_ST to be disabled
- [Config] CONFIG_RTLWIFI_DEBUG_ST=n
- SAUCE: Add r8822be to signature inclusion list
  * kernel oops in bcache module (LP: #1793901)
- SAUCE: bcache: never writeback a discard operation
  * CVE-2018-18397
- userfaultfd: use ENOENT instead of EFAULT if the atomic copy user fails
- userfaultfd: shmem: allocate anonymous memory for MAP_PRIVATE shmem
- userfaultfd: shmem/hugetlbfs: only allow to register VM_MAYWRITE vmas
- userfaultfd: shmem: add i_size checks
- userfaultfd: shmem: UFFDIO_COPY: set the page dirty if VM_WRITE is not set
  * Ignore "incomplete report" from Elan touchpanels (LP: #1813733)
- HID: i2c-hid: Ignore input report if there's no data present on Elan
  touchpanels
  * Vsock connect fails with ENODEV for large CID (LP: #1813934)
- vhost/vsock: fix vhost vsock cid hashing inconsistent
  * SRU: Fix thinkpad 11e 3rd boot hang (LP: #1804604)
- ACPI / LPSS: Force LPSS quirks on boot
  * Bionic update: upstream stable patchset 2019-01-17 (LP: #1812229)
- scsi: sd_zbc: Fix variable type and bogus comment
- KVM/Eventfd: Avoid crash when assign and deassign specific eventfd in
  parallel.
- x86/apm: Don't access __preempt_count with zeroed fs
- x86/events/intel/ds: Fix bts_interrupt_threshold alignment
- x86/MCE: Remove min interval polling limitation
- fat: fix memory allocation failure handling of match_strdup()
- ALSA: hda/realtek - Add Panasonic CF-SZ6 headset jack quirk
- ARCv2: [plat-hsdk]: Save accl reg pair by default
- ARC: Fix CONFIG_SWAP
- ARC: configs: Remove CONFIG_INITRAMFS_SOURCE from defconfigs
- ARC: mm: allow mprotect to make stack mappings executable
- mm: memcg: fix use after free in mem_cgroup_iter()
- mm/huge_memory.c: fix data loss when splitting a file pmd
- cpufreq: intel_pstate: Register when ACPI PCCH is present
- vfio/pci: Fix potential Spectre v1
- stop_machine: Disable preemption when waking two stopper threads
- drm/i915: Fix hotplug irq ack on i965/g4x
- drm/nouveau: Use drm_connector_list_iter_* for iterating connectors
- drm/nouveau: Avoid looping through fake MST connectors
- gen_stats: Fix netlink stats dumping in the presence of padding
- ipv4: Return EINVAL when ping_group_range sysctl doesn't map to user ns
- ipv6: fix useless rol32 call on hash
- ipv6: ila: select CONFIG_DST_CACHE
- lib/rhashtable: consider param->min_size when setting initial table size
- net: diag: Don't double-free TCP_NEW_SYN_RECV sockets in tcp_abort
- net: Don't copy pfmemalloc flag in __copy_skb_header()
- skbuff: Unconditionally copy pfmemalloc in __skb_clone()
- net/ipv4: Set oif in fib_compute_spec_dst
- net: phy: fix flag masking in __set_phy_supported
- ptp: fix missing break in switch
- qmi_wwan: add support for Quectel EG91
- tg3: Add higher cpu clock for 5762.
- hv_netvsc: Fix napi reschedule while receive completion is busy
- net/mlx4_en: Don't reuse RX page when XDP is set
- net: systemport: Fix CRC forwarding check for SYSTEMPORT Lite
- ipv6: make DAD fail with enhanced DAD when nonce length differs
- net: usb: asix: replace mii_nway_restart in resume path
- alpha: fix osf_wait4() breakage
- 

[Kernel-packages] [Bug 1813211] Re: Allow I/O schedulers to be loaded with modprobe in linux-azure

2019-02-25 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-azure - 4.18.0-1011.11

---
linux-azure (4.18.0-1011.11) cosmic; urgency=medium

  * linux-azure: 4.18.0-1011.11 -proposed tracker (LP: #1816081)

  * 4.15.0-1037 does not see all PCI devices on GPU VMs (LP: #1816106)
- Revert "PCI: hv: Make sure the bus domain is really unique"

linux-azure (4.18.0-1009.9) cosmic; urgency=medium

  * Allow I/O schedulers to be loaded with modprobe in linux-azure
(LP: #1813211)
- [Config] linux-azure: Enable all IO schedulers as modules

  * [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() (LP: #1802021)
- srcu: Lock srcu_data structure in srcu_gp_start()

  * CONFIG_SECURITY_SELINUX_DISABLE should be disabled on 4.15/4.18 Azure
(LP: #1813866)
- [Config]: disable CONFIG_SECURITY_SELINUX_DISABLE

  [ Ubuntu: 4.18.0-15.16 ]

  * Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot) (LP: #1814555)
- Revert "drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for gen4/gen5"
  * Userspace break as a result of missing patch backport (LP: #1813873)
- tty: Don't hold ldisc lock in tty_reopen() if ldisc present

 -- Stefan Bader   Fri, 15 Feb 2019 17:16:24
+0100

** Changed in: linux-azure (Ubuntu)
   Status: Invalid => Fix Released

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

Title:
  Allow I/O schedulers to be loaded with modprobe in linux-azure

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

Bug description:
  There was a previous request in bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671203 to limit
  the IO scheduler to NOOP in linux-azure. The other schedulers were
  turned off and NOOP was made the default.

  However with new upstream releases, new schedulers where added and
  linux-azure inherited the default config value for them from the
  master kernel. That's why there are some IO schedulers built as
  modules in the extra package (mq-deadline and kyber-iosched). In order
  to use those two modules, one needs to install the -extra package and
  modprobe the modules first:

  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] 

  # apt install linux-modules-extra-4.15.0-1036-azure

  # modprobe kyber-iosched
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber 

  # modprobe mq-deadline
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber mq-deadline 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber mq-deadline 

  
  The schedulers cfq and deadline have been completely disabled in LP bug 
#1671203 so they cannot be added with modprobe.

  This is a request to move back the cfq and deadline schedulers along
  with the mq-deadline and kyber-iosched schedulers to the main linux-
  azure package (in other words, not in the -extra package) and allow
  the users to be able to modprobe the schedulers when needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1813211/+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 1813211] Re: Allow I/O schedulers to be loaded with modprobe in linux-azure

2019-02-21 Thread Kleber Sacilotto de Souza
** Also affects: linux-azure (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

Title:
  Allow I/O schedulers to be loaded with modprobe in linux-azure

Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Fix Committed
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released

Bug description:
  There was a previous request in bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671203 to limit
  the IO scheduler to NOOP in linux-azure. The other schedulers were
  turned off and NOOP was made the default.

  However with new upstream releases, new schedulers where added and
  linux-azure inherited the default config value for them from the
  master kernel. That's why there are some IO schedulers built as
  modules in the extra package (mq-deadline and kyber-iosched). In order
  to use those two modules, one needs to install the -extra package and
  modprobe the modules first:

  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] 

  # apt install linux-modules-extra-4.15.0-1036-azure

  # modprobe kyber-iosched
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber 

  # modprobe mq-deadline
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber mq-deadline 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber mq-deadline 

  
  The schedulers cfq and deadline have been completely disabled in LP bug 
#1671203 so they cannot be added with modprobe.

  This is a request to move back the cfq and deadline schedulers along
  with the mq-deadline and kyber-iosched schedulers to the main linux-
  azure package (in other words, not in the -extra package) and allow
  the users to be able to modprobe the schedulers when needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1813211/+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 1813211] Re: Allow I/O schedulers to be loaded with modprobe in linux-azure

2019-02-20 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-azure - 4.18.0-1011.11

---
linux-azure (4.18.0-1011.11) cosmic; urgency=medium

  * linux-azure: 4.18.0-1011.11 -proposed tracker (LP: #1816081)

  * 4.15.0-1037 does not see all PCI devices on GPU VMs (LP: #1816106)
- Revert "PCI: hv: Make sure the bus domain is really unique"

linux-azure (4.18.0-1009.9) cosmic; urgency=medium

  * Allow I/O schedulers to be loaded with modprobe in linux-azure
(LP: #1813211)
- [Config] linux-azure: Enable all IO schedulers as modules

  * [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() (LP: #1802021)
- srcu: Lock srcu_data structure in srcu_gp_start()

  * CONFIG_SECURITY_SELINUX_DISABLE should be disabled on 4.15/4.18 Azure
(LP: #1813866)
- [Config]: disable CONFIG_SECURITY_SELINUX_DISABLE

  [ Ubuntu: 4.18.0-15.16 ]

  * Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot) (LP: #1814555)
- Revert "drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for gen4/gen5"
  * Userspace break as a result of missing patch backport (LP: #1813873)
- tty: Don't hold ldisc lock in tty_reopen() if ldisc present

 -- Stefan Bader   Fri, 15 Feb 2019 17:16:24
+0100

** Changed in: linux-azure (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

** Changed in: linux-azure (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5715

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5753

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5754

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-14625

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-14633

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-15471

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-16882

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-18653

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-18710

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-18955

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-19407

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-5391

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-6559

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-7755

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-9363

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

Title:
  Allow I/O schedulers to be loaded with modprobe in linux-azure

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

Bug description:
  There was a previous request in bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671203 to limit
  the IO scheduler to NOOP in linux-azure. The other schedulers were
  turned off and NOOP was made the default.

  However with new upstream releases, new schedulers where added and
  linux-azure inherited the default config value for them from the
  master kernel. That's why there are some IO schedulers built as
  modules in the extra package (mq-deadline and kyber-iosched). In order
  to use those two modules, one needs to install the -extra package and
  modprobe the modules first:

  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] 

  # apt install linux-modules-extra-4.15.0-1036-azure

  # modprobe kyber-iosched
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber 

  # modprobe mq-deadline
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber mq-deadline 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber mq-deadline 

  
  The schedulers cfq and deadline have been completely disabled in LP bug 
#1671203 so they cannot be added with modprobe.

  This is a request to move back the cfq and deadline schedulers along
  with the mq-deadline and kyber-iosched schedulers to the main linux-
  azure package (in other words, not in the -extra package) and allow
  the users to be able to modprobe the schedulers when needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1813211/+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 1813211] Re: Allow I/O schedulers to be loaded with modprobe in linux-azure

2019-02-14 Thread Marcelo Cerri
That's the expected result. Only multiqueue io schedulers will be
available for multiqueue block devices.

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

Title:
  Allow I/O schedulers to be loaded with modprobe in linux-azure

Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Fix Committed
Status in linux-azure source package in Cosmic:
  Fix Committed

Bug description:
  There was a previous request in bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671203 to limit
  the IO scheduler to NOOP in linux-azure. The other schedulers were
  turned off and NOOP was made the default.

  However with new upstream releases, new schedulers where added and
  linux-azure inherited the default config value for them from the
  master kernel. That's why there are some IO schedulers built as
  modules in the extra package (mq-deadline and kyber-iosched). In order
  to use those two modules, one needs to install the -extra package and
  modprobe the modules first:

  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] 

  # apt install linux-modules-extra-4.15.0-1036-azure

  # modprobe kyber-iosched
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber 

  # modprobe mq-deadline
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber mq-deadline 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber mq-deadline 

  
  The schedulers cfq and deadline have been completely disabled in LP bug 
#1671203 so they cannot be added with modprobe.

  This is a request to move back the cfq and deadline schedulers along
  with the mq-deadline and kyber-iosched schedulers to the main linux-
  azure package (in other words, not in the -extra package) and allow
  the users to be able to modprobe the schedulers when needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1813211/+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 1813211] Re: Allow I/O schedulers to be loaded with modprobe in linux-azure

2019-02-14 Thread David Coronel
[VERIFICATION BIONIC]

I can modprobe the mq-deadline, kyber and bfq schedulers but it looks
like doing a modprobe of the cfq and deadline schedulers doesn't list
them as choices in the available schedulers:

# uname -r
4.18.0-1009-azure

# modprobe bfq
# modprobe cfq-iosched
# modprobe mq-deadline
# modprobe kyber-iosched
# modprobe deadline-iosched

# tail /sys/block/sda/queue/scheduler
[none] mq-deadline kyber bfq 

I have these 4.18 kernel packages installed:

# dpkg -l | grep 4.18 | grep linux
ii  linux-azure 4.18.0.1009.9
ii  linux-azure-cloud-tools-4.18.0-1009 4.18.0-1009.9~18.04.1
ii  linux-azure-headers-4.18.0-1009 4.18.0-1009.9~18.04.1
ii  linux-azure-tools-4.18.0-1009   4.18.0-1009.9~18.04.1
ii  linux-cloud-tools-4.18.0-1009-azure 4.18.0-1009.9~18.04.1
ii  linux-cloud-tools-azure 4.18.0.1009.9
ii  linux-headers-4.18.0-1009-azure 4.18.0-1009.9~18.04.1
ii  linux-headers-azure 4.18.0.1009.9
ii  linux-image-4.18.0-1009-azure   4.18.0-1009.9~18.04.1
ii  linux-image-azure   4.18.0.1009.9
ii  linux-modules-4.18.0-1009-azure 4.18.0-1009.9~18.04.1
ii  linux-tools-4.18.0-1009-azure   4.18.0-1009.9~18.04.1
ii  linux-tools-azure   4.18.0.1009.9

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

Title:
  Allow I/O schedulers to be loaded with modprobe in linux-azure

Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Fix Committed
Status in linux-azure source package in Cosmic:
  Fix Committed

Bug description:
  There was a previous request in bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671203 to limit
  the IO scheduler to NOOP in linux-azure. The other schedulers were
  turned off and NOOP was made the default.

  However with new upstream releases, new schedulers where added and
  linux-azure inherited the default config value for them from the
  master kernel. That's why there are some IO schedulers built as
  modules in the extra package (mq-deadline and kyber-iosched). In order
  to use those two modules, one needs to install the -extra package and
  modprobe the modules first:

  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] 

  # apt install linux-modules-extra-4.15.0-1036-azure

  # modprobe kyber-iosched
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber 

  # modprobe mq-deadline
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber mq-deadline 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber mq-deadline 

  
  The schedulers cfq and deadline have been completely disabled in LP bug 
#1671203 so they cannot be added with modprobe.

  This is a request to move back the cfq and deadline schedulers along
  with the mq-deadline and kyber-iosched schedulers to the main linux-
  azure package (in other words, not in the -extra package) and allow
  the users to be able to modprobe the schedulers when needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1813211/+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 1813211] Re: Allow I/O schedulers to be loaded with modprobe in linux-azure

2019-02-14 Thread Brad Figg
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

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

Title:
  Allow I/O schedulers to be loaded with modprobe in linux-azure

Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Fix Committed
Status in linux-azure source package in Cosmic:
  Fix Committed

Bug description:
  There was a previous request in bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671203 to limit
  the IO scheduler to NOOP in linux-azure. The other schedulers were
  turned off and NOOP was made the default.

  However with new upstream releases, new schedulers where added and
  linux-azure inherited the default config value for them from the
  master kernel. That's why there are some IO schedulers built as
  modules in the extra package (mq-deadline and kyber-iosched). In order
  to use those two modules, one needs to install the -extra package and
  modprobe the modules first:

  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] 

  # apt install linux-modules-extra-4.15.0-1036-azure

  # modprobe kyber-iosched
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber 

  # modprobe mq-deadline
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber mq-deadline 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber mq-deadline 

  
  The schedulers cfq and deadline have been completely disabled in LP bug 
#1671203 so they cannot be added with modprobe.

  This is a request to move back the cfq and deadline schedulers along
  with the mq-deadline and kyber-iosched schedulers to the main linux-
  azure package (in other words, not in the -extra package) and allow
  the users to be able to modprobe the schedulers when needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1813211/+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 1813211] Re: Allow I/O schedulers to be loaded with modprobe in linux-azure

2019-02-06 Thread Marcelo Cerri
** Changed in: linux-azure (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: linux-azure (Ubuntu Cosmic)
   Status: New => Fix Committed

** Changed in: linux-azure (Ubuntu)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

** Changed in: linux-azure (Ubuntu Bionic)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

** Changed in: linux-azure (Ubuntu Cosmic)
 Assignee: (unassigned) => Marcelo Cerri (mhcerri)

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

Title:
  Allow I/O schedulers to be loaded with modprobe in linux-azure

Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Fix Committed
Status in linux-azure source package in Cosmic:
  Fix Committed

Bug description:
  There was a previous request in bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671203 to limit
  the IO scheduler to NOOP in linux-azure. The other schedulers were
  turned off and NOOP was made the default.

  However with new upstream releases, new schedulers where added and
  linux-azure inherited the default config value for them from the
  master kernel. That's why there are some IO schedulers built as
  modules in the extra package (mq-deadline and kyber-iosched). In order
  to use those two modules, one needs to install the -extra package and
  modprobe the modules first:

  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] 

  # apt install linux-modules-extra-4.15.0-1036-azure

  # modprobe kyber-iosched
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber 

  # modprobe mq-deadline
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber mq-deadline 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber mq-deadline 

  
  The schedulers cfq and deadline have been completely disabled in LP bug 
#1671203 so they cannot be added with modprobe.

  This is a request to move back the cfq and deadline schedulers along
  with the mq-deadline and kyber-iosched schedulers to the main linux-
  azure package (in other words, not in the -extra package) and allow
  the users to be able to modprobe the schedulers when needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1813211/+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 1813211] Re: Allow I/O schedulers to be loaded with modprobe in linux-azure

2019-02-04 Thread Kleber Sacilotto de Souza
** Also affects: linux-azure (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

** Changed in: linux-azure (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Allow I/O schedulers to be loaded with modprobe in linux-azure

Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  New
Status in linux-azure source package in Cosmic:
  New

Bug description:
  There was a previous request in bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671203 to limit
  the IO scheduler to NOOP in linux-azure. The other schedulers were
  turned off and NOOP was made the default.

  However with new upstream releases, new schedulers where added and
  linux-azure inherited the default config value for them from the
  master kernel. That's why there are some IO schedulers built as
  modules in the extra package (mq-deadline and kyber-iosched). In order
  to use those two modules, one needs to install the -extra package and
  modprobe the modules first:

  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] 

  # apt install linux-modules-extra-4.15.0-1036-azure

  # modprobe kyber-iosched
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber 

  # modprobe mq-deadline
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber mq-deadline 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber mq-deadline 

  
  The schedulers cfq and deadline have been completely disabled in LP bug 
#1671203 so they cannot be added with modprobe.

  This is a request to move back the cfq and deadline schedulers along
  with the mq-deadline and kyber-iosched schedulers to the main linux-
  azure package (in other words, not in the -extra package) and allow
  the users to be able to modprobe the schedulers when needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1813211/+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 1813211] Re: Allow I/O schedulers to be loaded with modprobe in linux-azure

2019-01-31 Thread Joshua R. Poulson
** Changed in: linux-azure (Ubuntu)
   Status: New => Confirmed

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

Title:
  Allow I/O schedulers to be loaded with modprobe in linux-azure

Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  There was a previous request in bug
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671203 to limit
  the IO scheduler to NOOP in linux-azure. The other schedulers were
  turned off and NOOP was made the default.

  However with new upstream releases, new schedulers where added and
  linux-azure inherited the default config value for them from the
  master kernel. That's why there are some IO schedulers built as
  modules in the extra package (mq-deadline and kyber-iosched). In order
  to use those two modules, one needs to install the -extra package and
  modprobe the modules first:

  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] 

  # apt install linux-modules-extra-4.15.0-1036-azure

  # modprobe kyber-iosched
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber 

  # modprobe mq-deadline
  # tail /sys/block/sd*/queue/scheduler
  ==> /sys/block/sda/queue/scheduler <==
  [none] kyber mq-deadline 

  ==> /sys/block/sdb/queue/scheduler <==
  [none] kyber mq-deadline 

  
  The schedulers cfq and deadline have been completely disabled in LP bug 
#1671203 so they cannot be added with modprobe.

  This is a request to move back the cfq and deadline schedulers along
  with the mq-deadline and kyber-iosched schedulers to the main linux-
  azure package (in other words, not in the -extra package) and allow
  the users to be able to modprobe the schedulers when needed.

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