linux-ext4 - Re: Buffer state bits

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]

Date:	Thu, 27 Aug 2009 18:03:18 +0530
From:	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
To:	Jan Kara <jack@...e.cz>
Cc:	linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Buffer state bits

> 
> BH_Mapped
> - Buffer has a physical block backing it stored in b_bdev + b_blocknr. This bit
>   is set by filesystem's get_block() function (or by VFS itself for block device
>   mappings).
> 
>   XXX: Some filesystems set BH_Mapped even for buffers that do no really
>   have the backing block (like buffers for delayed allocation). I think
>   we should get rid of it...
> 

Also we don't want get_block to be called multiple times for the same file offset.
__block_prepare_write does get_block looking at the BH_Mapped flag. ie one of reason
delay and unwritten buffer_heads are also marked mapped.


-aneesh
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html