<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/fs/udf/inode.c, branch linux-3.4.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.4.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.4.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2015-09-18T01:20:45Z</updated>
<entry>
<title>udf: Check length of extended attributes and allocation descriptors</title>
<updated>2015-09-18T01:20:45Z</updated>
<author>
<name>Jan Kara</name>
</author>
<published>2015-01-07T12:49:08Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=97186c0935bcdf8b9a72d1d7063577c845c25ef9'/>
<id>urn:sha1:97186c0935bcdf8b9a72d1d7063577c845c25ef9</id>
<content type='text'>
commit 23b133bdc452aa441fcb9b82cbf6dd05cfd342d0 upstream.

Check length of extended attributes and allocation descriptors when
loading inodes from disk. Otherwise corrupted filesystems could confuse
the code and make the kernel oops.

Reported-by: Carl Henrik Lunde &lt;chlunde@ping.uio.no&gt;
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
[lizf: Backported to 3.4:
 - call make_bad_inode() and then return
 - relace bs with inode-&gt;i_sb-&gt;s_blocksize]
Signed-off-by: Zefan Li &lt;lizefan@huawei.com&gt;
</content>
</entry>
<entry>
<title>udf: Verify i_size when loading inode</title>
<updated>2015-04-14T09:33:47Z</updated>
<author>
<name>Jan Kara</name>
</author>
<published>2014-12-19T11:03:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f9063aff1c0a589d225267e895b180d097f62409'/>
<id>urn:sha1:f9063aff1c0a589d225267e895b180d097f62409</id>
<content type='text'>
commit e159332b9af4b04d882dbcfe1bb0117f0a6d4b58 upstream.

Verify that inode size is sane when loading inode with data stored in
ICB. Otherwise we may get confused later when working with the inode and
inode size is too big.

Reported-by: Carl Henrik Lunde &lt;chlunde@ping.uio.no&gt;
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
[lizf: Backported to 3.4: just return on error, as there's no "out" label]
Signed-off-by: Zefan Li &lt;lizefan@huawei.com&gt;
</content>
</entry>
<entry>
<title>udf: don't increment lenExtents while writing to a hole</title>
<updated>2013-01-17T16:50:53Z</updated>
<author>
<name>Namjae Jeon</name>
</author>
<published>2012-10-09T15:09:12Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4faf067ae71be3d652e09c3119ce8125498cdf64'/>
<id>urn:sha1:4faf067ae71be3d652e09c3119ce8125498cdf64</id>
<content type='text'>
commit fb719c59bdb4fca86ee1fd1f42ab3735ca12b6b2 upstream.

Incrementing lenExtents even while writing to a hole is bad
for performance as calls to udf_discard_prealloc and
udf_truncate_tail_extent would not return from start if
isize != lenExtents

Signed-off-by: Namjae Jeon &lt;namjae.jeon@samsung.com&gt;
Signed-off-by: Ashish Sangwan &lt;a.sangwan@samsung.com&gt;
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
Signed-off-by: Shuah Khan &lt;shuah.khan@hp.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>udf: fix memory leak while allocating blocks during write</title>
<updated>2013-01-17T16:50:53Z</updated>
<author>
<name>Namjae Jeon</name>
</author>
<published>2012-10-09T15:08:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8d00c77065819b747c6fc0b56234afea72f17332'/>
<id>urn:sha1:8d00c77065819b747c6fc0b56234afea72f17332</id>
<content type='text'>
commit 2fb7d99d0de3fd8ae869f35ab682581d8455887a upstream.

Need to brelse the buffer_head stored in cur_epos and next_epos.

Signed-off-by: Namjae Jeon &lt;namjae.jeon@samsung.com&gt;
Signed-off-by: Ashish Sangwan &lt;a.sangwan@samsung.com&gt;
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
Signed-off-by: Shuah Khan &lt;shuah.khan@hp.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>udf: Fix file entry logicalBlocksRecorded</title>
<updated>2012-02-29T20:53:47Z</updated>
<author>
<name>Steve Nickel</name>
</author>
<published>2012-02-16T17:53:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b2527bfa535956d99663718b9d9aac0b8fe3f017'/>
<id>urn:sha1:b2527bfa535956d99663718b9d9aac0b8fe3f017</id>
<content type='text'>
ECMA 1.67 requires setting logicalBlocksRecorded to zero if the file
has no extents. This should be checked in udf_update_inode().
udf_fill_inode() will then take care of itself.

Signed-off-by: Steven P. Nickel &lt;snickel@focusinfo.com&gt;
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
<entry>
<title>udf: Init/maintain file entry checkpoint field</title>
<updated>2012-02-29T20:53:46Z</updated>
<author>
<name>Steve Nickel</name>
</author>
<published>2012-02-14T05:28:42Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d5e2cf07c388dbd06579ab39672e1bd8b9754e65'/>
<id>urn:sha1:d5e2cf07c388dbd06579ab39672e1bd8b9754e65</id>
<content type='text'>
In accordance with ECMA 1.67 Part 4, 14.9.15, the checkpoint field
should be initialized to 1 at creation. (Zero is *not* a valid value.)

Signed-off-by: Steven P. Nickel &lt;snickel@focusinfo.com&gt;
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
<entry>
<title>Merge branch 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs</title>
<updated>2012-01-09T20:51:21Z</updated>
<author>
<name>Linus Torvalds</name>
</author>
<published>2012-01-09T20:51:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ac69e0928054ff29a5049902fb477f9c7605c773'/>
<id>urn:sha1:ac69e0928054ff29a5049902fb477f9c7605c773</id>
<content type='text'>
* 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs:
  ext2/3/4: delete unneeded includes of module.h
  ext{3,4}: Fix potential race when setversion ioctl updates inode
  udf: Mark LVID buffer as uptodate before marking it dirty
  ext3: Don't warn from writepage when readonly inode is spotted after error
  jbd: Remove j_barrier mutex
  reiserfs: Force inode evictions before umount to avoid crash
  reiserfs: Fix quota mount option parsing
  udf: Treat symlink component of type 2 as /
  udf: Fix deadlock when converting file from in-ICB one to normal one
  udf: Cleanup calling convention of inode_getblk()
  ext2: Fix error handling on inode bitmap corruption
  ext3: Fix error handling on inode bitmap corruption
  ext3: replace ll_rw_block with other functions
  ext3: NULL dereference in ext3_evict_inode()
  jbd: clear revoked flag on buffers before a new transaction started
  ext3: call ext3_mark_recovery_complete() when recovery is really needed
</content>
</entry>
<entry>
<title>udf: Fix deadlock when converting file from in-ICB one to normal one</title>
<updated>2012-01-09T12:52:08Z</updated>
<author>
<name>Jan Kara</name>
</author>
<published>2011-12-10T01:30:48Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d2eb8c359309ec45d6bf5b147303ab8e13be86ea'/>
<id>urn:sha1:d2eb8c359309ec45d6bf5b147303ab8e13be86ea</id>
<content type='text'>
During BKL removal in 2.6.38, conversion of files from in-ICB format to normal
format got broken. We call -&gt;writepage with i_data_sem held but udf_get_block()
also acquires i_data_sem thus creating A-A deadlock.

We fix the problem by dropping i_data_sem before calling -&gt;writepage() which is
safe since i_mutex still protects us against any changes in the file. Also fix
pagelock - i_data_sem lock inversion in udf_expand_file_adinicb() by dropping
i_data_sem before calling find_or_create_page().

CC: stable@kernel.org
Reported-by: Matthias Matiak &lt;netzpython@mail-on.us&gt;
Tested-by: Matthias Matiak &lt;netzpython@mail-on.us&gt;
Reviewed-by: Namjae Jeon &lt;linkinjeon@gmail.com&gt;
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
<entry>
<title>udf: Cleanup calling convention of inode_getblk()</title>
<updated>2012-01-09T12:52:08Z</updated>
<author>
<name>Jan Kara</name>
</author>
<published>2011-12-10T00:43:33Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7b0b0933a3ff6052addf4d49ea99f75ab27df2d0'/>
<id>urn:sha1:7b0b0933a3ff6052addf4d49ea99f75ab27df2d0</id>
<content type='text'>
inode_getblk() always returned NULL and passed results in its parameters.
Make the function return something useful - found block number.

Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
<entry>
<title>udf: propagate umode_t</title>
<updated>2012-01-04T03:55:08Z</updated>
<author>
<name>Al Viro</name>
</author>
<published>2011-07-26T07:18:29Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=faa17292fd3a5a80345511ea341a59ac40ab59dc'/>
<id>urn:sha1:faa17292fd3a5a80345511ea341a59ac40ab59dc</id>
<content type='text'>
note re mount options: fmask and dmask are explicitly truncated to 12bit,
UDF_INVALID_MODE just needs to be guaranteed to differ from any such value.
And umask is used only in &amp;= with umode_t, so we ignore other bits anyway.

Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
</content>
</entry>
</feed>
