public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
* chmod errors compiling on btrfs
@ 2009-11-07 20:36 Andrew Benton
  2009-11-09 15:15 ` Chris Mason
  0 siblings, 1 reply; 5+ messages in thread
From: Andrew Benton @ 2009-11-07 20:36 UTC (permalink / raw)
  To: linux-btrfs

Hello World.
I've created a btrfs partition and have tried compiling some programs on 
it, however, some of them fail with errors due to incorrect permissions. 
e2fsprogs fails like this:-

make[1]: Leaving directory `/mnt/btrfs/sources/e2fsprogs-1.41.9'
make[1]: Entering directory `/mnt/btrfs/sources/e2fsprogs-1.41.9/lib/et'
	SUBST compile_et
make[1]: Leaving directory `/mnt/btrfs/sources/e2fsprogs-1.41.9/lib/et'
make[1]: Entering directory `/mnt/btrfs/sources/e2fsprogs-1.41.9/lib/ext2fs'
	SUBST ext2_err.et
	COMPILE_ET ext2_err.et
chmod: ext2_err.h: new permissions are r--r--rw-, not r--r--r--
chmod: ext2_err.c: new permissions are r--r--rw-, not r--r--r--
make[1]: *** [ext2_err.h] Error 1
make[1]: Leaving directory `/mnt/btrfs/sources/e2fsprogs-1.41.9/lib/ext2fs'
make: *** [subs] Error 2
andy:/mnt/btrfs/sources/e2fsprogs-1.41.9$


and coreutils fails like this:-

   CCLD   hostname
   CCLD   setuidgid
   CCLD   getlimits
   CCLD   su
make[3]: Leaving directory `/mnt/btrfs/sources/coreutils-7.6/src'
make[2]: Leaving directory `/mnt/btrfs/sources/coreutils-7.6/src'
Making all in doc
make[2]: Entering directory `/mnt/btrfs/sources/coreutils-7.6/doc'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/mnt/btrfs/sources/coreutils-7.6/doc'
Making all in man
make[2]: Entering directory `/mnt/btrfs/sources/coreutils-7.6/man'
   GEN    hostname.1
chmod: hostname.1-t: new permissions are r--rw-rw-, not r--r--r--
make[2]: *** [hostname.1] Error 1
make[2]: Leaving directory `/mnt/btrfs/sources/coreutils-7.6/man'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/mnt/btrfs/sources/coreutils-7.6'
make: *** [all] Error 2
andy:/mnt/btrfs/sources$

Both times the files created were world writeable when they should have 
been read only. I get the same errors if I compile as myself or root. If 
I compile in my home folder (on a reiserfs partition) they compile with 
no problem. I'm using a self compiled vanila 2.6.31.4 kernel. I created 
the partition with btrfs-progs-0.19.

Andy
(Andrew Benton)

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: chmod errors compiling on btrfs
  2009-11-07 20:36 chmod errors compiling on btrfs Andrew Benton
@ 2009-11-09 15:15 ` Chris Mason
  2009-11-09 17:30   ` Andrew Benton
  2009-11-09 18:58   ` Andrew Benton
  0 siblings, 2 replies; 5+ messages in thread
From: Chris Mason @ 2009-11-09 15:15 UTC (permalink / raw)
  To: Andrew Benton; +Cc: linux-btrfs

On Sat, Nov 07, 2009 at 08:36:40PM +0000, Andrew Benton wrote:
> 
> Both times the files created were world writeable when they should
> have been read only. I get the same errors if I compile as myself or
> root. If I compile in my home folder (on a reiserfs partition) they
> compile with no problem. I'm using a self compiled vanila 2.6.31.4
> kernel. I created the partition with btrfs-progs-0.19.

We fixed some umask problems recently, these should be fixed in the
master branch of the btrfs-unstable repo (which is against 2.6.31).

-chris


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: chmod errors compiling on btrfs
  2009-11-09 15:15 ` Chris Mason
@ 2009-11-09 17:30   ` Andrew Benton
  2009-11-09 18:58   ` Andrew Benton
  1 sibling, 0 replies; 5+ messages in thread
From: Andrew Benton @ 2009-11-09 17:30 UTC (permalink / raw)
  To: linux-btrfs

On 09/11/09 15:15, Chris Mason wrote:
> On Sat, Nov 07, 2009 at 08:36:40PM +0000, Andrew Benton wrote:
>>
>> Both times the files created were world writeable when they should
>> have been read only. I get the same errors if I compile as myself or
>> root. If I compile in my home folder (on a reiserfs partition) they
>> compile with no problem. I'm using a self compiled vanila 2.6.31.4
>> kernel. I created the partition with btrfs-progs-0.19.
>
> We fixed some umask problems recently, these should be fixed in the
> master branch of the btrfs-unstable repo (which is against 2.6.31).
>

Thanks, I'll give that a try

Andy


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: chmod errors compiling on btrfs
  2009-11-09 15:15 ` Chris Mason
  2009-11-09 17:30   ` Andrew Benton
@ 2009-11-09 18:58   ` Andrew Benton
  2009-11-09 19:14     ` Chris Mason
  1 sibling, 1 reply; 5+ messages in thread
From: Andrew Benton @ 2009-11-09 18:58 UTC (permalink / raw)
  To: linux-btrfs

On 09/11/09 15:15, Chris Mason wrote:
> We fixed some umask problems recently, these should be fixed in the
> master branch of the btrfs-unstable repo (which is against 2.6.31).
>

Thanks, that did the trick. Will these umask fixes be in the 2.6.32 kernel?

Andy

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: chmod errors compiling on btrfs
  2009-11-09 18:58   ` Andrew Benton
@ 2009-11-09 19:14     ` Chris Mason
  0 siblings, 0 replies; 5+ messages in thread
From: Chris Mason @ 2009-11-09 19:14 UTC (permalink / raw)
  To: Andrew Benton; +Cc: linux-btrfs

On Mon, Nov 09, 2009 at 06:58:07PM +0000, Andrew Benton wrote:
> On 09/11/09 15:15, Chris Mason wrote:
> >We fixed some umask problems recently, these should be fixed in the
> >master branch of the btrfs-unstable repo (which is against 2.6.31).
> >
> 
> Thanks, that did the trick. Will these umask fixes be in the 2.6.32 kernel?

Great.  They are already included in 2.6.32-rc releases

-chris


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2009-11-09 19:14 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-11-07 20:36 chmod errors compiling on btrfs Andrew Benton
2009-11-09 15:15 ` Chris Mason
2009-11-09 17:30   ` Andrew Benton
2009-11-09 18:58   ` Andrew Benton
2009-11-09 19:14     ` Chris Mason

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox