From: Daniel Drake <dsd@gentoo.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OT] util-linux 2.13-pre1
Date: Thu, 04 Aug 2005 11:08:20 +0100 [thread overview]
Message-ID: <42F1E914.1060107@gentoo.org> (raw)
In-Reply-To: <20050802230751.GB4029@stusta.de>
[-- Attachment #1: Type: text/plain, Size: 258 bytes --]
Adrian,
Adrian Bunk wrote:
> util-linux 2.13-pre1 is available at
> ftp://ftp.kernel.org/pub/linux/utils/util-linux/testing/util-linux-2.13-pre1.tar.gz
Any comments on the mount patch I sent to you?
Attaching it again now. Please apply.
Thanks,
Daniel
[-- Attachment #2: util-linux-mount-umask.patch --]
[-- Type: text/x-patch, Size: 962 bytes --]
From: Daniel Drake <dsd@gentoo.org>
Some filesystems such as FAT will default to using the umask of the current
process if the user did not specify a umask option.
Currently, mount.c calls umask(022) early on, removing the possibility of the
user-specified umask (at shell level) being used by default.
Removing the umask(022) call solves the problem.
This appears safe to do, because the code which creates files already does this
safely (saves umask, sets umask 022, creates file, restores umask).
Please apply.
--- util-linux-2.13-pre1/mount/mount.c.orig 2005-08-04 11:00:50.000000000 +0100
+++ util-linux-2.13-pre1/mount/mount.c 2005-08-04 11:00:58.000000000 +0100
@@ -1466,8 +1466,6 @@ main(int argc, char *argv[]) {
if ((p = strrchr(progname, '/')) != NULL)
progname = p+1;
- umask(022);
-
/* People report that a mount called from init without console
writes error messages to /etc/mtab
Let us try to avoid getting fd's 0,1,2 */
next prev parent reply other threads:[~2005-08-04 10:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 23:07 [OT] util-linux 2.13-pre1 Adrian Bunk
2005-08-04 10:08 ` Daniel Drake [this message]
2005-08-09 19:49 ` Adrian Bunk
2005-08-09 11:46 ` P
2005-08-09 15:26 ` Adrian Bunk
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=42F1E914.1060107@gentoo.org \
--to=dsd@gentoo.org \
--cc=bunk@stusta.de \
--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