All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@sun.com>
To: "Theodore Ts'o" <tytso@MIT.EDU>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH, E2FSPROGS] blkid: Automatically chose between ext4 and ext4dev as appropriate
Date: Mon, 11 Feb 2008 16:46:43 -0700	[thread overview]
Message-ID: <20080211234643.GL3029@webber.adilger.int> (raw)
In-Reply-To: <E1JNboG-0000IP-8D@closure.thunk.org>

On Feb 08, 2008  17:35 -0500, Theodore Ts'o wrote:
> I plan to release this in an upcoming 1.40.6 release, along with code
> that allows "tune2fs -E test_fs" to work on ext4 filesystems.  The idea
> is that if I can get this into community distro's, it will make it
> easier for them to experiment with ext4/ext4dev, with the appropriate
> forward compatibility when sometime (hopefully 2.6.26 or 2.6.27?) we
> rename ext4dev to ext4.
> 
> Any comments before I push this change out to the maint branch?
> 
> 						- Ted
> 
> 
> @@ -158,6 +159,109 @@ static void get_ext2_info(blkid_dev dev, struct blkid_magic *id,
>  		blkid_set_tag(dev, "SEC_TYPE", "ext2", sizeof("ext2"));
>  }
>  
> +/*
> + * Check to see if a filesystem is in /proc/filesystems.
> + * Returns 1 if found, 0 if not
> + */
> +int fs_proc_check(const char *fs_name)
> +{
> +}

Sure.

> +int check_for_modules(const char *fs_name)
> +{
> +}

This part is quite fragile IMHO.  Why not blindly do an attempt to load
this module via the equivalent of system("modprobe %s", fs_name) and then
call fs_proc_check() to see if it is available?  That removes all of the
kernel/module knowlege/complexity from blkid.

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

      parent reply	other threads:[~2008-02-11 23:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-08 22:35 [PATCH, E2FSPROGS] blkid: Automatically chose between ext4 and ext4dev as appropriate Theodore Ts'o
2008-02-08 22:50 ` Eric Sandeen
2008-02-08 23:20   ` Theodore Tso
2008-02-11 23:46 ` 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=20080211234643.GL3029@webber.adilger.int \
    --to=adilger@sun.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@MIT.EDU \
    /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.