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
| ||
|
Date: Wed, 26 Jan 2022 08:51:35 +0000 From: David Howells <dhowells@...hat.com> To: JeffleXu <jefflexu@...ux.alibaba.com> Cc: dhowells@...hat.com, linux-cachefs@...hat.com, xiang@...nel.org, chao@...nel.org, linux-erofs@...ts.ozlabs.org, linux-fsdevel@...r.kernel.org, joseph.qi@...ux.alibaba.com, bo.liu@...ux.alibaba.com, tao.peng@...ux.alibaba.com, gerry@...ux.alibaba.com, eguan@...ux.alibaba.com, linux-kernel@...r.kernel.org Subject: Re: [PATCH v2 00/20] fscache,erofs: fscache-based demand-read semantics JeffleXu <jefflexu@...ux.alibaba.com> wrote: > "/path/to/file+offset" > ^ > > Besides, what does the 'offset' mean? Assuming you're storing multiple erofs files within the same backend file, you need to tell the the cache backend how to find the data. Assuming the erofs data is arranged such that each erofs file is a single contiguous region, then you need a pathname and a file offset to find one of them. David
Powered by blists - more mailing lists