[Kernel-packages] [Bug 1838619] Re: Turn off nvme driver on raspi2

2019-09-30 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-raspi2 - 4.15.0-1048.52

---
linux-raspi2 (4.15.0-1048.52) bionic; urgency=medium

  * bionic/linux-raspi2: 4.15.0-1048.52 -proposed tracker (LP: #1844372)

  * arm64: large modules fail to load (LP: #1841109)
- [config] Remove CONFIG_ARM64_MODULE_CMODEL_LARGE

  * Turn off nvme driver on raspi2 (LP: #1838619)
- [Config] disable NVME

  [ Ubuntu: 4.15.0-65.74 ]

  * bionic/linux: 4.15.0-65.74 -proposed tracker (LP: #1844403)
  * arm64: large modules fail to load (LP: #1841109)
- arm64/kernel: kaslr: reduce module randomization range to 4 GB
- arm64/kernel: don't ban ADRP to work around Cortex-A53 erratum #843419
- arm64: fix undefined reference to 'printk'
- arm64/kernel: rename module_emit_adrp_veneer->module_emit_veneer_for_adrp
- [config] Remove CONFIG_ARM64_MODULE_CMODEL_LARGE
  * CVE-2018-20976
- xfs: clear sb->s_fs_info on mount failure
  * br_netfilter: namespace sysctl operations (LP: #1836910)
- net: bridge: add bitfield for options and convert vlan opts
- net: bridge: convert nf call options to bits
- netfilter: bridge: port sysctls to use brnf_net
- netfilter: bridge: namespace bridge netfilter sysctls
- netfilter: bridge: prevent UAF in brnf_exit_net()
  * tuntap: correctly set SOCKWQ_ASYNC_NOSPACE (LP: #1830756)
- tuntap: correctly set SOCKWQ_ASYNC_NOSPACE
  * Bionic update: upstream stable patchset 2019-08-30 (LP: #1842114)
- HID: Add 044f:b320 ThrustMaster, Inc. 2 in 1 DT
- MIPS: kernel: only use i8253 clocksource with periodic clockevent
- mips: fix cacheinfo
- netfilter: ebtables: fix a memory leak bug in compat
- ASoC: dapm: Fix handling of custom_stop_condition on DAPM graph walks
- bonding: Force slave speed check after link state recovery for 802.3ad
- can: dev: call netif_carrier_off() in register_candev()
- ASoC: Fail card instantiation if DAI format setup fails
- st21nfca_connectivity_event_received: null check the allocation
- st_nci_hci_connectivity_event_received: null check the allocation
- ASoC: ti: davinci-mcasp: Correct slot_width posed constraint
- net: usb: qmi_wwan: Add the BroadMobi BM818 card
- qed: RDMA - Fix the hw_ver returned in device attributes
- isdn: mISDN: hfcsusb: Fix possible null-pointer dereferences in
  start_isoc_chain()
- netfilter: ipset: Fix rename concurrency with listing
- isdn: hfcsusb: Fix mISDN driver crash caused by transfer buffer on the 
stack
- perf bench numa: Fix cpu0 binding
- can: sja1000: force the string buffer NULL-terminated
- can: peak_usb: force the string buffer NULL-terminated
- net/ethernet/qlogic/qed: force the string buffer NULL-terminated
- NFSv4: Fix a potential sleep while atomic in nfs4_do_reclaim()
- HID: input: fix a4tech horizontal wheel custom usage
- SMB3: Kernel oops mounting a encryptData share with CONFIG_DEBUG_VIRTUAL
- net: cxgb3_main: Fix a resource leak in a error path in 'init_one()'
- net: hisilicon: make hip04_tx_reclaim non-reentrant
- net: hisilicon: fix hip04-xmit never return TX_BUSY
- net: hisilicon: Fix dma_map_single failed on arm64
- libata: have ata_scsi_rw_xlat() fail invalid passthrough requests
- libata: add SG safety checks in SFF pio transfers
- x86/lib/cpu: Address missing prototypes warning
- drm/vmwgfx: fix memory leak when too many retries have occurred
- perf ftrace: Fix failure to set cpumask when only one cpu is present
- perf cpumap: Fix writing to illegal memory in handling cpumap mask
- perf pmu-events: Fix missing "cpu_clk_unhalted.core" event
- selftests: kvm: Adding config fragments
- HID: wacom: correct misreported EKR ring values
- HID: wacom: Correct distance scale for 2nd-gen Intuos devices
- Revert "dm bufio: fix deadlock with loop device"
- ceph: don't try fill file_lock on unsuccessful GETFILELOCK reply
- libceph: fix PG split vs OSD (re)connect race
- drm/nouveau: Don't retry infinitely when receiving no data on i2c over AUX
- gpiolib: never report open-drain/source lines as 'input' to user-space
- userfaultfd_release: always remove uffd flags and clear vm_userfaultfd_ctx
- x86/retpoline: Don't clobber RFLAGS during CALL_NOSPEC on i386
- x86/apic: Handle missing global clockevent gracefully
- x86/CPU/AMD: Clear RDRAND CPUID bit on AMD family 15h/16h
- x86/boot: Save fields explicitly, zero out everything else
- x86/boot: Fix boot regression caused by bootparam sanitizing
- dm kcopyd: always complete failed jobs
- dm btree: fix order of block initialization in btree_split_beneath
- dm space map metadata: fix missing store of apply_bops() return value
- dm table: fix invalid memory accesses with too high sector number
- dm zoned: improve error handling in reclaim
- dm zoned: improve error handling in i/o map code
- dm zoned: properly handle backing 

[Kernel-packages] [Bug 1838619] Re: Turn off nvme driver on raspi2

2019-09-03 Thread Kleber Sacilotto de Souza
** Changed in: linux-raspi2 (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-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1838619

Title:
  Turn off nvme driver on raspi2

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

Bug description:
  Impact:

  We recently adjusted CONFIG_NVM to fix a build failure. The change
  causing this was actually a mis-merge and will be reverted. However
  the question came up whether it makes sense at all to build any
  raspberry kernel with NVME support at all. There currently is no way
  to attach any NVME to a raspberry pi, so lets turn off driver support
  for it for that kernel in total.

  Fix:

  Disable the relevant config options:

  # CONFIG_NVM is not set
  ...
  # CONFIG_NVME_FC is not set
  # CONFIG_NVME_TARGET is not set

  
  Regression potential:

  None, we are disabling support for a piece of hardware that doesn't
  exist on the RaspberryPi boards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1838619/+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 1838619] Re: Turn off nvme driver on raspi2

2019-09-02 Thread Kleber Sacilotto de Souza
** Changed in: linux-raspi2 (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: linux-raspi2 (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux-raspi2 (Ubuntu Bionic)
   Importance: Undecided => Wishlist

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

Title:
  Turn off nvme driver on raspi2

Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 source package in Bionic:
  In Progress

Bug description:
  Impact:

  We recently adjusted CONFIG_NVM to fix a build failure. The change
  causing this was actually a mis-merge and will be reverted. However
  the question came up whether it makes sense at all to build any
  raspberry kernel with NVME support at all. There currently is no way
  to attach any NVME to a raspberry pi, so lets turn off driver support
  for it for that kernel in total.

  Fix:

  Disable the relevant config options:

  # CONFIG_NVM is not set
  ...
  # CONFIG_NVME_FC is not set
  # CONFIG_NVME_TARGET is not set

  
  Regression potential:

  None, we are disabling support for a piece of hardware that doesn't
  exist on the RaspberryPi boards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1838619/+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 1838619] Re: Turn off nvme driver on raspi2

2019-09-02 Thread Paolo Pisati
** Description changed:

+ Impact:
+ 
  We recently adjusted CONFIG_NVM to fix a build failure. The change
  causing this was actually a mis-merge and will be reverted. However the
  question came up whether it makes sense at all to build any raspberry
  kernel with NVME support at all. There currently is no way to attach any
  NVME to a raspberry pi, so lets turn off driver support for it for that
  kernel in total.
+ 
+ Fix:
+ 
+ Disable the relevant config options:
+ 
+ # CONFIG_NVM is not set
+ ...
+ # CONFIG_NVME_FC is not set
+ # CONFIG_NVME_TARGET is not set
+ 
+ 
+ Regression potential:
+ 
+ None, we are disabling support for a piece of hardware that doesn't
+ exist on the RaspberryPi boards.

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

Title:
  Turn off nvme driver on raspi2

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

Bug description:
  Impact:

  We recently adjusted CONFIG_NVM to fix a build failure. The change
  causing this was actually a mis-merge and will be reverted. However
  the question came up whether it makes sense at all to build any
  raspberry kernel with NVME support at all. There currently is no way
  to attach any NVME to a raspberry pi, so lets turn off driver support
  for it for that kernel in total.

  Fix:

  Disable the relevant config options:

  # CONFIG_NVM is not set
  ...
  # CONFIG_NVME_FC is not set
  # CONFIG_NVME_TARGET is not set

  
  Regression potential:

  None, we are disabling support for a piece of hardware that doesn't
  exist on the RaspberryPi boards.

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