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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHnuAexhYVpBg3Hq9i79Yt7LmiAxaf=ZDFR14=EOQCd8HiwyuA@mail.gmail.com>
Date:	Tue, 1 Apr 2014 09:01:55 +0200
From:	Daniel Smedegaard Buus <danielbuus@...il.com>
To:	Sitsofe Wheeler <sitsofe@...oo.com>
Cc:	Kent Overstreet <kmo@...erainc.com>,
	Nicholas Swenson <nks@...erainc.com>,
	linux-bcache@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Correct way to remove a cache device?

I couldn't figure out a predictable way to detach it properly. Even
when doing it as early as possible in the boot sequence, it'd succeed
anywhere from the first time I tried to seven reboots later.

I actually ended up doing something very nasty, but very efficient: I
simply dd zeroes to the beginning of the cache device, then reboot,
and the kernel would no longer recognize the cache device, and I could
continue normally.

Not pretty by any standard (actually makes me feel like showering),
but it works ;)
--
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