public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Brad Boyer <flar@pants.nu>, Roman Zippel <zippel@linux-m68k.org>,
	linux-hfsplus-devel@lists.sourceforge.net,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] HFS+ driver
Date: Mon, 12 May 2003 11:58:59 +0200	[thread overview]
Message-ID: <jeissglc4c.fsf@sykes.suse.de> (raw)
In-Reply-To: <20030508221202.GE3458@werewolf.able.es> (J. A. Magallon's message of "Fri, 9 May 2003 00:12:02 +0200")

"J.A. Magallon" <jamagallon@able.es> writes:

|> Modified version, including the hfsplus dir and the 64 bit changes, is at
|> http://giga.cps.unizar.es/~magallon/linux/hfsplus-20030507-2.bz2

There is a warning in btree.c:hfsplus_btree_alloc_node.  Does this make
sense?

--- btree.c.~1~	2003-05-12 11:53:42.000000000 +0200
+++ btree.c	2003-05-12 11:53:51.000000000 +0200
@@ -204,7 +204,7 @@ hfsplus_bnode *hfsplus_btree_alloc_node(
 					}
 				}
 			}
-			if (++off >= PAGE_CACHE_MASK) {
+			if (++off >= PAGE_CACHE_SIZE) {
 				hfsplus_kunmap(*pagep++);
 				data = hfsplus_kmap(*pagep);
 				off = 0;

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2003-05-12  9:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-07 15:06 [ANNOUNCE] HFS+ driver Roman Zippel
2003-05-07 15:40 ` David S. Miller
2003-05-07 16:14 ` Daniele Pala
2003-05-07 19:39 ` Brad Boyer
2003-05-07 23:53   ` Roman Zippel
2003-05-08 21:34 ` J.A. Magallon
2003-05-08 21:47   ` Brad Boyer
2003-05-08 22:12     ` J.A. Magallon
2003-05-12  9:58       ` Andreas Schwab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-07 15:55 Jeffrey Baker
2003-05-07 16:38 ` Miles Lane

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=jeissglc4c.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=flar@pants.nu \
    --cc=jamagallon@able.es \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-hfsplus-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zippel@linux-m68k.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