** Tags added: cscc
--
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/1789131
Title:
Probable regression with EXT3 file systems and CVE-2018-1093 patches
Status in linux package in Ubuntu:
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
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/1789131
Title:
Probable regression with EXT3 file systems and CVE-
This bug was fixed in the package linux - 3.13.0-160.210
---
linux (3.13.0-160.210) trusty; urgency=medium
* CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
* CVE-2018-14634
- exec: Limit arg stack to at most 75% of _STK_LIM
linux (3.13.0-159.20
I can confirm that the kernel 3.13.0-159-generic from trusty-proposed
solves the problem.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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-
trusty' to 'verification-done-trusty'. If the problem still exists,
change the tag 'verifica
** Changed in: linux (Ubuntu Trusty)
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/1789131
Title:
Probable regression with EXT3 file systems
SRU Request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-August/095106.html
** Description changed:
+
+ == SRU Justification ==
+ Mainline commit 7dac4a1726a9 introduced a regression in v4.17-rc1, which
+ made it's way into Trusty via upstream stable updates. This regression
+
I opened another bug for the 16.04 because the cause is not the patch
CVE-2018-1093 :
1789653 : regression with EXT4 file systems and meta_bg flag
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-1093
--
You received this bug notification because you are a member of Kernel
Pack
Impacted also in 16.04 lts (kernel 4.4.0-134-generic ) with all
partitions in ext4 with flag meta_bg :
ext4_check_descriptors: block bitmap for group 0 overlaps block group
descriptors
the flag meta_bg activates automatically by warming up a partition above
60GB (with lvextend and resize2fs).
go
Thanks for testing, Sarah. I'll submit an SRU request to have this
commit included in Trusty.
This regression was introduced by the following mainline commit:
7dac4a1726a9 ("ext4: add validity checks for bitmap block numbers")
This commit was added to mainline in version v4.17-rc1. However, the
On 08/28/2018 09:49 AM, Joseph Salisbury wrote:
> This is probably the fix:
> 22be37acce25 ext4: fix bitmap position validation
>
> I built a test kernel with commit 22be37acce25. The test kernel can be
> downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1789131
>
> Can you test this ke
This is probably the fix:
22be37acce25 ext4: fix bitmap position validation
I built a test kernel with commit 22be37acce25. The test kernel can be
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1789131
Can you test this kernel and see if it resolves this bug?
Note about installing tes
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Trusty)
On 08/27/2018 01:21 PM, Joseph Salisbury wrote:
> Does 3.13.0-157.207 exhibit the bug and 3.13.0-156.206 does not? If
> that is the case, we can perform a bisect to identify the offending
> commit.
That is correct.
--
You received this bug notification because you are a member of Kernel
Package
Does 3.13.0-157.207 exhibit the bug and 3.13.0-156.206 does not? If
that is the case, we can perform a bisect to identify the offending
commit.
** Changed in: linux (Ubuntu Trusty)
Status: Incomplete => Triaged
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
You re
On 08/27/2018 11:16 AM, Joseph Salisbury wrote:
> The specific version to test is 3.13.0-158.
>
No, that doesn't fix it.
root@scratch2:~# uname -a
Linux scratch2 3.13.0-158-generic #208-Ubuntu SMP Fri Aug 24 17:07:38 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
root@scratch2:~# dmesg | grep mount
[
The specific version to test is 3.13.0-158.
--
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/1789131
Title:
Probable regression with EXT3 file systems and CVE-2018-1093 patches
Status in
Would it be possible for you to test the proposed kernel and post back if it
resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.
Thank you in advance!
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Also a
This problem doesn't show up in 4.4.0-134-generic.
--
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/1789131
Title:
Probable regression with EXT3 file systems and CVE-2018-1093 patches
Sta
As for running
apport-collect 1789131
This doesn't appear to work well in a headless system with a minimal
install. I believe I've given all the necessary details for reproducing
the issue.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notificati
I believe a command sequence like this can be used to reliably reproduce
the issue:
umount /mnt
truncate -s128m /tmp/test.img
cmd="/sbin/mkfs.ext3 -E stride=128,stripe_width=512 -F /tmp/test.img"
echo $cmd > /dev/kmsg
$cmd
mount -o loop /tmp/test.img /mnt/
while dd if=/dev/zero of=/mnt/$RANDOM bs=
I confirmed that adding "-E stride=128,stripe_width=512" to the call to
mkfs results gets the following errors almost immediately at boot with
3.13.0-157.207:
[5.680480] EXT4-fs error (device xvda1): ext4_validate_block_bitmap:376:
comm mountall: bg 213: block 7007360: invalid block bitmap
[
I noticed the unusual thing here is:
RAID stride: 128
RAID stripe width: 512
I'm going to do some testing around this to see if it's related. It
could be this is the issue and not anything EXT3 vs. EXT4.
--
You received this bug notification because you are a member of Kernel
Packages, which is
23 matches
Mail list logo
