public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: t.artem@mailcity.com,
	OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
	Roman Zippel <zippel@linux-m68k.org>
Subject: MS_SILENT vs. vfat and hfs
Date: Wed, 2 Mar 2011 12:45:17 +0100	[thread overview]
Message-ID: <20110302114517.GA496@nb.net.home> (raw)


 The mount(8) command uses "quiet" mount option as a synonym to the
 MS_SILENT mount flag (since util-linux 2.7, Aug 1997).

 It means than on systems where is properly defined the MS_SILENT
 mount flags in headers is the "quiet" mount option always translated
 to the MS_SILENT mount flags and "quiet" string is never send to FS
 drivers.

   $ strace -e mount mount -o quiet /dev/sdb1 /mnt/test
   mount("/dev/sdb1", "/mnt/test", "vfat", MS_MGC_VAL|MS_SILENT, NULL) = 0
                                                      ^^^^^^^^^

 Unfortunately, 
 
   $ grep -r \"quiet\" *

   fat/inode.c:    {Opt_quiet, "quiet"},
   hfs/super.c:    { opt_quiet, "quiet" },

 vfat and hfs drivers use "quiet" as a mount option. That's bug.

 There should not be a collision between mount(8) mount options and
 filesystem specific mount options.

 My suggestion is to fix the fat and hfs code to use something other
 than "quiet" (shutup, noisless, ...). I think you don't have to care
 about backward compatibility, because it's probably broken for years.

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

             reply	other threads:[~2011-03-02 11:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-02 11:45 Karel Zak [this message]
2011-03-02 14:14 ` MS_SILENT vs. vfat and hfs OGAWA Hirofumi
2011-03-02 14:43   ` Karel Zak
2011-03-02 15:06     ` Karel Zak
2011-03-02 15:16       ` OGAWA Hirofumi
2011-03-02 15:13     ` OGAWA Hirofumi

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=20110302114517.GA496@nb.net.home \
    --to=kzak@redhat.com \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=t.artem@mailcity.com \
    --cc=zippel@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox