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: <000d01cf5d53$d6394560$82abd020$@petrovi.no-ip.info>
Date:	Mon, 21 Apr 2014 14:21:27 +0300
From:	Пламен Петров <plamen@...rovi.no-ip.info>
To:	<linux-kernel@...r.kernel.org>
Subject: kernel panic during boot - 3.14.1, root is btrfs

Hello!
I was trying to move several systems which have their root formatted as
btrfs from 3.13.x to 3.14.x and the kernel panicked during boot.
Is there anything special that needs to be done as to prepare an
in-use-btrfs-root for kernel >=3.14 ?
I bisected the problem to a btrfs commit, although I'm not entirely sure its
100% correct.
The systems are one physical machine and a couple of virtual ones. Since I
bisected this the physical one was converted to XFS root - it's a production
machine with real users.
More details on bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=74261
Greg KH says that 3.13.11 will be the last of the series, and advises to
move on to 3.14.x - but currently that is impossible for me (bar converting
the root to different FS).
Can someone think of something to help this situation?

P.S. Please, CC me as I'm not subscribed to the kernel mailing list.
---------------------------------
Plamen Petrov

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ