mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
To: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: 2.2.18 + VM-global + reiserfs + ext3 0.0.5e safe?
Date: Fri, 26 Jan 2001 01:02:02 +0100	[thread overview]
Message-ID: <20010126010202.C9075@emma1.emma.line.org> (raw)

Hi,

Short story:

it's again the reiserfs + ext3 issue. I managed to get ext3 and reiserfs
into the same tree. Is that safe to use without further patching?

Long story:

I have a heavily patched kernel (mostly drivers like I²C, dc390 and
stuff), among the patches are VM-global-7 by Andrea Arcangeli and
ReiserFS 3.5.28. After that, I merged ext3 0.0.5e, there were no
conflicts in buffer code or anything (so I assume my last ext3 merge
failed for VM-global-7, not for reiserfs). 

However, the old symbol clashes (buffer_journaled and release_journal)
remain. I used perl to rename these symbols to reiserfs_buffer_journaled
and reiserfs_release_journal in fs/reiserfs/*.c and
include/linux/fs_reiserfs.h, cleaned up the Makefile and *.h rejects
(only "bad context" because reiserfs was already there, and
prototypes). 

Now, is there any reason for concern the kernel might cause fs
corruption beyond the risk that EITHER reiserfs OR ext3 ONE BY ITSELF
infer?

The kernel patched like this compiles without relevant warnings and
boots up ok, copying from a ro-mounted ext2 to either reiserfs or ext3
does not cause obvious problems, but is there a potential for failure
that I can't see at the moment?

-- 
Matthias Andree
-
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:[~2001-01-26  0:33 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=20010126010202.C9075@emma1.emma.line.org \
    --to=matthias.andree@stud.uni-dortmund.de \
    --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

all inboxes | Powered by JetHome®