[bugzilla-daemon@gentoo.org: [Bug 93671] mount uses wrong default umask for fat filesystem]

From: Karel Kulhavy (clock_at_twibright.com)
Date: 06/27/05

  • Next message: Erik Slagter: "Re: Promise ATA/133 Errors With 2.6.10+"
    Date:	Mon, 27 Jun 2005 12:07:46 +0200
    To: linux-kernel@vger.kernel.org
    
    

    ----- Forwarded message from bugzilla-daemon@gentoo.org -----

    Date: Sun, 26 Jun 2005 23:36:36 +0000
    From: bugzilla-daemon@gentoo.org
    To: clock@twibright.com
    Subject: [Bug 93671] mount uses wrong default umask for fat filesystem

    Clear-Text: http://bugs.gentoo.org/show_bug.cgi?id=93671
    Secure: https://bugs.gentoo.org/show_bug.cgi?id=93671

    stian@nixia.no changed:

               What |Removed |Added
    ----------------------------------------------------------------------------
                     CC| |stian@nixia.no

    ------- Additional Comments From stian@nixia.no 2005-06-26 16:36 PDT -------
    This is not a mount bug, but a kernel-bug. umask=nnn is passed along other
    user-flags to the mount syscall as a string, and the kernel-filesystem driver
    parses the string and denies the syscall if a syntax-error occures. Not all
    filesystems supports umask, so umask is not sent unless spesified. If the mount
    man-page claims that umask is defaulted to the current shell umask setting, the
    kernel-driver needs to take this into account when umask isn't found in the
    string it receives from user-space. Just my 5 cent about this bug

    -- 
    Configure bugmail: http://bugs.gentoo.org/userprefs.cgi?tab=email
    ------- You are receiving this mail because: -------
    You reported the bug, or are watching the reporter.
    ----- End forwarded message -----
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at  http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at  http://www.tux.org/lkml/
    

  • Next message: Erik Slagter: "Re: Promise ATA/133 Errors With 2.6.10+"

    Relevant Pages

    • Re: evangelizing linux not needed
      ... Both should be umask (do a "man mount" to see mounting options). ... an installer to guess things for you. ... used for your stock kernel. ...
      (alt.os.linux)
    • Re: Latest microcode data from Intel
      ... A bit of a bug somewhere here... ... %preunscriptlet failed, exit status 1 ... umask 022 ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: rw vs. umask in mount call, also, conditional mounting
      ... The 'rw' option is something passed to the mount command that tells it ... The umask basically sets up the 'default' permissions set that will be ... > I have a usb card reader that when plugged into my system is either ...
      (comp.os.linux.setup)
    • Re: Changing permissions on a FAT32 drive shared by Linux and Windows
      ... > I have a FAT32 drive on my system that my fstab mounts in Linux, ... > use to store files on that I need to access in both OS's. ... Here are the options (taken from man mount) ... Set the umask. ...
      (comp.os.linux.misc)
    • Re: umask
      ... bug report said. ... several umask bugs that you might be running into. ... The other main problem I found is with Nautilus. ... fairly simple to add this patch to the nautilus srpm and rebuild it. ...
      (Fedora)