public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [BK][2.4] reiserfs: Enable tail packing, resend
Date: Mon, 12 May 2003 23:34:25 +0400	[thread overview]
Message-ID: <3EBFF741.3070505@namesys.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 11 bytes --]


-- 
Hans


[-- Attachment #2: [2.4] reiserfs: Enable tail packing, resend --]
[-- Type: message/rfc822, Size: 2308 bytes --]

From: Oleg Drokin <green@namesys.com>
To: reiser@namesys.com
Subject: [2.4] reiserfs: Enable tail packing, resend
Date: Mon, 12 May 2003 18:02:32 +0400
Message-ID: <20030512140232.GD4165@namesys.com>

Hello!

    This patch restores the tail packing fucntionality that was
    mistakenly disabled by previously accepted directio fix patch.

    Please pull from bk://namesys.com/bk/reiser3-linux-2.4-tailfix

Diffstat:
 inode.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

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.1158  -> 1.1159 
#	 fs/reiserfs/inode.c	1.42    -> 1.43   
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 03/05/03	green@angband.namesys.com	1.1159
# reiserfs: One of the O_DIRECT fixes disabled tail packing by mistake. Enable it again.
# --------------------------------------------
#
diff -Nru a/fs/reiserfs/inode.c b/fs/reiserfs/inode.c
--- a/fs/reiserfs/inode.c	Mon May 12 17:47:44 2003
+++ b/fs/reiserfs/inode.c	Mon May 12 17:47:44 2003
@@ -2085,8 +2085,8 @@
 	/* If the file have grown beyond the border where it
 	   can have a tail, unmark it as needing a tail
 	   packing */
-	if ( (have_large_tails (inode->i_sb) && inode->i_size < block_size (inode)*4) ||
-	     (have_small_tails (inode->i_sb) && inode->i_size < block_size(inode)) )
+	if ( (have_large_tails (inode->i_sb) && inode->i_size > block_size (inode)*4) ||
+	     (have_small_tails (inode->i_sb) && inode->i_size > block_size(inode)) )
 	    inode->u.reiserfs_i.i_flags &= ~i_pack_on_close_mask;
 
 	journal_begin(&th, inode->i_sb, 1) ;



                 reply	other threads:[~2003-05-12 19:21 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=3EBFF741.3070505@namesys.com \
    --to=reiser@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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