public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Avantika Mathur <mathur@linux.vnet.ibm.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: Girish Shilamkar <girish@clusterfs.com>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] uninitialized groups ported - kernel
Date: Thu, 21 Jun 2007 16:54:14 -0700	[thread overview]
Message-ID: <467B0FA6.1090509@linux.vnet.ibm.com> (raw)
In-Reply-To: <20070621173757.GA1075@schatzie.adilger.int>

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

Kernel build was failing with the uninitialized patches when 
CONFIG_CRC16=m. The patch below resolves this issue.

Also, when testing the patches, filesystem mount fails:

EXT4-fs error (device sdc1): ext4_check_descriptors: Checksum for group 1 failed (0!=1)

EXT4-fs: group descriptors corrupted!

EXT4-fs error (device sdc1): ext4_check_descriptors: Checksum for group 7 failed (0!=1)

Even though the uninitgrps feature is not enabled, the gdp->bg_checksum 
on disk is nonzero.
Mingming will pull the patches out of the patch queue until this is fixed.

Thanks
Avantika
---


[-- Attachment #2: uninit-fix.patch --]
[-- Type: text/x-patch, Size: 1013 bytes --]

diff -uprN linux-2.6.22-rc5/fs/ext4/group.h linux-2.6.22-rc5-patch/fs/ext4/group.h
--- linux-2.6.22-rc5/fs/ext4/group.h	2007-06-21 16:32:52.000000000 -0700
+++ linux-2.6.22-rc5-patch/fs/ext4/group.h	2007-06-21 16:30:33.000000000 -0700
@@ -8,7 +8,7 @@
 
 #ifndef _LINUX_EXT4_GROUP_H
 #define _LINUX_EXT4_GROUP_H
-#if defined(CONFIG_CRC16) || defined(CONFIG_CRC16_MODULE)
+#if defined(CONFIG_CRC16)
 #include <linux/crc16.h>
 #endif
 
diff -uprN linux-2.6.22-rc5/fs/ext4/super.c linux-2.6.22-rc5-patch/fs/ext4/super.c
--- linux-2.6.22-rc5/fs/ext4/super.c	2007-06-21 16:32:53.000000000 -0700
+++ linux-2.6.22-rc5-patch/fs/ext4/super.c	2007-06-21 16:30:22.000000000 -0700
@@ -1232,7 +1232,7 @@ static int ext4_setup_super(struct super
 	return res;
 }
 
-#if !defined(CONFIG_CRC16) && !defined(CONFIG_CRC16_MODULE)
+#if !defined(CONFIG_CRC16)
 /** CRC table for the CRC-16. The poly is 0x8005 (x16 + x15 + x2 + 1) */
 __u16 const crc16_table[256] = {
 	0x0000, 0xC0C1, 0xC181, 0x0140, 0xC301, 0x03C0, 0x0280, 0xC241,

  reply	other threads:[~2007-06-21 23:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-05 17:48 [PATCH] uninitialized groups ported - kernel Avantika Mathur
2007-06-05 18:48 ` Eric Sandeen
2007-06-05 21:20   ` Andreas Dilger
2007-06-19  4:04     ` Avantika Mathur
2007-06-19  7:50       ` Andreas Dilger
2007-06-20 11:56         ` Girish Shilamkar
2007-06-21 17:37           ` Andreas Dilger
2007-06-21 23:54             ` Avantika Mathur [this message]
2007-06-22 16:04               ` Andreas Dilger
2007-06-22 16:20               ` Dave Kleikamp

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=467B0FA6.1090509@linux.vnet.ibm.com \
    --to=mathur@linux.vnet.ibm.com \
    --cc=adilger@clusterfs.com \
    --cc=girish@clusterfs.com \
    --cc=linux-ext4@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