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-
cosmic' to 'verification-done-cosmic'. If the problem still exists,
change the tag 'verification-needed-cosmic' to 'verification-failed-
cosmic'.

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-cosmic

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

Title:
  potential memory corruption on arm64 on dev release

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:
  [Impact]
  Potential memory corruption.

  [Test Case]
  I've not seen a failure in practice (well, it's easy to crash 5.0 but, as the 
commit message notes, that's because it includes an additional patch that 
happens to "tickle" this. But to regression test, I boot a HiSilicon D06 to a 
ramdisk and remove the hisi_sas_v3_hw module, which allocates memory as 
described in the commit message.

  [Fix]
  376991db4b646 driver core: Postpone DMA tear-down until after devres release

  [Regression Risk]
  From the stable tree, so in theory would be applied eventually anyway.

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

Reply via email to