<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/fs/ext4/super.c, branch linux-2.6.28.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.28.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.28.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2009-03-17T00:32:33Z</updated>
<entry>
<title>Revert "ext4: wait on all pending commits in ext4_sync_fs()"</title>
<updated>2009-03-17T00:32:33Z</updated>
<author>
<name>Jan Kara</name>
</author>
<published>2009-02-24T17:14:42Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=00d9374d7af832e275bfc54c1d542cdb21c31797'/>
<id>urn:sha1:00d9374d7af832e275bfc54c1d542cdb21c31797</id>
<content type='text'>
(cherry picked from commit 9eddacf9e9c03578ef2c07c9534423e823d677f8)

This undoes commit 14ce0cb411c88681ab8f3a4c9caa7f42e97a3184.

Since jbd2_journal_start_commit() is now fixed to return 1 when we
started a transaction commit, there's some transaction waiting to be
committed or there's a transaction already committing, we don't
need to call ext4_force_commit() in ext4_sync_fs(). Furthermore
ext4_force_commit() can unnecessarily create sync transaction which is
expensive so it's worthwhile to remove it when we can.

http://bugzilla.kernel.org/show_bug.cgi?id=12224

Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
Cc: Eric Sandeen &lt;sandeen@redhat.com&gt;
Cc: linux-ext4@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ext4: Add sanity checks for the superblock before mounting the filesystem</title>
<updated>2009-02-20T22:40:28Z</updated>
<author>
<name>Theodore Ts'o</name>
</author>
<published>2009-02-17T15:32:38Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6a09fd55e8ea8312125ec6f7b86dad9ea44991b7'/>
<id>urn:sha1:6a09fd55e8ea8312125ec6f7b86dad9ea44991b7</id>
<content type='text'>
(cherry picked from commit 4ec110281379826c5cf6ed14735e47027c3c5765)

This avoids insane superblock configurations that could lead to kernel
oops due to null pointer derefences.

http://bugzilla.kernel.org/show_bug.cgi?id=12371

Thanks to David Maciejak at Fortinet's FortiGuard Global Security
Research Team who discovered this bug independently (but at
approximately the same time) as Thiemo Nagel, who submitted the patch.

Signed-off-by: Thiemo Nagel &lt;thiemo.nagel@ph.tum.de&gt;
Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ext4: avoid ext4_error when mounting a fs with a single bg</title>
<updated>2009-02-20T22:40:23Z</updated>
<author>
<name>Aneesh Kumar K.V</name>
</author>
<published>2009-02-20T22:40:23Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5a7330c4bf35a4943e0ee0a1ad3373f8ce99654a'/>
<id>urn:sha1:5a7330c4bf35a4943e0ee0a1ad3373f8ce99654a</id>
<content type='text'>
(cherry picked from commit 565a9617b2151e21b22700e97a8b04e70e103153)

Remove some completely unneeded code which which caused an ext4_error
to be generated when mounting a file system with only a single block
group.

Signed-off-by: Aneesh Kumar K.V &lt;aneesh.kumar@linux.vnet.ibm.com&gt;
Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ext4: Add support for non-native signed/unsigned htree hash algorithms</title>
<updated>2009-02-20T22:40:22Z</updated>
<author>
<name>Theodore Ts'o</name>
</author>
<published>2009-02-17T15:32:19Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=69db706481e3d100c6def5bf15b251f2a6ef03ab'/>
<id>urn:sha1:69db706481e3d100c6def5bf15b251f2a6ef03ab</id>
<content type='text'>
(cherry picked from commit f99b25897a86fcfff9140396a97261ae65fed872)

The original ext3 hash algorithms assumed that variables of type char
were signed, as God and K&amp;R intended.  Unfortunately, this assumption
is not true on some architectures.  Userspace support for marking
filesystems with non-native signed/unsigned chars was added two years
ago, but the kernel-side support was never added (until now).

Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>ext4: wait on all pending commits in ext4_sync_fs()</title>
<updated>2008-11-03T23:10:55Z</updated>
<author>
<name>Theodore Ts'o</name>
</author>
<published>2008-11-03T23:10:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=14ce0cb411c88681ab8f3a4c9caa7f42e97a3184'/>
<id>urn:sha1:14ce0cb411c88681ab8f3a4c9caa7f42e97a3184</id>
<content type='text'>
In ext4_sync_fs, we only wait for a commit to finish if we started it,
but there may be one already in progress which will not be synced.

In the case of a data=ordered umount with pending long symlinks which
are delayed due to a long list of other I/O on the backing block
device, this causes the buffer associated with the long symlinks to
not be moved to the inode dirty list in the second phase of
fsync_super.  Then, before they can be dirtied again, kjournald exits,
seeing the UMOUNT flag and the dirty pages are never written to the
backing block device, causing long symlink corruption and exposing new
or previously freed block data to userspace.

To ensure all commits are synced, we flush all journal commits now
when sync_fs'ing ext4.

Signed-off-by: Arthur Jones &lt;ajones@riverbed.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
Cc: Eric Sandeen &lt;sandeen@redhat.com&gt;
Cc: &lt;linux-ext4@vger.kernel.org&gt;
</content>
</entry>
<entry>
<title>ext4: Convert to host order before using the values.</title>
<updated>2008-11-04T14:11:26Z</updated>
<author>
<name>Aneesh Kumar K.V</name>
</author>
<published>2008-11-04T14:11:26Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d94e99a64c3beece22dbfb2b335771a59184eb0a'/>
<id>urn:sha1:d94e99a64c3beece22dbfb2b335771a59184eb0a</id>
<content type='text'>
Use le16_to_cpu to read the s_reserved_gdt_blocks values
from super block.

Signed-off-by: Aneesh Kumar K.V &lt;aneesh.kumar@linux.vnet.ibm.com&gt;
Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
</content>
</entry>
<entry>
<title>ext4: fix a bug accessing freed memory in ext4_abort</title>
<updated>2008-10-28T02:53:05Z</updated>
<author>
<name>Hidehiro Kawai</name>
</author>
<published>2008-10-28T02:53:05Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ef2cabf7c6d838eb0ee2b4fb8ef84f7c06ce16d9'/>
<id>urn:sha1:ef2cabf7c6d838eb0ee2b4fb8ef84f7c06ce16d9</id>
<content type='text'>
Vegard Nossum reported a bug which accesses freed memory (found via
kmemcheck).  When journal has been aborted, ext4_put_super() calls
ext4_abort() after freeing the journal_t object, and then ext4_abort()
accesses it.  This patch fix it.

Signed-off-by: Hidehiro Kawai &lt;hidehiro.kawai.ez@hitachi.com&gt;
Acked-by: Jan Kara &lt;jack@suse.cz&gt;
Signed-off-by: "Theodore Ts'o" &lt;tytso@mit.edu&gt;
</content>
</entry>
<entry>
<title>Merge git://git.kernel.org/pub/scm/linux/kernel/git/viro/bdev</title>
<updated>2008-10-23T17:23:07Z</updated>
<author>
<name>Linus Torvalds</name>
</author>
<published>2008-10-23T17:23:07Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=22484856402bfa1ff3defe47f6029ab0418240d9'/>
<id>urn:sha1:22484856402bfa1ff3defe47f6029ab0418240d9</id>
<content type='text'>
* git://git.kernel.org/pub/scm/linux/kernel/git/viro/bdev: (66 commits)
  [PATCH] kill the rest of struct file propagation in block ioctls
  [PATCH] get rid of struct file use in blkdev_ioctl() BLKBSZSET
  [PATCH] get rid of blkdev_locked_ioctl()
  [PATCH] get rid of blkdev_driver_ioctl()
  [PATCH] sanitize blkdev_get() and friends
  [PATCH] remember mode of reiserfs journal
  [PATCH] propagate mode through swsusp_close()
  [PATCH] propagate mode through open_bdev_excl/close_bdev_excl
  [PATCH] pass fmode_t to blkdev_put()
  [PATCH] kill the unused bsize on the send side of /dev/loop
  [PATCH] trim file propagation in block/compat_ioctl.c
  [PATCH] end of methods switch: remove the old ones
  [PATCH] switch sr
  [PATCH] switch sd
  [PATCH] switch ide-scsi
  [PATCH] switch tape_block
  [PATCH] switch dcssblk
  [PATCH] switch dasd
  [PATCH] switch mtd_blkdevs
  [PATCH] switch mmc
  ...
</content>
</entry>
<entry>
<title>[PATCH] switch quota_on-related stuff to kern_path()</title>
<updated>2008-10-23T09:12:44Z</updated>
<author>
<name>Al Viro</name>
</author>
<published>2008-08-02T04:57:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8264613def2e5c4f12bc3167713090fd172e6055'/>
<id>urn:sha1:8264613def2e5c4f12bc3167713090fd172e6055</id>
<content type='text'>
Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>[PATCH] pass fmode_t to blkdev_put()</title>
<updated>2008-10-21T11:48:58Z</updated>
<author>
<name>Al Viro</name>
</author>
<published>2008-02-23T01:40:24Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9a1c3542768b5a58e45a9216921cd10a3bae1205'/>
<id>urn:sha1:9a1c3542768b5a58e45a9216921cd10a3bae1205</id>
<content type='text'>
Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
</content>
</entry>
</feed>
