All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schuldei <andreas@schuldei.org>
To: unlisted-recipients:; (no To-header on input)@pop.zip.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext2's inode i_version gone, what now? (stable branch)
Date: Sat, 30 Dec 2000 12:54:17 +0100	[thread overview]
Message-ID: <20001230125417.B29582@sigrid.schuldei.com> (raw)
In-Reply-To: <20001229220820.C28926@sigrid.schuldei.com>
In-Reply-To: <20001229220820.C28926@sigrid.schuldei.com>; from andreas@schuldei.org on Fri, Dec 29, 2000 at 10:08:20PM +0100

* Andreas Schuldei (andreas@schuldei.org) [001229 22:08]:
> However a real problem (for me) is that the author (whom I can not reach by
> email) build stegfs on top of the ext2 filesystem. There he uses ext2's inode
> structure and at some places reads/writes from ext2 inode's i_version.
> However, this is not there in ext2_fs_i.h. But I am working with source for
> 2.2.18 and a lot could have happend since 2.2.14. I would not have expected
> the inode struct to change, though.
> 
> Why was it taken away? How is compatibility maintained? What could I use 
> instead to fix the problem?

Now I think i_version was moved from ext2_fs_i.h (struct ext2_inode_info) to
fs.h (struct inode). stegfs still has i_version in it's own stegfs_inode_info.
I guess to cleanly move the stegfs from 2.2.14 to 2.2.18 it would be good to
not have a own stegfs i_version. Are there any mean, hidden, desasterous
implications waiting if I move it?

> Anyone who is interested in this:
> http://ban.joh.cam.ac.uk/~adm36/StegFS/download.html

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-30 12:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-29 21:08 ext2's inode i_version gone, what now? (stable branch) Andreas Schuldei
2000-12-30 11:54 ` Andreas Schuldei [this message]
2001-01-04 18:52   ` Stephen C. Tweedie

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=20001230125417.B29582@sigrid.schuldei.com \
    --to=andreas@schuldei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.