kernel.git/fs/nilfs2/dat.c, branch linux-2.6.34.y

nilfs2: fix various typos in comments

2010-03-14T01:29:51Z

This fixes various typos I found in comments of nilfs2. Signed-off-by: Ryusuke Konishi

nilfs2: delete unnecessary condition in nilfs_dat_translate

2010-02-13T03:26:03Z

This is a trivial patch to delete unnecessary condition in nilfs_dat_translate. nilfs_dat_translate() will asign translated address to *blocknrp if blocknrp is not NULL. However the condition is unneeded, because all callers of nilfs_dat_translate() pass blocknrp properly. Signed-off-by: Jiro SEKIBA Signed-off-by: Ryusuke Konishi

nilfs2: add palloc cache to dat

2009-11-20T01:05:50Z

This adds the palloc cache to DAT file. The palloc cache is allocated on the extended region of nilfs_mdt_info struct. The struct nilfs_dat_info defines the extended on memory structure of DAT. Signed-off-by: Ryusuke Konishi

nilfs2: separate read method of meta data files on super root block

2009-11-20T01:05:48Z

Will displace nilfs_mdt_read_inode_direct function with an individual read method: nilfs_dat_read, nilfs_sufile_read, nilfs_cpfile_read. This provides the opportunity to initialize local variables of each metadata file after reading the inode. Signed-off-by: Ryusuke Konishi

nilfs2: separate constructor of metadata files

2009-11-20T01:05:48Z

This will displace nilfs_mdt_new() constructor with individual metadata file constructors like nilfs_dat_new(), new_sufile_new(), nilfs_cpfile_new(), and nilfs_ifile_new(). This makes it possible for each metadata file to have own intialization code. Signed-off-by: Ryusuke Konishi

nilfs2: add update functions of virtual block address to dat

2009-09-14T09:27:15Z

This is a preparation for the successive cleanup ("nilfs2: allow btree to directly call dat operations"). This adds functions bundling a few operations to change an entry of virtual block address on the dat file. Signed-off-by: Ryusuke Konishi

nilfs2: remove nilfs_dat_abort_start and nilfs_dat_abort_free

2009-09-14T09:27:15Z

These functions are not called from any functions. Signed-off-by: Ryusuke Konishi

nilfs2: fix incorrect KERN_CRIT messages in case of write failures

2009-07-05T01:44:20Z

In case of write-failure retries, the following KERN_CRIT level messages are mistakenly output by nilfs_dat_commit_start() function: nilfs_dat_commit_start: vbn = 408463, start = 12506, end = 18446744073709551615, pbn = 530210 nilfs_dat_commit_start: vbn = 408515, start = 12506, end = 18446744073709551615, pbn = 530211 nilfs_dat_commit_start: vbn = 408464, start = 12506, end = 18446744073709551615, pbn = 530212 ... This suppresses these messages. Signed-off-by: Ryusuke Konishi Cc: stable@kernel.org

nilfs2: allow future expansion of metadata read out via get info ioctl

2009-06-10T14:41:11Z

Nilfs has some ioctl commands to read out metadata from meta data files: - NILFS_IOCTL_GET_CPINFO for checkpoint file, - NILFS_IOCTL_GET_SUINFO for segment usage file, and - NILFS_IOCTL_GET_VINFO for Disk Address Transalation (DAT) file, respectively. Every routine on these metadata files is implemented so that it allows future expansion of on-disk format. But, the above ioctl commands do not support expansion even though nilfs_argv structure can handle arbitrary size for data exchanged via ioctl. This allows future expansion of the following structures which give basic format of the "get information" ioctls: - struct nilfs_cpinfo - struct nilfs_suinfo - struct nilfs_vinfo So, this introduces forward compatility of such ioctl commands. In this patch, a sanity check in nilfs_ioctl_get_info() function is changed to accept larger data structure [1], and metadata read routines are rewritten so that they become compatible for larger structures; the routines will just ignore the remaining fields which the current version of nilfs doesn't know. [1] The ioctl function already has another upper limit (PAGE_SIZE against a structure, which appears in nilfs_ioctl_wrap_copy function), and this will not cause security problem. Signed-off-by: Ryusuke Konishi

nilfs2: remove nilfs_dat_prepare_free function

2009-06-10T14:41:09Z

This function is unused. Signed-off-by: Ryusuke Konishi