lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Tue, 09 Apr 2019 07:57:29 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 104571] ext4_mb_generate_buddy block bitmap and bg descriptor
 inconsistent

https://bugzilla.kernel.org/show_bug.cgi?id=104571

dpsenner (dpsenner@...il.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dpsenner@...il.com

--- Comment #6 from dpsenner (dpsenner@...il.com) ---
We were recently hit by this issue, too on a physical x64 machine that hosts
one kvm virtual machine guest with a windows server 2016 x64 operating system.
The filesystem is a mdadm software raid1 spanning over two disks with ext4
on-top.

$ uname -r
4.15.0-43-generic

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.1 LTS
Release:        18.04
Codename:       bionic

The filesystem of the physical machine went read only and effectively crashed
all processes, including the guest operating system. A hard reset and disk
check appears to have solved the symptom, but we have mixed feelings since we
don't know about any collateral damage this may have caused. dmesg displays
worrying information that is hopefully not a symptom of irreversible root
filesystem corruption:

systemd-journald[457]: File
/var/log/journal/7346ea28f12b763f29b8995058d63291/user-1000.journal corrupted
or uncleanly shut down, renaming and replacing.

The symptom manifested while booting the guest machine and thus may well be
related to a burst of random reads and writes of the kvm guest. We observed
moderate disk activity in htop.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

Powered by blists - more mailing lists