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  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20170504210626.GN25821@shells.gnugeneration.com>
Date:   Thu, 4 May 2017 14:06:26 -0700
From:   vcaputo@...garu.com
To:     linux-kernel <linux-kernel@...r.kernel.org>
Subject: [REGRESSION] 4.11.0-rc8 ext4 mount randomly returning EBUSY during
 boot w/systemd?

I'm not sure about this one, but never experienced it prior to 4.11.0-rc8.

During boot sometimes the home.mount unit fails and `systemctl status
home.mount` reports that the mount failed due to it already being busy.

I'm able to fix it by simply issuing `systemctl restart home.mount` from the
maintenance shell, ^d and the boot resumes normally.

This is a plain Debian Jessie amd64 system, with dmcrypt and lvm2.

Is this a known kernel regression that got fixed already?  It's possible this
is an unrelated systemd bug, but it's odd that I never saw this before this
kernel.

Unfortunately I've been too busy the last few weeks to spend much time on the
computer in rc8+, so this is all a bit nebulous.

Regards,
Vito Caputo

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ