redonkable/remarkable-linux
redonkable/remarkable-linux
1
0
Fork 0
Code Releases Activity

ufs: the offsets ufs_block_to_path() puts into array are not sector_t

Browse source 
type makes no sense - those are indices in block number arrays, not
block numbers.  And no, UFS is not likely to grow indirect blocks with
4Gpointers in them...

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
This commit is contained in:
Al Viro 2015-06-04 14:13:14 -04:00
parent 010d331fc3
commit 4e3911f3d7
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
fs/ufs/inode.c
View file

@ -41,7 +41,7 @@
#include "swab.h"
#include "util.h"
static int ufs_block_to_path(struct inode *inode, sector_t i_block, sector_t offsets[4])
static int ufs_block_to_path(struct inode *inode, sector_t i_block, unsigned offsets[4])
{
struct ufs_sb_private_info *uspi = UFS_SB(inode->i_sb)->s_uspi;
int ptrs = uspi->s_apb;
@ -153,7 +153,7 @@ again:
while (--depth) {
__fs32 *ptr;
struct buffer_head *bh;
sector_t n = *p++;
unsigned n = *p++;
bh = sb_bread(sb, uspi->s_sbbase +
fs32_to_cpu(sb, q->key32) + (n>>shift));
@ -177,7 +177,7 @@ ufs2:
while (--depth) {
__fs64 *ptr;
struct buffer_head *bh;
sector_t n = *p++;
unsigned n = *p++;
bh = sb_bread(sb, uspi->s_sbbase +
fs64_to_cpu(sb, q->key64) + (n>>shift));