#5340: BLOCK_CACHE_DEBUG_CHANGED is too strict ---------------------------+------------------------------------------------ Reporter: romain | Owner: axeld Type: bug | Status: new Priority: normal | Milestone: R1 Component: System/Kernel | Version: R1/alpha1 Keywords: | Blockedby: Platform: All | Blocking: ---------------------------+------------------------------------------------ Comment(by axeld): Indeed, the current code is broken when used without transactions. However, your fix does not actually solve the problem, it only hides it. In fact, is_writing has to be correctly used (as much as possible). A quick idea would be to set it to true when a transaction less block is checked out, and set it to false again in put_cached_block() if the used count reaches zero. However, that would lead to a block never being written back if you cache it over the whole mount time (which is something we could simply forbid, though). -- Ticket URL: <http://dev.haiku-os.org/ticket/5340#comment:3> Haiku <http://dev.haiku-os.org> Haiku - the operating system.