Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 06 Feb 2008 18:35:59 +0200
From:      Andriy Gapon <avg@icyb.net.ua>
To:        Scott Long <scottl@samsco.org>
Cc:        freebsd-hackers@FreeBSD.org, scottl@FreeBSD.org, freebsd-fs@FreeBSD.org, pav@FreeBSD.org, Julian Elischer <julian@elischer.org>, Remko Lodder <remko@FreeBSD.org>
Subject:   Re: fs/udf: vm pages "overlap" while reading  large dir [patch]
Message-ID:  <47A9E1EF.5020507@icyb.net.ua>
In-Reply-To: <47A8CA83.1000405@samsco.org>
References:  <200612221824.kBMIOhfM049471@freefall.freebsd.org>	 <47A2EDB0.8000801@icyb.net.ua> <47A2F404.7010208@icyb.net.ua>	 <47A735A4.3060506@icyb.net.ua> <47A75B47.2040604@elischer.org> <1202155663.62432.0.camel@ikaros.oook.cz> <47A8754C.5010607@icyb.net.ua> <47A8CA83.1000405@samsco.org>

next in thread | previous in thread | raw e-mail | index | archive | help
on 05/02/2008 22:43 Scott Long said the following:
> Andriy Gapon wrote:
> 
>> But there is another issue that I also mentioned in the email about
>> directory reading. It is UDF_INVALID_BMAP case of udf_bmap_internal,
>> i.e. the case when file data is embedded into a file entry.
>> This is a special case that needs to be handled differently.
>> udf_readatoffset() handles it, but the latest udf_read code doesn't.
>> I have a real UDF filesystem where this type of allocation is used for
>> small files and those files can not be read.
> 
> Oh, so directory data can also follow this convention?  Blah.  Feel free
> to fix that too if you want =-)

Yes, this allocation type can be applied to both files and directories.
Directories are already handled because of readatoffset() but udf_read
needs to be made aware of this special case.

-- 
Andriy Gapon



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47A9E1EF.5020507>