linux-kernel - Re: Kernel 2.6.30.4 loop(..?) regression (& with/2.6.31-rc6)

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090828165526.GA6133@infradead.org>
Date:	Fri, 28 Aug 2009 12:55:26 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Justin Piszcz <jpiszcz@...idpixels.com>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Nikanth Karthikesan <knikanth@...e.de>, xfs@....sgi.com,
	linux-kernel@...r.kernel.org, Jens Axboe <jens.axboe@...cle.com>
Subject: Re: Kernel 2.6.30.4 loop(..?) regression (& with/2.6.31-rc6)

On Fri, Aug 28, 2009 at 07:23:11AM -0400, Justin Piszcz wrote:
> If both '-o nobarrier' and the patch solves the issue, what is the next  
> action that should be taken?  Update the documentation to always use
> -o nobarrier for cryptoloop? Or get the patch reverted in mainline?

We'll have to figure out why it causes those problems and how fix them.
-o nobarrier on a loop device is extremly unsafe as you will possible
lose large amounts of log updates in case of a crash.

--
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/