From: Karel Kulhavy <clock@twibright.com>
To: linux-kernel@vger.kernel.org
Subject: [bugzilla-daemon@gentoo.org: [Bug 93671] mount uses wrong default umask for fat filesystem]
Date: Mon, 27 Jun 2005 12:07:46 +0200 [thread overview]
Message-ID: <20050627100746.GC24093@kestrel> (raw)
----- 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 -----
next reply other threads:[~2005-06-27 10:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 10:07 Karel Kulhavy [this message]
2005-06-27 14:42 ` [bugzilla-daemon@gentoo.org: [Bug 93671] mount uses wrong default umask for fat filesystem] 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=20050627100746.GC24093@kestrel \
--to=clock@twibright.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox