From: Mark Nipper <nipsy@bitgnome.net>
To: linux-kernel@vger.kernel.org
Subject: lost patch for fs/reiserfs/fix_node.c
Date: Fri, 7 Jan 2005 13:29:34 -0600 [thread overview]
Message-ID: <20050107192934.GA42646@king.bitgnome.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
Any reason the attached patch from Oleg Drokin never made
it even in 2.6.10 now? I see the supposedly harmless errors this
patch is meant to correct and it seems like an oversight it never
made it into the tree.
--
Mark Nipper e-contacts:
4475 Carter Creek Parkway nipsy@bitgnome.net
Apartment 724 http://nipsy.bitgnome.net/
Bryan, Texas, 77802-4481 AIM/Yahoo: texasnipsy ICQ: 66971617
(979)575-3193 MSN: nipsy@tamu.edu
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GG/IT d- s++:+ a- C++$ UBL++++$ P--->+++ L+++$ !E---
W++(--) N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--)
Y+ PGP t+ 5 X R tv b+++@ DI+(++) D+ G e h r++ y+(**)
------END GEEK CODE BLOCK------
---begin random quote of the moment---
He hoped and prayed that there wasn't an afterlife. Then he
realized there was a contradiction involved here and merely
hoped that there wasn't an afterlife.
-- Douglas Adams
----end random quote of the moment----
[-- Attachment #2: indirect_item.patch --]
[-- Type: text/plain, Size: 678 bytes --]
--- linux-2.6.10/fs/reiserfs/fix_node.c.orig 2004-12-24 15:34:30.000000000 -0600
+++ linux-2.6.10/fs/reiserfs/fix_node.c 2005-01-07 13:20:43.000000000 -0600
@@ -510,9 +510,10 @@
// s2bytes
snum012[4] = op_unit_num (&vn->vn_vi[split_item_num]) - snum012[4] - bytes_to_r - bytes_to_l - bytes_to_S1new;
- if (vn->vn_vi[split_item_num].vi_index != TYPE_DIRENTRY)
+ if (vn->vn_vi[split_item_num].vi_index != TYPE_DIRENTRY &&
+ vn->vn_vi[split_item_num].vi_index != TYPE_INDIRECT)
reiserfs_warning (tb->tb_sb, "vs-8115: get_num_ver: not "
- "directory item");
+ "directory or indirect item");
}
/* now we know S2bytes, calculate S1bytes */
reply other threads:[~2005-01-07 19:39 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=20050107192934.GA42646@king.bitgnome.net \
--to=nipsy@bitgnome.net \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome