From: Andreas Dilger <adilger@turbolinux.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: super_operations in -pre7
Date: Tue, 16 Jan 2001 15:59:37 -0700 (MST) [thread overview]
Message-ID: <200101162259.f0GMxcN01740@webber.adilger.net> (raw)
In-Reply-To: <20010116221357.H20275@parcelfarce.linux.theplanet.co.uk> "from Matthew Wilcox at Jan 16, 2001 10:13:57 pm"
Mattew Wilcox writes:
> several new operations have been added to super_operations, presumably
> as part of the reiserfs merge. write_super_lockfs and unlockfs are
> never called. can we remove them?
These operations were added to co-ordinate filesystem backups/snapshots
for journalling filesystems (especially in conjunction with LVM). At
some point in the future ext3 will also be using them. However, (only
having looked at preliminary patches, and not the final 2.4.1-pre reiserfs
merge) it is bad to insert them in the middle of the super_operations
struct at this point, as it breaks every filesystem that isn't part of
the kernel. That said, the addition of (reiserfs-specific) read_inode2
and dirty_inode pointers also break all non-kernel filesystems. Argh!
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
-
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/
prev parent reply other threads:[~2001-01-16 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-16 22:13 Matthew Wilcox
2001-01-16 22:59 ` Andreas Dilger [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=200101162259.f0GMxcN01740@webber.adilger.net \
--to=adilger@turbolinux.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
/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®