From: reiser@reload.namesys.com (Hans Reiser)
To: green@namesys.com, linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: [BK] PATCH ReiserFS 2 of 3 RESEND
Date: Mon, 9 Sep 2002 15:31:47 +0400 (MSD) [thread overview]
Message-ID: <20020909113147.C5983A7CE2@reload.namesys.com> (raw)
Hello!
This changeset corrects logic in reiserfs code that calculates amount
of blocks file will take. Please apply.
You can get it from bk://thebsh.namesys.com/reiser3-linux-2.5
Diffstat:
inode.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
Plain text patch:
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet 1.500 -> 1.501
# fs/reiserfs/inode.c 1.63 -> 1.64
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 02/08/20 green@angband.namesys.com 1.501
# Corrected calculation of amount of blocks that file occupies on reiserfs.
# --------------------------------------------
#
diff -Nru a/fs/reiserfs/inode.c b/fs/reiserfs/inode.c
--- a/fs/reiserfs/inode.c Tue Aug 20 13:58:51 2002
+++ b/fs/reiserfs/inode.c Tue Aug 20 13:58:51 2002
@@ -919,7 +919,7 @@
inode->i_blocks = sd_v1_blocks(sd);
inode->i_generation = le32_to_cpu (INODE_PKEY (inode)->k_dir_id);
blocks = (inode->i_size + 511) >> 9;
- blocks = _ROUND_UP (blocks, inode->i_blksize >> 9);
+ blocks = _ROUND_UP (blocks, inode->i_sb->s_blocksize >> 9);
if (inode->i_blocks > blocks) {
// there was a bug in <=3.5.23 when i_blocks could take negative
// values. Starting from 3.5.17 this value could even be stored in
reply other threads:[~2002-09-09 11:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020909113147.C5983A7CE2@reload.namesys.com \
--to=reiser@reload.namesys.com \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).