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

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

[Karel Kulhavy]

----- 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 -----

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

[OGAWA Hirofumi]

Karel Kulhavy <clock@twibright.com> writes:

> ------- 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

Look util-linux-2.12q... hm, mount command is reseting the umask in main().
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>