linux-ext4 - a question about ext4_fsblk

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>] [day] [month] [year] [list]

Message-Id: <200610220746.k9M7kRHv012761@nrchpc.ac.cn>
Date:	Sun, 22 Oct 2006 15:38:00 +0800
From:	"郭明阳" <guomingyang@...hpc.ac.cn>
To:	"linux-ext4" <linux-ext4@...r.kernel.org>,
	"linux-ext4" <linux-ext4@...r.kernel.org>,
	"linux-ext4" <linux-ext4@...r.kernel.org>,
	"linux-ext4" <linux-ext4@...r.kernel.org>,
	"linux-ext4" <linux-ext4@...r.kernel.org>,
	"linux-ext4" <linux-ext4@...r.kernel.org>,
	"linux-ext4" <linux-ext4@...r.kernel.org>
Cc:	"linux-fsdevel" <linux-fsdevel@...r.kernel.org>
Subject: a question about ext4_fsblk_t

Hello everyone:

		I am a student interesting in linux filesystem, I have a problem about the replace of block number type to ext4_fsblk_t. Is it complete? Or has it passed all the test? Because I have found a place like this in linux-2.6.19-rc2/fs/ext4/inode.c 



+struct buffer_head *ext4_bread(handle_t *handle, struct inode *inode,
+                               int block, int create, int *err)


the block's type is not changed. Although I think it will bring no mistake, I doubt about why not change it. Thank you !


guomingyang

-
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