Re: Ideas to do custom operation just after mount?

All of lore.kernel.org
 help / color / mirror / Atom feed

From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Dave Chinner <david@fromorbit.com>
Cc: fstests@vger.kernel.org, btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Ideas to do custom operation just after mount?
Date: Mon, 21 Dec 2015 10:25:52 +0800	[thread overview]
Message-ID: <56776330.1090500@cn.fujitsu.com> (raw)
In-Reply-To: <20151221001654.GM19802@dastard>



Dave Chinner wrote on 2015/12/21 11:16 +1100:
> On Thu, Dec 17, 2015 at 09:55:14AM +0800, Qu Wenruo wrote:
>> Hi,
>>
>> Will xfstests provides some API to do some operation just after
>> mounting a filesystem?
>>
>> Some filesystem(OK, btrfs again) has some function(now qgroup only)
>> which needed to be enabled by ioctl instead of mount option.
>
> Irk.
>
> Seriously, I need ot find some time to split all the fs specific
> stuff in common/rc into separate files and have each different
> filesystem implement it's own version of the relevant functions
> like _scratch_mkfs, _scratch_mount, etc.
>
> That will enable btrfs to do truly hideous stuff like this that
> admins will hate you for requiring, and the rest of us won't have to
> care about it.
>
>> So is there any good idea to do some operation just after mounting
>> in xfstests?
>
> You're just going to have to wait a bit - the first piece of this
> is in the overlayfs support patches, and the rest of it is in my
> local work area in an incomplete state.

Glad to hear that, I'll just wait for the formal implement.

Thanks,
Qu

>
> Cheers,
>
> Dave.
>

WARNING: multiple messages have this Message-ID (diff)

From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Dave Chinner <david@fromorbit.com>
Cc: <fstests@vger.kernel.org>, btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Ideas to do custom operation just after mount?
Date: Mon, 21 Dec 2015 10:25:52 +0800	[thread overview]
Message-ID: <56776330.1090500@cn.fujitsu.com> (raw)
In-Reply-To: <20151221001654.GM19802@dastard>



Dave Chinner wrote on 2015/12/21 11:16 +1100:
> On Thu, Dec 17, 2015 at 09:55:14AM +0800, Qu Wenruo wrote:
>> Hi,
>>
>> Will xfstests provides some API to do some operation just after
>> mounting a filesystem?
>>
>> Some filesystem(OK, btrfs again) has some function(now qgroup only)
>> which needed to be enabled by ioctl instead of mount option.
>
> Irk.
>
> Seriously, I need ot find some time to split all the fs specific
> stuff in common/rc into separate files and have each different
> filesystem implement it's own version of the relevant functions
> like _scratch_mkfs, _scratch_mount, etc.
>
> That will enable btrfs to do truly hideous stuff like this that
> admins will hate you for requiring, and the rest of us won't have to
> care about it.
>
>> So is there any good idea to do some operation just after mounting
>> in xfstests?
>
> You're just going to have to wait a bit - the first piece of this
> is in the overlayfs support patches, and the rest of it is in my
> local work area in an incomplete state.

Glad to hear that, I'll just wait for the formal implement.

Thanks,
Qu

>
> Cheers,
>
> Dave.
>

next prev parent reply	other threads:[~2015-12-21  2:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17  1:55 Ideas to do custom operation just after mount? Qu Wenruo
2015-12-17  1:55 ` Qu Wenruo
2015-12-21  0:16 ` Dave Chinner
2015-12-21  2:25   ` Qu Wenruo [this message]
2015-12-21  2:25     ` Qu Wenruo
2015-12-21  2:38     ` Qu Wenruo
2015-12-21  2:38       ` Qu Wenruo
2015-12-21  5:18       ` Anand Jain
2015-12-22  0:14         ` Kai Krakow
2015-12-22  0:14           ` Kai Krakow
2015-12-22  9:28           ` Duncan
2015-12-23 23:17         ` Dave Chinner

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=56776330.1090500@cn.fujitsu.com \
    --to=quwenruo@cn.fujitsu.com \
    --cc=david@fromorbit.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@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.