From: Johannes Weiner <hnazfoo@googlemail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC] #define rwxr_xr_x 0755
Date: Sat, 29 Jul 2006 15:58:37 +0200 [thread overview]
Message-ID: <20060729135837.GB28712@leiferikson.dystopia.lan> (raw)
In-Reply-To: <20060727205911.GB5356@martell.zuzino.mipt.ru>
Hi,
On Fri, Jul 28, 2006 at 12:59:11AM +0400, Alexey Dobriyan wrote:
> Every time I try to decipher S_I* combos I cry in pain. Often I just
> refer to include/linux/stat.h defines to find out what mode it is
> because numbers are actually quickier to understand.
>
> Compare and contrast:
>
> 0644 vs S_IRUGO|S_IWUSR vs rw_r__r__
>
> I'd say #2 really sucks.
I understood the octal notation at once. #2 took a second, I'd prefer
writing it S_IRUGO | S_IWUSR which makes it slightly more obvious.
#3 is even better than #2 but still sucks. What against octals?
> What people think? Should folks at Moscow call 03 ASAP?
>
> --- a/fs/smbfs/inode.c
> +++ b/fs/smbfs/inode.c
> @@ -575,10 +575,8 @@ static int smb_fill_super(struct super_b
> mnt->flags = (oldmnt->file_mode >> 9) | SMB_MOUNT_UID |
> SMB_MOUNT_GID | SMB_MOUNT_FMODE | SMB_MOUNT_DMODE;
> } else {
> - mnt->file_mode = S_IRWXU | S_IRGRP | S_IXGRP |
> - S_IROTH | S_IXOTH | S_IFREG;
> - mnt->dir_mode = S_IRWXU | S_IRGRP | S_IXGRP |
> - S_IROTH | S_IXOTH | S_IFDIR;
> + mnt->file_mode = rwxr_xr_x | S_IFREG;
0755 | S_IFREG is more readable I think.
> + mnt->dir_mode = rwxr_xr_x | S_IFDIR;
0755 | S_IFDIR ; same here
Hannes
next prev parent reply other threads:[~2006-07-29 13:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 20:59 [RFC] #define rwxr_xr_x 0755 Alexey Dobriyan
2006-07-27 22:23 ` Björn Steinbrink
2006-07-28 16:34 ` Handle X
2006-07-28 16:48 ` Josef Sipek
2006-07-29 1:43 ` Dmitry Torokhov
2006-07-29 7:59 ` Jan Engelhardt
2006-07-28 3:22 ` Josef Sipek
2006-07-29 13:58 ` Johannes Weiner [this message]
2006-07-28 4:54 Albert Cahalan
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=20060729135837.GB28712@leiferikson.dystopia.lan \
--to=hnazfoo@googlemail.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;
as well as URLs for NNTP newsgroup(s).