This bug was fixed in the package linux - 4.8.0-30.32
---
linux (4.8.0-30.32) yakkety; urgency=low
* CVE-2016-8655 (LP: #1646318)
- packet: fix race condition in packet_set_ring
-- Brad Figg Thu, 01 Dec 2016 08:02:53 -0800
** Changed in: linux (Ubuntu Zesty)
Status:
This bug was fixed in the package linux - 4.8.0-28.30
---
linux (4.8.0-28.30) yakkety; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1641083
* lxc-attach to malicious container allows access to host (LP: #1639345)
- Revert "UBUNTU: SAUCE: (noup) ptrace:
This bug was fixed in the package linux - 4.4.0-51.72
---
linux (4.4.0-51.72) xenial; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1644611
* 4.4.0-1037-snapdragon #41: kernel panic on boot (LP: #1644596)
- Revert "dma-mapping: introduce the DMA_ATTR_NO_
FTR/FYI (as per chatter w/kamal) we're waiting for >= 4.8.0-28
to be available at https://launchpad.net/ubuntu/+source/linux-hwe-edge
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638700
Title:
hio
Corruption no longer visible with 4.4.0-49-generic:
https://pastebin.canonical.com/171039/
Testing with Yakkety proper would be messy - what's the timeline for
getting an updated 4.8 kernel into Xenial? I currently only see
4.8.0-27.29~16.04.1.
** Tags removed: verification-needed-xenial
**
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-
yakkety' to 'verification-done-yakkety'.
If verification is not done by 5 working days from
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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Yakkety)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
https://lists.ubuntu.com/archives/kernel-team/2016-November/080705.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638700
Title:
hio: SSD data corruption under stress test
To manage notificatio
** Tags added: canonical-bootstack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638700
Title:
hio: SSD data corruption under stress test
To manage notifications about this bug go to:
https://bugs
On Thu, Nov 3, 2016 at 5:42 AM, Kamal Mostafa wrote:
> Ming Lei comment #2 says you're the author of this patch to the hio
> driver:
>
> +#if (LINUX_VERSION_CODE >= KERNEL_VERSION(4,3,0))
> + blk_queue_split(q, &bio, q->bio_split);
> +#endif
> +
>
> Can you provide us with a short explanatio
On Wed, Nov 2, 2016 at 2:08 PM, James Troup
wrote:
> I've confirmed the corruption is gone with the two fixes above on both
4.4 and 4.8.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638700
Title:
Ming Lei comment #2 says you're the author of this patch to the hio
driver:
+#if (LINUX_VERSION_CODE >= KERNEL_VERSION(4,3,0))
+ blk_queue_split(q, &bio, q->bio_split);
+#endif
+
Can you provide us with a short explanation for the git log, and also
your Signed-off-by line for that patch?
-
James, thanks for clarifying that. In that case, all my references to
"hio driver 2.1.0.26" should actually say "the patch set James is
testing", and the two fixes should still likely both be applied to the
Ubuntu hio driver.
--
You received this bug notification because you are a member of Ubun
Side-note about bug in hio driver 2.1.0.26 (#1: bio_endio() shim macro
sets bi_error field). This turns out NOT the cause of this data
corruption bug per James' testing, but should be corrected (both in the
upstream driver and Ubuntu).
The idea behind this change is correct (the macro shim should
(Also 2.1.0.26 is not public yet for reasons Huawei are trying to figure
out, 2.1.0.25 is the last publicly available driver.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638700
Title:
hio: SSD d
Sorry - for the avoidance of doubt, neither of these changes are in
2.1.0.26 - 2.1.0.26 doesn't even include your patches. I was testing
2.1.0.26 + our patches + the 2 changes you mention. #1 does come from
Huawei, #2 comes from Ming Lei of Canonical.
--
You received this bug notification becau
Huawei's upstream hio driver version 2.1.0.26 introduces two changes
relative to the current Ubuntu version:
#1. bio_endio() shim macro sets bi_error field {{ but note bug in
implementation! }}
#2. blk_queue_split() call inserted ssd_make_request()
James' initial test results indicate that #2 ap
18 matches
Mail list logo
