summaryrefslogtreecommitdiffstats
path: root/fs/ufs
diff options
context:
space:
mode:
authorAl Viro <viro@zeniv.linux.org.uk>2015-06-04 14:13:14 -0400
committerAl Viro <viro@zeniv.linux.org.uk>2015-07-06 17:39:31 -0400
commit4e3911f3d704d681477cdb4e1a2bfd52d5e42d23 (patch)
tree32bcdd81662bdbde65aed187a917a84ff7d8902f /fs/ufs
parent010d331fc315c96607aa6ecdfebb9fcdd349fc9b (diff)
downloadop-kernel-dev-4e3911f3d704d681477cdb4e1a2bfd52d5e42d23.zip
op-kernel-dev-4e3911f3d704d681477cdb4e1a2bfd52d5e42d23.tar.gz
ufs: the offsets ufs_block_to_path() puts into array are not sector_t
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>
Diffstat (limited to 'fs/ufs')
-rw-r--r--fs/ufs/inode.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/fs/ufs/inode.c b/fs/ufs/inode.c
index ec758ed..4367218 100644
--- a/fs/ufs/inode.c
+++ b/fs/ufs/inode.c
@@ -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));
OpenPOWER on IntegriCloud