From: Steve Magnani <steve.magnani@digidescorp.com>
To: "Pali Rohár" <pali.rohar@gmail.com>, "Jan Kara" <jack@suse.com>,
"Roald Strauss" <mr_lou@dewfall.dk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: UDF filesystem image with Write-Once UDF Access Type
Date: Fri, 26 Jul 2019 12:44:34 -0500 [thread overview]
Message-ID: <35c0e9f3-b3b6-96c3-e339-2267a3abde9b@digidescorp.com> (raw)
In-Reply-To: <20190712100224.s2chparxszlbnill@pali>
Hi,
On 7/12/19 5:02 AM, Pali Rohár wrote:
> In my opinion without support for additional layer, kernel should treat
> UDF Write-Once Access Type as read-only mount for userspace. And not
> classic read/write mount.
>
> ...
>
> It seems that udf.ko does not support updating VAT table, so probably it
> should treat also filesystem with VAT as read-only too.
>
I thinkb085fbe2ef7fa7489903c45271ae7b7a52b0f9ab <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/udf?h=v5.1&id=b085fbe2ef7fa7489903c45271ae7b7a52b0f9ab>, deployed in 4.20,
does both of the things you want.
One case I ran across today that Windows handles, but Linux doesn't,
is write-protection via flags in the DomainIdentifier fields of the
Logical Volume Descriptor and File Set Descriptor. Linux allows
RW mount when those are marked protected, but Windows forces RO mount.
Regards,
------------------------------------------------------------------------
Steven J. Magnani "I claim this network for MARS!
www.digidescorp.com Earthling, return my space modulator!"
#include <standard.disclaimer>
next prev parent reply other threads:[~2019-07-26 17:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 10:02 UDF filesystem image with Write-Once UDF Access Type Pali Rohár
2019-07-26 17:44 ` Steve Magnani [this message]
2019-08-01 7:44 ` Jan Kara
2019-08-01 7:35 ` Jan Kara
2019-08-01 8:38 ` Jan Kara
2019-08-01 8:57 ` Pali Rohár
2019-08-02 10:28 ` Jan Kara
2019-08-01 8:44 ` Pali Rohár
2019-08-01 10:21 ` Roald Strauss
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=35c0e9f3-b3b6-96c3-e339-2267a3abde9b@digidescorp.com \
--to=steve.magnani@digidescorp.com \
--cc=jack@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mr_lou@dewfall.dk \
--cc=pali.rohar@gmail.com \
/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).