<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/fs/udf/inode.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-10-29T09:12:14Z</updated>
<entry>
<title>udf: Avoid accessing uninitialized data on failed inode read</title>
<updated>2020-10-29T09:12:14Z</updated>
<author>
<name>Jan Kara</name>
</author>
<published>2020-09-25T10:14:03Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=fc9db7fbbf6238ef22e684c29894a4d76911943e'/>
<id>urn:sha1:fc9db7fbbf6238ef22e684c29894a4d76911943e</id>
<content type='text'>
[ Upstream commit 044e2e26f214e5ab26af85faffd8d1e4ec066931 ]

When we fail to read inode, some data accessed in udf_evict_inode() may
be uninitialized. Move the accesses to !is_bad_inode() branch.

Reported-by: syzbot+91f02b28f9bb5f5f1341@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>fs: convert mpage_readpages to mpage_readahead</title>
<updated>2020-06-02T17:59:07Z</updated>
<author>
<name>Matthew Wilcox (Oracle)</name>
</author>
<published>2020-06-02T04:47:02Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d4388340ae0bc8397ef5b24342279f7739982918'/>
<id>urn:sha1:d4388340ae0bc8397ef5b24342279f7739982918</id>
<content type='text'>
Implement the new readahead aop and convert all callers (block_dev,
exfat, ext2, fat, gfs2, hpfs, isofs, jfs, nilfs2, ocfs2, omfs, qnx6,
reiserfs &amp; udf).

The callers are all trivial except for GFS2 &amp; OCFS2.

Signed-off-by: Matthew Wilcox (Oracle) &lt;willy@infradead.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Reviewed-by: Junxiao Bi &lt;junxiao.bi@oracle.com&gt; # ocfs2
Reviewed-by: Joseph Qi &lt;joseph.qi@linux.alibaba.com&gt; # ocfs2
Reviewed-by: Dave Chinner &lt;dchinner@redhat.com&gt;
Reviewed-by: John Hubbard &lt;jhubbard@nvidia.com&gt;
Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;
Reviewed-by: William Kucharski &lt;william.kucharski@oracle.com&gt;
Cc: Chao Yu &lt;yuchao0@huawei.com&gt;
Cc: Cong Wang &lt;xiyou.wangcong@gmail.com&gt;
Cc: Darrick J. Wong &lt;darrick.wong@oracle.com&gt;
Cc: Eric Biggers &lt;ebiggers@google.com&gt;
Cc: Gao Xiang &lt;gaoxiang25@huawei.com&gt;
Cc: Jaegeuk Kim &lt;jaegeuk@kernel.org&gt;
Cc: Michal Hocko &lt;mhocko@suse.com&gt;
Cc: Zi Yan &lt;ziy@nvidia.com&gt;
Cc: Johannes Thumshirn &lt;johannes.thumshirn@wdc.com&gt;
Cc: Miklos Szeredi &lt;mszeredi@redhat.com&gt;
Link: http://lkml.kernel.org/r/20200414150233.24495-17-willy@infradead.org
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&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: augment UDF permissions on new inodes</title>
<updated>2019-08-27T13:38:46Z</updated>
<author>
<name>Steven J. Magnani</name>
</author>
<published>2019-08-27T12:13:59Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c3367a1b47d590f97109cd4b5189e750fb26c0f1'/>
<id>urn:sha1:c3367a1b47d590f97109cd4b5189e750fb26c0f1</id>
<content type='text'>
Windows presents files created within Linux as read-only, even when
permissions in Linux indicate the file should be writable.

UDF defines a slightly different set of basic file permissions than Linux.
Specifically, UDF has "delete" and "change attribute" permissions for each
access class (user/group/other). Linux has no equivalents for these.

When the Linux UDF driver creates a file (or directory), no UDF delete or
change attribute permissions are granted. The lack of delete permission
appears to cause Windows to mark an item read-only when its permissions
otherwise indicate that it should be read-write.

Fix this by having UDF delete permissions track Linux write permissions.
Also grant UDF change attribute permission to the owner when creating a
new inode.

Reported by: Ty Young
Signed-off-by: Steven J. Magnani &lt;steve@digidescorp.com&gt;
Link: https://lore.kernel.org/r/20190827121359.9954-1-steve@digidescorp.com
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
<entry>
<title>udf: reduce leakage of blocks related to named streams</title>
<updated>2019-08-26T09:17:55Z</updated>
<author>
<name>Steven J. Magnani</name>
</author>
<published>2019-08-14T12:50:02Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ab9a3a737284b3d9e1d2ba43a0ef31b3ef2e2417'/>
<id>urn:sha1:ab9a3a737284b3d9e1d2ba43a0ef31b3ef2e2417</id>
<content type='text'>
Windows is capable of creating UDF files having named streams.
One example is the "Zone.Identifier" stream attached automatically
to files downloaded from a network. See:
  https://msdn.microsoft.com/en-us/library/dn392609.aspx

Modification of a file having one or more named streams in Linux causes
the stream directory to become detached from the file, essentially leaking
all blocks pertaining to the file's streams.

Fix by saving off information about an inode's streams when reading it,
for later use when its on-disk data is updated.

Link: https://lore.kernel.org/r/20190814125002.10869-1-steve@digidescorp.com
Signed-off-by: Steven J. Magnani &lt;steve@digidescorp.com&gt;
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
<entry>
<title>udf: Fix incorrect final NOT_ALLOCATED (hole) extent length</title>
<updated>2019-07-10T08:11:24Z</updated>
<author>
<name>Steven J. Magnani</name>
</author>
<published>2019-07-01T02:39:35Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=fa33cdbf3eceb0206a4f844fe91aeebcf6ff2b7a'/>
<id>urn:sha1:fa33cdbf3eceb0206a4f844fe91aeebcf6ff2b7a</id>
<content type='text'>
In some cases, using the 'truncate' command to extend a UDF file results
in a mismatch between the length of the file's extents (specifically, due
to incorrect length of the final NOT_ALLOCATED extent) and the information
(file) length. The discrepancy can prevent other operating systems
(i.e., Windows 10) from opening the file.

Two particular errors have been observed when extending a file:

1. The final extent is larger than it should be, having been rounded up
   to a multiple of the block size.

B. The final extent is not shorter than it should be, due to not having
   been updated when the file's information length was increased.

[JK: simplified udf_do_extend_final_block(), fixed up some types]

Fixes: 2c948b3f86e5 ("udf: Avoid IO in udf_clear_inode")
CC: stable@vger.kernel.org
Signed-off-by: Steven J. Magnani &lt;steve@digidescorp.com&gt;
Link: https://lore.kernel.org/r/1561948775-5878-1-git-send-email-steve@digidescorp.com
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 BUG on corrupted inode</title>
<updated>2018-12-12T14:48:49Z</updated>
<author>
<name>Jan Kara</name>
</author>
<published>2018-12-12T13:29:20Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d288d95842f1503414b7eebce3773bac3390457e'/>
<id>urn:sha1:d288d95842f1503414b7eebce3773bac3390457e</id>
<content type='text'>
When inode is corrupted so that extent type is invalid, some functions
(such as udf_truncate_extents()) will just BUG. Check that extent type
is valid when loading the inode to memory.

Reported-by: Anatoly Trosinenko &lt;anatoly.trosinenko@gmail.com&gt;
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
<entry>
<title>udf: convert inode stamps to timespec64</title>
<updated>2018-06-27T11:58:00Z</updated>
<author>
<name>Arnd Bergmann</name>
</author>
<published>2018-06-20T08:15:13Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c3b9cecd89b806e14544af596396e18abd00f145'/>
<id>urn:sha1:c3b9cecd89b806e14544af596396e18abd00f145</id>
<content type='text'>
The VFS structures are finally converted to always use 64-bit timestamps,
and this file system can represent a long range of on-disk timestamps
already, so now let's fit in the missing bits for udf.

Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
<entry>
<title>udf: Drop unused arguments of udf_delete_aext()</title>
<updated>2018-06-20T09:05:49Z</updated>
<author>
<name>Jan Kara</name>
</author>
<published>2018-06-13T16:04:24Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6c1e4d06a3808dc67dbce2d631f4c12574567dd5'/>
<id>urn:sha1:6c1e4d06a3808dc67dbce2d631f4c12574567dd5</id>
<content type='text'>
udf_delete_aext() uses its last two arguments only as local variables.
Drop them.

Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
</feed>
