linux-kernel - Re: [PATCH 0/3] Bcache: version 4

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: <4BDC764F.7040606@gmail.com>
Date:	Sat, 01 May 2010 10:43:27 -0800
From:	Kent Overstreet <kent.overstreet@...il.com>
To:	Valdis.Kletnieks@...edu
CC:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] Bcache: version 4

On 05/01/2010 05:01 AM, Valdis.Kletnieks@...edu wrote:
> On Fri, 30 Apr 2010 16:12:13 -0800, Kent Overstreet said:
>
>> Most of the basic functionality is now there; the most visible thing is
>> it's now correctly saving all the metadata, so you can unload a cache
>> and then reload it, and everything will still be there.
>
> If you unload a cache and then reload it, what prevents it from serving
> up now-stale data from an extent that was modified while the cache was
> unloaded?
>
> (Telling me "Get some caffeine, it's about halfway down in patch 2" or
> "We'll add that in Version 6 of the patch" are both acceptable answers" :)

The plan is check if any devices are open read write on cache load and 
unload, and invalidate their cached data if so. Not implemented yet, though.
--
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/