linux-kernel - Re: question regarding the Linux block device cache

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]

Date:	Fri, 9 Mar 2007 18:58:55 -0500
From:	"Xin Zhao" <uszhaoxin@...il.com>
To:	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: question regarding the Linux block device cache

I read the code and found that a block buffer is not necessarily freed
even if the corresponding inode is released. Looks like block buffer
can stay around as long as the system still has free memory. Is my
understanding correct?

-x

On 3/9/07, Xin Zhao <uszhaoxin@...il.com> wrote:
> Hi,
>
> I am working on a file system that allow multiple files to share data
> blocks. That is, a data block can be shared by two or more files. Now
> my question is: suppose file A and B share the same data block D. Now
> a process open file A and read block D, then this process closes file
> A. If another process open file B and read block D right after the
> first process closes A, is the data of block D read from some cache or
> has to be loaded from disk again? I think this has to do with the
> Linux block device buffer cache. But I am not quite familiar with this
> part.
>
> Can someone help me or direct me to the right place to find the answer?
>
> Thanks in advance!
>
> -x
>
-
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/