All of lore.kernel.org
 help / color / mirror / Atom feed
From: nicholas.clark@gmail.com
To: nicholas.clark@gmail.com, linux-ext4@vger.kernel.org
Subject: [PATCH RESEND 1/2] Fuse2fs: fix 'mount' entry in some cases.
Date: Sun, 14 Oct 2018 08:58:36 -0600	[thread overview]
Message-ID: <20181014145837.6344-2-nicholas.clark@gmail.com> (raw)
In-Reply-To: <20181014145837.6344-1-nicholas.clark@gmail.com>

From: Nicholas Clark <nicholas.clark@gmail.com>

FUSE's parser allows command-line options to be specified before
or after the device/image and mount-path. This commit changes the
value of the fsname mount option to be correct even if options are
specified before the target device/image.

Signed-off-by: Nicholas Clark <nicholas.clark@gmail.com>
---
 misc/fuse2fs.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/misc/fuse2fs.c b/misc/fuse2fs.c
index 5c73895e..3214be4a 100644
--- a/misc/fuse2fs.c
+++ b/misc/fuse2fs.c
@@ -3845,7 +3845,7 @@ int main(int argc, char *argv[])
 	/* Set up default fuse parameters */
 	snprintf(extra_args, BUFSIZ, "-okernel_cache,subtype=ext4,use_ino,"
 		 "fsname=%s,attr_timeout=0" FUSE_PLATFORM_OPTS,
-		 argv[1]);
+		 fctx.device);
 	if (fctx.no_default_opts == 0)
 		fuse_opt_add_arg(&args, extra_args);
 
-- 
2.17.1

  reply	other threads:[~2018-10-14 22:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-14 14:58 [PATCH RESEND 0/2] e2fsprogs: fuse2fs bugfix and new 'fakeroot' feature nicholas.clark
2018-10-14 14:58 ` nicholas.clark [this message]
2018-10-14 14:58 ` [PATCH RESEND 2/2] Fuse2fs: add fakeroot option nicholas.clark
  -- strict thread matches above, loose matches on Subject: below --
2018-10-14 15:00 [PATCH RESEND 0/2] e2fsprogs: fuse2fs bugfix and new 'fakeroot' feature nicholas.clark
2018-10-14 15:00 ` [PATCH RESEND 1/2] Fuse2fs: fix 'mount' entry in some cases nicholas.clark
2018-10-16 19:38   ` Theodore Y. Ts'o

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=20181014145837.6344-2-nicholas.clark@gmail.com \
    --to=nicholas.clark@gmail.com \
    --cc=linux-ext4@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.