From: FabF <fabian.frederick@skynet.be>
To: linus@osdl.org
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: [PATCH 2.6.7-rc1] ext2 debugger broken
Date: Mon, 24 May 2004 20:30:55 +0200 [thread overview]
Message-ID: <1085423455.5746.5.camel@localhost.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 98 bytes --]
Linus,
This fixes ext2 debugger.It seems percpu_counter_read stamp moved
lately.
Regards,
FabF
[-- Attachment #2: ext2dbg1.diff --]
[-- Type: text/x-patch, Size: 802 bytes --]
diff -Naur orig/fs/ext2/ialloc.c edited/fs/ext2/ialloc.c
--- orig/fs/ext2/ialloc.c 2004-05-10 04:32:37.000000000 +0200
+++ edited/fs/ext2/ialloc.c 2004-05-24 20:09:33.000000000 +0200
@@ -663,7 +663,7 @@
}
brelse(bitmap_bh);
printk("ext2_count_free_inodes: stored = %lu, computed = %lu, %lu\n",
- percpu_counter_read(EXT2_SB(sb)->s_freeinodes_counter),
+ percpu_counter_read(&EXT2_SB(sb)->s_freeinodes_counter),
desc_count, bitmap_count);
unlock_super(sb);
return desc_count;
@@ -724,7 +724,7 @@
bitmap_count += x;
}
brelse(bitmap_bh);
- if (percpu_counter_read(EXT2_SB(sb)->s_freeinodes_counter) !=
+ if (percpu_counter_read(&EXT2_SB(sb)->s_freeinodes_counter) !=
bitmap_count)
ext2_error(sb, "ext2_check_inodes_bitmap",
"Wrong free inodes count in super block, "
reply other threads:[~2004-05-24 19:02 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=1085423455.5746.5.camel@localhost.localdomain \
--to=fabian.frederick@skynet.be \
--cc=linus@osdl.org \
--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