public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Benton <b3nton@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: chmod errors compiling on btrfs
Date: Mon, 09 Nov 2009 17:30:39 +0000	[thread overview]
Message-ID: <4AF851BF.7010304@gmail.com> (raw)
In-Reply-To: <20091109151503.GA2812@think>

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


  reply	other threads:[~2009-11-09 17:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2009-11-09 18:58   ` Andrew Benton
2009-11-09 19:14     ` Chris Mason

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=4AF851BF.7010304@gmail.com \
    --to=b3nton@gmail.com \
    --cc=linux-btrfs@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