From: "Pali Rohár" <pali.rohar@gmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Jan Kara <jack@suse.cz>
Subject: [WIP PATCH 0/4] Support for UDF 1.01 and 2.60 revisions
Date: Sun, 12 Jan 2020 18:59:29 +0100 [thread overview]
Message-ID: <20200112175933.5259-1-pali.rohar@gmail.com> (raw)
These are my work-in-progress patches for UDF 1.01 and 2.60 revisions.
Patches are untested and UDF 2.60 support is only in R/O mode.
I'm sending them to know what do you think about it. There is missing
code for parsing of numFiles, numDirs, minUDFReadRev and minUDFWriteRev
values from UDF 1.50 VAT discs, but this could be done in other patches.
PS: If somebody is interested in UDF 1.01 specification, please let me
know and I could send it. It is missing on OSTA website.
Pali Rohár (4):
udf: Do not access LVIDIU revision members when they are not filled
udf: Fix reading numFiles and numDirs from UDF 2.00+ VAT discs
udf: Fix reading minUDFReadRev and minUDFWriteRev from UDF 2.00+ VAT
discs
udf: Allow to read UDF 2.60 discs
fs/udf/super.c | 71 +++++++++++++++++++++++++++++++++++++++----------
fs/udf/udf_sb.h | 10 ++++++-
2 files changed, 66 insertions(+), 15 deletions(-)
--
2.20.1
next reply other threads:[~2020-01-12 18:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-12 17:59 Pali Rohár [this message]
2020-01-12 17:59 ` [WIP PATCH 1/4] udf: Do not access LVIDIU revision members when they are not filled Pali Rohár
2020-01-13 12:00 ` Jan Kara
2020-01-13 18:37 ` Pali Rohár
2020-01-14 12:01 ` Jan Kara
2020-01-12 17:59 ` [WIP PATCH 2/4] udf: Fix reading numFiles and numDirs from UDF 2.00+ VAT discs Pali Rohár
2020-01-13 11:58 ` Jan Kara
2020-01-13 18:11 ` Pali Rohár
2020-01-14 11:18 ` Jan Kara
2020-01-14 11:37 ` Jan Kara
2020-01-12 17:59 ` [WIP PATCH 3/4] udf: Fix reading minUDFReadRev and minUDFWriteRev " Pali Rohár
2020-01-12 17:59 ` [WIP PATCH 4/4] udf: Allow to read UDF 2.60 discs Pali Rohár
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=20200112175933.5259-1-pali.rohar@gmail.com \
--to=pali.rohar@gmail.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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.