linux-ext4 - Re: Fwd: barriers off by default?

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: <72c5d9a0805121211l50e1b136xf33e0b3b7fda103c@mail.gmail.com>
Date:	Mon, 12 May 2008 13:11:51 -0600
From:	"Eric A" <erpo41@...il.com>
To:	"Eric Sandeen" <sandeen@...hat.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: Fwd: barriers off by default?

On Mon, May 12, 2008 at 1:00 PM, Eric Sandeen <sandeen@...hat.com> wrote:
> Eric A wrote:
>  >  Documentation/block/barrier.txt
>  >
>  >  There's a section that starts:
>  >
>  >  "* Error handling.  Currently, block layer will report error to upper
>  >  layer if any of requests in an ordered sequence fails.  Unfortunately,
>  >  this doesn't seem to be enough. "
>
>
>
> And ends:
>
>  "As the probability of this happening is very low and the drive should
>  be faulty, implementing the fix is probably an overkill.  But, still,
>  it's there."
>
>  I'm not sure it's an argument for disabling barriers in general.   :)

I agree; it's just something that's been bugging me since I started
searching for a solution for zfs-fuse. Maybe performance is the
reason? Flushing the write cache is kind of slow.

Cheers,
Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html