search for: s_irwxugo

Hello, when i compiled latest linux 2.6.4 kernel source with gcc 3.3.2 on Linux/x86, i got a few warnings about varaibles beeing compared against constants where the range of the variable is so that the expression is always constant. The explicit comparison has to do with the code for high-uid and gid sheme. attached you will find a diff which does eliminate this error message by introducing an

...dle *trans, int err; u64 index = 0; - inode = btrfs_new_inode(trans, new_root, NULL, "..", 2, new_dirid, - new_dirid, S_IFDIR | 0700, &index); + inode = btrfs_new_inode(trans, new_root, NULL, "..", 2, + new_dirid, new_dirid, + S_IFDIR | (~current_umask() & S_IRWXUGO), + &index); if (IS_ERR(inode)) return PTR_ERR(inode); inode->i_op = &btrfs_dir_inode_operations; -- 1.7.8.4 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http:...

...ndling of different servertypes. - (Not all operations are done this way. yet.) -2001-12-31 Ren? Scharfe <l.s.r@web.de> - - * inode.c: added smb_show_options to show mount options in /proc/mounts - * inode.c, getopt.c, getopt.h: merged flag and has_arg in struct option - * inode.c: use S_IRWXUGO where appropriate - -2001-12-22 Urban Widmark <urban@teststation.com> - - * file.c, proc.c: Fix problems triggered by the "fsx test" - -2001-09-17 Urban Widmark <urban@teststation.com> - - * proc.c: Use 4096 (was 512) as the blocksize for better write - performance (patch or...

...ndling of different servertypes. - (Not all operations are done this way. yet.) -2001-12-31 Ren? Scharfe <l.s.r@web.de> - - * inode.c: added smb_show_options to show mount options in /proc/mounts - * inode.c, getopt.c, getopt.h: merged flag and has_arg in struct option - * inode.c: use S_IRWXUGO where appropriate - -2001-12-22 Urban Widmark <urban@teststation.com> - - * file.c, proc.c: Fix problems triggered by the "fsx test" - -2001-09-17 Urban Widmark <urban@teststation.com> - - * proc.c: Use 4096 (was 512) as the blocksize for better write - performance (patch or...

If we have particularly full nodes, we could call btrfs_node_blockptr up to 32 times, which is 32 pairs of kmap/kunmap, which _sucks_. So go ahead and map the extent buffer while we look for readahead targets. Thanks, Signed-off-by: Josef Bacik <josef@redhat.com> --- fs/btrfs/ctree.c | 23 +++++++++++++++++++++-- 1 files changed, 21 insertions(+), 2 deletions(-) diff --git