From: Hans Reiser <reiser@namesys.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [[BK][PATCH] 2.5 trivial reiserfs resizer patch (needed now that
Date: Fri, 14 Feb 2003 21:16:28 +0300 [thread overview]
Message-ID: <3E4D327C.6050007@namesys.com> (raw)
mark_buffer_dirty requires buffer to be uptodate already)
Content-Type: multipart/mixed;
boundary="------------050908040703060205000401"
This is a multi-part message in MIME format.
--------------050908040703060205000401
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
--
Hans
--------------050908040703060205000401
Content-Type: message/rfc822;
name="Trivial resizer fix for 2.5, please forward to Linus."
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="Trivial resizer fix for 2.5, please forward to Linus."
Return-Path: <green@namesys.com>
Delivered-To: reiser@namesys.com
Received: (qmail 5381 invoked from network); 14 Feb 2003 08:46:38 -0000
Received: from angband.namesys.com (postfix@212.16.7.85)
by thebsh.namesys.com with SMTP; 14 Feb 2003 08:46:38 -0000
Received: by angband.namesys.com (Postfix on SuSE Linux 7.3 (i386), from userid 521)
id 92208452F0A; Fri, 14 Feb 2003 11:46:36 +0300 (MSK)
Date: Fri, 14 Feb 2003 11:46:36 +0300
From: Oleg Drokin <green@namesys.com>
To: reiser@namesys.com
Subject: Trivial resizer fix for 2.5, please forward to Linus.
Message-ID: <20030214114636.F10351@namesys.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.22.1i
Hello!
This trivial changeset fixes reiserfs resizer crash now that
mark_buffer_dirty requires buffer to be uptodate already.
Noticed by Alex Tomas <bzzz@tmi.comex.ru>
Please pull from bk://namesys.com/bk/reiser3-linux-2.5-resizer-fix
Diffstat:
resize.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.1060 -> 1.1061
# fs/reiserfs/resize.c 1.11 -> 1.12
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 03/02/14 green@angband.namesys.com 1.1061
# reiserfs: Move mark_buffer_uptodate in front of mark_buffer_dirty in resizer.
# This is needed because mark_buffer_dirty is now checking if buffer is up to date.
# Noticed by Alex Tomas <bzzz@tmi.comex.ru>
# --------------------------------------------
#
diff -Nru a/fs/reiserfs/resize.c b/fs/reiserfs/resize.c
--- a/fs/reiserfs/resize.c Fri Feb 14 11:39:28 2003
+++ b/fs/reiserfs/resize.c Fri Feb 14 11:39:28 2003
@@ -118,8 +118,8 @@
memset(bitmap[i].bh->b_data, 0, sb_blocksize(sb));
reiserfs_test_and_set_le_bit(0, bitmap[i].bh->b_data);
- mark_buffer_dirty(bitmap[i].bh) ;
set_buffer_uptodate(bitmap[i].bh);
+ mark_buffer_dirty(bitmap[i].bh) ;
sync_dirty_buffer(bitmap[i].bh);
// update bitmap_info stuff
bitmap[i].first_zero_hint=1;
--------------050908040703060205000401--
reply other threads:[~2003-02-14 18:07 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=3E4D327C.6050007@namesys.com \
--to=reiser@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