<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/fs/udf/truncate.c, branch linux-6.7.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-6.7.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-6.7.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2023-05-30T13:39:13Z</updated>
<entry>
<title>fs: udf: Replace GPL 2.0 boilerplate license notice with SPDX identifier</title>
<updated>2023-05-30T13:39:13Z</updated>
<author>
<name>Bagas Sanjaya</name>
</author>
<published>2023-05-22T00:54:34Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5ce345541ee43333bfbd99a2ea56b1a0a167c457'/>
<id>urn:sha1:5ce345541ee43333bfbd99a2ea56b1a0a167c457</id>
<content type='text'>
The notice refers to full GPL 2.0 text on now defunct MIT FTP site [1].
Replace it with appropriate SPDX license identifier.

Cc: Thomas Gleixner &lt;tglx@linutronix.de&gt;
Cc: Pali Rohár &lt;pali@kernel.org&gt;
Link: https://web.archive.org/web/20020809115410/ftp://prep.ai.mit.edu/pub/gnu/GPL [1]
Signed-off-by: Bagas Sanjaya &lt;bagasdotme@gmail.com&gt;
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
Message-Id: &lt;20230522005434.22133-2-bagasdotme@gmail.com&gt;
</content>
</entry>
<entry>
<title>udf: use wrapper i_blocksize() in udf_discard_prealloc()</title>
<updated>2023-03-13T10:16:16Z</updated>
<author>
<name>Yangtao Li</name>
</author>
<published>2023-03-10T03:08:20Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f768dc3cf74983107464bcd773167c92b85cb8f2'/>
<id>urn:sha1:f768dc3cf74983107464bcd773167c92b85cb8f2</id>
<content type='text'>
Convert to use i_blocksize() for readability.

Signed-off-by: Yangtao Li &lt;frank.li@vivo.com&gt;
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
Message-Id: &lt;20230310030821.66090-2-frank.li@vivo.com&gt;
</content>
</entry>
<entry>
<title>udf: Drop VARCONV support</title>
<updated>2023-01-26T15:46:32Z</updated>
<author>
<name>Jan Kara</name>
</author>
<published>2023-01-18T12:27:07Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=101ee137d32adc5b53f5c2a61fbda8f70f994845'/>
<id>urn:sha1:101ee137d32adc5b53f5c2a61fbda8f70f994845</id>
<content type='text'>
UDF was supporting a strange mode where the media was containing 7
blocks of unknown data for every 32 blocks of the filesystem. I have yet
to see the media that would need such conversion (maybe it comes from
packet writing times) and the conversions have been inconsistent in the
code. In particular any write will write to a wrong block and corrupt
the media. This is an indication and no user actually needs this so
let's just drop the support instead of trying to fix it.

Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
<entry>
<title>udf: remove redundant variable netype</title>
<updated>2023-01-09T09:39:53Z</updated>
<author>
<name>Colin Ian King</name>
</author>
<published>2023-01-05T13:49:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1fb40763a58c1f8130c0131c624060c6bbb929b8'/>
<id>urn:sha1:1fb40763a58c1f8130c0131c624060c6bbb929b8</id>
<content type='text'>
The variable netype is assigned a value that is never read, the assignment
is redundant the variable can be removed.

Message-Id: &lt;20230105134925.45599-1-colin.i.king@gmail.com&gt;
Signed-off-by: Colin Ian King &lt;colin.i.king@gmail.com&gt;
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
<entry>
<title>udf: Do not bother looking for prealloc extents if i_lenExtents matches i_size</title>
<updated>2022-12-09T11:37:26Z</updated>
<author>
<name>Jan Kara</name>
</author>
<published>2022-12-07T16:34:33Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6ad53f0f71c52871202a7bf096feb2c59db33fc5'/>
<id>urn:sha1:6ad53f0f71c52871202a7bf096feb2c59db33fc5</id>
<content type='text'>
If rounded block-rounded i_lenExtents matches block rounded i_size,
there are no preallocation extents. Do not bother walking extent linked
list.

CC: stable@vger.kernel.org
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
<entry>
<title>udf: Fix preallocation discarding at indirect extent boundary</title>
<updated>2022-12-09T11:37:26Z</updated>
<author>
<name>Jan Kara</name>
</author>
<published>2022-12-07T16:25:10Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=cfe4c1b25dd6d2f056afc00b7c98bcb3dd0b1fc3'/>
<id>urn:sha1:cfe4c1b25dd6d2f056afc00b7c98bcb3dd0b1fc3</id>
<content type='text'>
When preallocation extent is the first one in the extent block, the
code would corrupt extent tree header instead. Fix the problem and use
udf_delete_aext() for deleting extent to avoid some code duplication.

CC: stable@vger.kernel.org
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
<entry>
<title>udf: Fix spelling in EXT_NEXT_EXTENT_ALLOCDESCS</title>
<updated>2020-01-08T10:11:46Z</updated>
<author>
<name>Pali Rohár</name>
</author>
<published>2020-01-07T21:29:02Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=800552ceecc749aa4e87c95291be232c80bd1e56'/>
<id>urn:sha1:800552ceecc749aa4e87c95291be232c80bd1e56</id>
<content type='text'>
Change EXT_NEXT_EXTENT_ALLOCDECS to proper spelling
EXT_NEXT_EXTENT_ALLOCDESCS.

Link: https://lore.kernel.org/r/20200107212904.30471-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: Propagate errors from udf_truncate_extents()</title>
<updated>2019-03-18T15:30:02Z</updated>
<author>
<name>Jan Kara</name>
</author>
<published>2019-03-11T14:27:02Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2b42be5eb24564227b15e66f54f088e5a26549c7'/>
<id>urn:sha1:2b42be5eb24564227b15e66f54f088e5a26549c7</id>
<content type='text'>
Make udf_truncate_extents() properly propagate errors to its callers and
let udf_setsize() handle the error properly as well. This lets userspace
know in case there's some error when truncating blocks.

Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
<entry>
<title>udf: Fix crash on IO error during truncate</title>
<updated>2019-03-18T15:29:52Z</updated>
<author>
<name>Jan Kara</name>
</author>
<published>2019-03-11T14:04:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d3ca4651d05c0ff7259d087d8c949bcf3e14fb46'/>
<id>urn:sha1:d3ca4651d05c0ff7259d087d8c949bcf3e14fb46</id>
<content type='text'>
When truncate(2) hits IO error when reading indirect extent block the
code just bugs with:

kernel BUG at linux-4.15.0/fs/udf/truncate.c:249!
...

Fix the problem by bailing out cleanly in case of IO error.

CC: stable@vger.kernel.org
Reported-by: jean-luc malet &lt;jeanluc.malet@gmail.com&gt;
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
<entry>
<title>udf: Fix 64-bit sign extension issues affecting blocks &gt; 0x7FFFFFFF</title>
<updated>2017-10-17T09:56:45Z</updated>
<author>
<name>Steve Magnani</name>
</author>
<published>2017-10-12T13:48:40Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b490bdd630cc43a5725e76c7c23f8a7e55551145'/>
<id>urn:sha1:b490bdd630cc43a5725e76c7c23f8a7e55551145</id>
<content type='text'>
Large (&gt; 1 TiB) UDF filesystems appear subject to several problems when
mounted on 64-bit systems:

* readdir() can fail on a directory containing File Identifiers residing
  above 0x7FFFFFFF. This manifests as a 'ls' command failing with EIO.

* FIBMAP on a file block located above 0x7FFFFFFF can return a negative
  value. The low 32 bits are correct, but applications that don't mask the
  high 32 bits of the result can perform incorrectly.

Per suggestion by Jan Kara, introduce a udf_pblk_t type for representation
of UDF block addresses. Ultimately, all driver functions that manipulate
UDF block addresses should use this type; for now, deployment is limited
to functions with actual or potential sign extension issues.

Changes to udf_readdir() and udf_block_map() address the issues noted
above; other changes address potential similar issues uncovered during
audit of the driver code.

Signed-off-by: Steven J. Magnani &lt;steve@digidescorp.com&gt;
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
</feed>
