All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zorro Lang <zlang@redhat.com>
To: David Disseldorp <ddiss@suse.de>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] common/rc: drop SGI DMF specific _mount_ops_filter
Date: Wed, 11 Jan 2023 17:56:09 +0800	[thread overview]
Message-ID: <20230111095609.xca2wmkgsdxaiwqt@zlang-mailbox> (raw)
In-Reply-To: <20230110222243.6522-1-ddiss@suse.de>

On Tue, Jan 10, 2023 at 11:22:43PM +0100, David Disseldorp wrote:
> The _mount() helper function is the only caller of _mount_ops_filter(),
> which appears to have been used in the past to replace the SGI DMF
> specific mtpt= mount option setting.
> 
> _mount() invocations could now be replaced with $MOUNT_PROG calls
> directly, but I've retained the helper function for readability.
> 
> Link: https://irix7.com/techpubs/007-3683-007.pdf
> Signed-off-by: David Disseldorp <ddiss@suse.de>
> ---

This makes sense to me. Likes we've removed dmapi things, this "-o mtpt"
support can be removed too.

The _mount_ops_filter() might can be brought back if we need a filter
for _mount() in one day, I think that's another story. Now let's remove
it if it's useless.

Reviewed-by: Zorro Lang <zlang@redhat.com>

>  common/rc | 15 +--------------
>  1 file changed, 1 insertion(+), 14 deletions(-)
> 
> diff --git a/common/rc b/common/rc
> index 23530413..81ce1026 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -120,7 +120,7 @@ _get_hugepagesize()
>  
>  _mount()
>  {
> -    $MOUNT_PROG `_mount_ops_filter $*`
> +    $MOUNT_PROG $*
>  }
>  
>  # Call _mount to do mount operation but also save mountpoint to
> @@ -211,19 +211,6 @@ _test_options()
>  	TEST_OPTIONS="$TEST_OPTIONS ${log_opt}logdev=$TEST_LOGDEV"
>  }
>  
> -_mount_ops_filter()
> -{
> -    local params="$*"
> -    local last_index=$(( $# - 1 ))
> -
> -    [ $last_index -gt 0 ] && shift $last_index
> -    local fs_escaped=$1
> -
> -    echo $params | \
> -        $PERL_PROG -ne "s#mtpt=[^,|^\n|^\s]*#mtpt=$fs_escaped\1\2#; print;"
> -
> -}
> -
>  # Used for mounting non-scratch devices (e.g. loop, dm constructs)
>  # with the safe set of scratch mount options (e.g. loop image may be
>  # hosted on $SCRATCH_DEV, so can't use external scratch devices).
> -- 
> 2.35.3
> 


      reply	other threads:[~2023-01-11 10:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10 22:22 [PATCH] common/rc: drop SGI DMF specific _mount_ops_filter David Disseldorp
2023-01-11  9:56 ` Zorro Lang [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=20230111095609.xca2wmkgsdxaiwqt@zlang-mailbox \
    --to=zlang@redhat.com \
    --cc=ddiss@suse.de \
    --cc=fstests@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.