<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/fs/udf/super.c, branch linux-5.9.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.9.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.9.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2020-11-05T10:51:41Z</updated>
<entry>
<title>udf: Fix memory leak when mounting</title>
<updated>2020-11-05T10:51:41Z</updated>
<author>
<name>Jan Kara</name>
</author>
<published>2020-09-22T10:20:14Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d4a5c29a9bef13c2003d0d200f27d04625ef1d22'/>
<id>urn:sha1:d4a5c29a9bef13c2003d0d200f27d04625ef1d22</id>
<content type='text'>
commit a7be300de800e755714c71103ae4a0d205e41e99 upstream.

udf_process_sequence() allocates temporary array for processing
partition descriptors on volume which it fails to free. Free the array
when it is not needed anymore.

Fixes: 7b78fd02fb19 ("udf: Fix handling of Partition Descriptors")
CC: stable@vger.kernel.org
Reported-by: syzbot+128f4dd6e796c98b3760@syzkaller.appspotmail.com
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>udf: Limit sparing table size</title>
<updated>2020-10-29T09:12:13Z</updated>
<author>
<name>Jan Kara</name>
</author>
<published>2020-09-25T12:53:08Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=310594d44c3d66c0472054ec4017243c2d4f8339'/>
<id>urn:sha1:310594d44c3d66c0472054ec4017243c2d4f8339</id>
<content type='text'>
[ Upstream commit 44ac6b829c4e173fdf6df18e6dd86aecf9a3dc99 ]

Although UDF standard allows it, we don't support sparing table larger
than a single block. Check it during mount so that we don't try to
access memory beyond end of buffer.

Reported-by: syzbot+9991561e714f597095da@syzkaller.appspotmail.com
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>udf: Replace HTTP links with HTTPS ones</title>
<updated>2020-07-14T12:37:39Z</updated>
<author>
<name>Alexander A. Klimov</name>
</author>
<published>2020-07-13T20:07:38Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=248727a49897c5f5f984353c67272a97a8429c4b'/>
<id>urn:sha1:248727a49897c5f5f984353c67272a97a8429c4b</id>
<content type='text'>
Rationale:
Reduces attack surface on kernel devs opening the links for MITM
as HTTPS traffic is much harder to manipulate.

Deterministic algorithm:
For each file:
  If not .svg:
    For each line:
      If doesn't contain `\bxmlns\b`:
        For each link, `\bhttp://[^# \t\r\n]*(?:\w|/)`:
	  If neither `\bgnu\.org/license`, nor `\bmozilla\.org/MPL\b`:
            If both the HTTP and HTTPS versions
            return 200 OK and serve the same content:
              Replace HTTP with HTTPS.

Link: https://lore.kernel.org/r/20200713200738.37800-1-grandmaster@al2klimov.de
Signed-off-by: Alexander A. Klimov &lt;grandmaster@al2klimov.de&gt;
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
<entry>
<title>udf: Clarify meaning of f_files in udf_statfs</title>
<updated>2020-01-20T12:59:41Z</updated>
<author>
<name>Jan Kara</name>
</author>
<published>2020-01-17T11:36:38Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=356557be8670ffdb6dc01cc2702e3614bcf64310'/>
<id>urn:sha1:356557be8670ffdb6dc01cc2702e3614bcf64310</id>
<content type='text'>
UDF does not have separate preallocated table of inodes. So similarly to
XFS we pretend that every free block is also a free inode in statfs(2)
output. Clarify this in a comment.

Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
<entry>
<title>udf: Allow writing to 'Rewritable' partitions</title>
<updated>2020-01-20T12:59:17Z</updated>
<author>
<name>Jan Kara</name>
</author>
<published>2020-01-17T11:11:14Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=15fb05fd286ac57a0802d71624daeb5c1c2d5b07'/>
<id>urn:sha1:15fb05fd286ac57a0802d71624daeb5c1c2d5b07</id>
<content type='text'>
UDF 2.60 standard states in section 2.2.14.2:

    A partition with Access Type 3 (rewritable) shall define a Freed
    Space Bitmap or a Freed Space Table, see 2.3.3. All other partitions
    shall not define a Freed Space Bitmap or a Freed Space Table.

    Rewritable partitions are used on media that require some form of
    preprocessing before re-writing data (for example legacy MO). Such
    partitions shall use Access Type 3.

    Overwritable partitions are used on media that do not require
    preprocessing before overwriting data (for example: CD-RW, DVD-RW,
    DVD+RW, DVD-RAM, BD-RE, HD DVD-Rewritable). Such partitions shall
    use Access Type 4.

however older versions of the standard didn't have this wording and
there are tools out there that create UDF filesystems with rewritable
partitions but that don't contain a Freed Space Bitmap or a Freed Space
Table on media that does not require pre-processing before overwriting a
block. So instead of forcing media with rewritable partition read-only,
base this decision on presence of a Freed Space Bitmap or a Freed Space
Table.

Reported-by: Pali Rohár &lt;pali.rohar@gmail.com&gt;
Reviewed-by: Pali Rohár &lt;pali.rohar@gmail.com&gt;
Fixes: b085fbe2ef7f ("udf: Fix crash during mount")
Link: https://lore.kernel.org/linux-fsdevel/20200112144735.hj2emsoy4uwsouxz@pali
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
<entry>
<title>udf: Disallow R/W mode for disk with Metadata partition</title>
<updated>2020-01-13T11:40:17Z</updated>
<author>
<name>Pali Rohár</name>
</author>
<published>2020-01-12T14:49:59Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=57debb815459d2ef3e25aacfe355307d14b73a91'/>
<id>urn:sha1:57debb815459d2ef3e25aacfe355307d14b73a91</id>
<content type='text'>
Currently we do not support writing to UDF disks with Metadata partition.
There is already check that disks with declared minimal write revision to
UDF 2.50 or higher are mounted only in R/O mode but this does not cover
situation when minimal write revision is set incorrectly (e.g. to 2.01).

Link: https://lore.kernel.org/r/20200112144959.28104-1-pali.rohar@gmail.com
Signed-off-by: Pali Rohár &lt;pali.rohar@gmail.com&gt;
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
<entry>
<title>udf: Fix meaning of ENTITYID_FLAGS_* macros to be really bitwise-or flags</title>
<updated>2020-01-13T11:38:46Z</updated>
<author>
<name>Pali Rohár</name>
</author>
<published>2020-01-12T22:13:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=49be68c4931d9f0f171e5f01a574fc40205db2b5'/>
<id>urn:sha1:49be68c4931d9f0f171e5f01a574fc40205db2b5</id>
<content type='text'>
Currently ENTITYID_FLAGS_* macros definitions are written as hex numbers
but their meaning is not bitwise-or flags. But rather bit position. This is
unusual and could be misleading. So change meaning of ENTITYID_FLAGS_*
macros definitions to be really bitwise-or flags.

Link: https://lore.kernel.org/r/20200112221353.29711-1-pali.rohar@gmail.com
Signed-off-by: Pali Rohár &lt;pali.rohar@gmail.com&gt;
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
<entry>
<title>udf: Fix free space reporting for metadata and virtual partitions</title>
<updated>2020-01-09T17:38:18Z</updated>
<author>
<name>Jan Kara</name>
</author>
<published>2020-01-07T15:36:49Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a4a8b99ec819ca60b49dc582a4287ef03411f117'/>
<id>urn:sha1:a4a8b99ec819ca60b49dc582a4287ef03411f117</id>
<content type='text'>
Free space on filesystems with metadata or virtual partition maps
currently gets misreported. This is because these partitions are just
remapped onto underlying real partitions from which keep track of free
blocks. Take this remapping into account when counting free blocks as
well.

Reviewed-by: Pali Rohár &lt;pali.rohar@gmail.com&gt;
Reported-by: Pali Rohár &lt;pali.rohar@gmail.com&gt;
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
<entry>
<title>udf: Move OSTA Identifier Suffix macros from ecma_167.h to osta_udf.h</title>
<updated>2020-01-08T10:12:18Z</updated>
<author>
<name>Pali Rohár</name>
</author>
<published>2020-01-07T21:29:03Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=871b9b14c673d862b2f24478ed3583a40906ea66'/>
<id>urn:sha1:871b9b14c673d862b2f24478ed3583a40906ea66</id>
<content type='text'>
Rename structure name and its members to match naming convention and fix
endianity type for UDFRevision member. Also remove duplicate definition of
UDF_ID_COMPLIANT which is already in osta_udf.h.

Link: https://lore.kernel.org/r/20200107212904.30471-2-pali.rohar@gmail.com
Signed-off-by: Pali Rohár &lt;pali.rohar@gmail.com&gt;
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
<entry>
<title>fs-udf: Delete an unnecessary check before brelse()</title>
<updated>2019-09-04T16:19:43Z</updated>
<author>
<name>Markus Elfring</name>
</author>
<published>2019-09-03T19:12:09Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4eb09e1112180672795f4238e9252531f607c7a7'/>
<id>urn:sha1:4eb09e1112180672795f4238e9252531f607c7a7</id>
<content type='text'>
The brelse() function tests whether its argument is NULL
and then returns immediately.
Thus the test around the call is not needed.

This issue was detected by using the Coccinelle software.

Signed-off-by: Markus Elfring &lt;elfring@users.sourceforge.net&gt;
Link: https://lore.kernel.org/r/a254c1d1-0109-ab51-c67a-edc5c1c4b4cd@web.de
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
</feed>
