All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: Matthew Wilcox <willy@debian.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Whatever happened to write_super_lockfs?
Date: Fri, 18 Jul 2003 14:06:51 -0700	[thread overview]
Message-ID: <20030718140651.K21579@schatzie.adilger.int> (raw)
In-Reply-To: <20030718203916.GX23808@parcelfarce.linux.theplanet.co.uk>; from willy@debian.org on Fri, Jul 18, 2003 at 09:39:16PM +0100

On Jul 18, 2003  21:39 +0100, Matthew Wilcox wrote:
> $ find -type f |xargs grep write_super_lockfs
> ./fs/ext3/super.c:      .write_super_lockfs = ext3_write_super_lockfs,
> ./fs/ext3/super.c:void ext3_write_super_lockfs(struct super_block *sb)
> ./fs/jfs/super.c:static void jfs_write_super_lockfs(struct super_block *sb)
> ./fs/jfs/super.c:       .write_super_lockfs = jfs_write_super_lockfs,
> ./fs/ntfs/super.c:      //write_super_lockfs    = NULL,   /* ? */
> ./fs/reiserfs/super.c:static void reiserfs_write_super_lockfs (struct super_block * s)
> ./fs/reiserfs/super.c:  .write_super_lockfs = reiserfs_write_super_lockfs,
> ./fs/xfs/linux/xfs_super.c:     .write_super_lockfs     = linvfs_freeze_fs,
> ./include/linux/ext3_fs.h:extern void ext3_write_super_lockfs (struct super_block *);
> ./include/linux/fs.h:   void (*write_super_lockfs) (struct super_block *);
> 
> Should we just delete that code now?
> 
> (Ditto unlockfs, btw:
> 
> $ find -type f |xargs grep unlockfs |grep -v ^Binary
> ./fs/ext3/super.c:      .unlockfs       = ext3_unlockfs,
> ./fs/ext3/super.c:void ext3_unlockfs(struct super_block *sb)
> ./fs/jfs/super.c:static void jfs_unlockfs(struct super_block *sb)
> ./fs/jfs/super.c:       .unlockfs       = jfs_unlockfs,
> ./fs/ntfs/super.c:      //unlockfs      = NULL,           /* ? */
> ./fs/reiserfs/super.c:void reiserfs_unlockfs(struct super_block *s) {
> ./fs/reiserfs/super.c:  .unlockfs = reiserfs_unlockfs,
> ./fs/xfs/linux/xfs_super.c:     .unlockfs               = linvfs_unfreeze_fs,
> ./include/linux/ext3_fs.h:extern void ext3_unlockfs (struct super_block *);
> ./include/linux/fs.h:   void (*unlockfs) (struct super_block *);
> )

No.  I've been trying to get Chris Mason to submit the (very small) code
into the kernel for a long time now.  It is needed for LVM and EVMS snapshots.
The inclusion is being slowed down by the lack of Viro.

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/


  reply	other threads:[~2003-07-18 20:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-18 20:39 Whatever happened to write_super_lockfs? Matthew Wilcox
2003-07-18 21:06 ` Andreas Dilger [this message]
2003-07-18 21:09   ` Matthew Wilcox
2003-07-18 21:28     ` Andreas Dilger

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=20030718140651.K21579@schatzie.adilger.int \
    --to=adilger@clusterfs.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=willy@debian.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.