From: Jeff Mahoney <jeffm@suse.de>
To: Chris Mason <chris.mason@oracle.com>
Cc: Btrfs Development List <linux-btrfs@vger.kernel.org>
Subject: Re: Device files on read-only file systems?
Date: Mon, 15 Aug 2011 13:19:06 -0400 [thread overview]
Message-ID: <4E49550A.1040204@suse.de> (raw)
In-Reply-To: <1313420293-sup-2507@shiny>
On 08/15/2011 10:58 AM, Chris Mason wrote:
> Excerpts from Jeff Mahoney's message of 2011-08-15 09:11:24 -0400:
>> Hi all -
>>
>> btrfs_permission currently returns -EROFS when the root is set read-only
>> and the open is requested read-write. It doesn't make an exception for
>> device files. Is this intentional?
>
> No, definitely not intentional.
Ok. I'll post a patch in a few minutes.
-Jeff
--
Jeff Mahoney
SUSE Labs
prev parent reply other threads:[~2011-08-15 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 13:11 Device files on read-only file systems? Jeff Mahoney
2011-08-15 14:58 ` Chris Mason
2011-08-15 17:19 ` Jeff Mahoney [this message]
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=4E49550A.1040204@suse.de \
--to=jeffm@suse.de \
--cc=chris.mason@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.