From: Jan Kara <firstname.lastname@example.org> To: Steve Magnani <email@example.com> Cc: "Roald Strauss" <firstname.lastname@example.org>, "Pali Rohár" <email@example.com>, "Jan Kara" <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org Subject: Re: UDF filesystem image with Write-Once UDF Access Type Date: Thu, 1 Aug 2019 09:44:04 +0200 [thread overview] Message-ID: <20190801074404.GB25064@quack2.suse.cz> (raw) In-Reply-To: <email@example.com> On Fri 26-07-19 12:44:34, Steve Magnani wrote: > 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. Yeah, you're right. We are currently completely ignoring the DomainIdentifier field and at least for read-write mounts we should make sure it is valid. So that's something that needs fixing. Honza -- Jan Kara <firstname.lastname@example.org> SUSE Labs, CR
next prev parent reply other threads:[~2019-08-01 7:44 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-07-12 10:02 Pali Rohár 2019-07-26 17:44 ` Steve Magnani 2019-08-01 7:44 ` Jan Kara [this message] 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=20190801074404.GB25064@quack2.suse.cz \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: UDF filesystem image with Write-Once UDF Access Type' \ /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
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).