public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: gagneraud christian <cgagneraud@anfora.fr>
To: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 cannot even initialize
Date: 21 Jun 2002 10:20:01 +0200	[thread overview]
Message-ID: <1024647631.25826.7.camel@christian> (raw)
In-Reply-To: <20020620195253.B13478@wohnheim.fh-wedel.de>

Le jeu 20/06/2002 à 19:52, Jörn Engel a écrit :
> On Thu, 20 June 2002 19:16:43 +0200, gagneraud christian wrote:
> > Le jeu 20/06/2002 à 18:46, Jörn Engel a écrit :
> > > After merging current JFFS2 with our kernel again, I tripped over the
> > > first sanity check in super-v24.c. Here is the dmesg:
> > > JFFS2 error: struct jffs2_sb_info (376 bytes) doesn't fit in the super_block union (272 bytes)
> > > 
> > > Is this a known issue? What do I do?
> > > 
> > > Jörn
> > i use JFFS2 CVS code on a 2.4.4linux and i've had to modify
> > include/linux/fs.h:
> > ----8<-------8<-------8<-------8<-------8<-------8<-------8<-------8<---
> diff -Naur linux-2.4.4-2002-03-21/include/linux/fs.h
> linux-denx-2.4.4-20020321-edu/include/linux/fs.h
> --- linux-2.4.4-2002-03-21/include/linux/fs.h   Mon Apr 30 01:15:31 2001
> +++ linux-denx-2.4.4-20020321-edu/include/linux/fs.h    Thu Apr 25
> 19:12:28 2002
> @@ -296,6 +296,7 @@
>  #include <linux/ncp_fs_i.h>
>  #include <linux/proc_fs_i.h>
>  #include <linux/usbdev_fs_i.h>
> +#include <linux/jffs2_fs_i.h>
> 
>  /*
>   * Attribute flags.  These should be or-ed together to figure out what
> @@ -461,6 +462,7 @@
>                 struct proc_inode_info          proc_i;
>                 struct socket                   socket_i;
>                 struct usbdev_inode_info        usbdev_i;
> +               struct jffs2_inode_info         jffs2_i;
>                 void                            *generic_ip;
>  
>  extern struct list_head super_blocks;
>  
> @@ -689,6 +692,7 @@
>                 struct udf_sb_info      udf_sb;
>                 struct ncp_sb_info      ncpfs_sb;
>                 struct usbdev_sb_info   usbdevfs_sb;
> +               struct jffs2_sb_info    jffs2_sb;
>                 void                    *generic_sbp;
>         } u;
>         /*
> > ----8<-------8<-------8<-------8<-------8<-------8<-------8<-------8<---
> > 
> > hope this help.
> 
> It sure did. Thanks a lot!
> 
> Jörn
> 
> -- 
> Perfection (in design) is achieved not when there is nothing more to
> add, but rather when there is nothing more to take away.
> -- Eric Raymond in "The cathedral and the bazaar"
> 
-- 
/**********************************************
* Christian Gagneraud
***********************************************
* cgagneraud@anfora.fr
***********************************************
* ANFORA
* bat Actys, Voie3
* 31313 Labège Innopole
* FRANCE
***********************************************/

      parent reply	other threads:[~2002-06-21  8:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-20 16:46 JFFS2 cannot even initialize Jörn Engel
2002-06-20 18:00 ` David Woodhouse
     [not found] ` <1024593433.25822.4.camel@christian>
     [not found]   ` <20020620195253.B13478@wohnheim.fh-wedel.de>
2002-06-21  8:20     ` gagneraud christian [this message]

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=1024647631.25826.7.camel@christian \
    --to=cgagneraud@anfora.fr \
    --cc=linux-mtd@lists.infradead.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