<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/fs/fat/inode.c, branch linux-2.6.37.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.37.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.37.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2010-10-04T19:10:45Z</updated>
<entry>
<title>BKL: Remove BKL from fat</title>
<updated>2010-10-04T19:10:45Z</updated>
<author>
<name>Arnd Bergmann</name>
</author>
<published>2010-09-14T21:07:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3768744cfea7b995dce27f02341161fbfdfee80c'/>
<id>urn:sha1:3768744cfea7b995dce27f02341161fbfdfee80c</id>
<content type='text'>
The lock_kernel in fat_put_super is not needed because
it only protects the super block itself and we know that
no other thread can reach it because we are about to
kfree the object.

In the two fill_super functions, this converts the locking
to use lock_super like elsewhere in the fat code. This
is probably not needed either, but is consistent and puts
us on the safe side.

Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
Cc: OGAWA Hirofumi &lt;hirofumi@mail.parknet.co.jp&gt;
Cc: Jan Blunck &lt;jblunck@infradead.org&gt;
</content>
</entry>
<entry>
<title>covert fatfs to -&gt;evict_inode()</title>
<updated>2010-08-09T20:48:01Z</updated>
<author>
<name>Al Viro</name>
</author>
<published>2010-06-05T23:28:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=deee3ce466a3e2cfb54c93b8fd22bbccd19ea7d6'/>
<id>urn:sha1:deee3ce466a3e2cfb54c93b8fd22bbccd19ea7d6</id>
<content type='text'>
Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>get rid of cont_write_begin_newtrunc</title>
<updated>2010-08-09T20:47:31Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2010-06-04T09:29:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=282dc178849882289d30e58b54be6b2799b351aa'/>
<id>urn:sha1:282dc178849882289d30e58b54be6b2799b351aa</id>
<content type='text'>
Move the call to vmtruncate to get rid of accessive blocks to the callers
in preparation of the new truncate sequence and rename the non-truncating
version to cont_write_begin.

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>sort out blockdev_direct_IO variants</title>
<updated>2010-08-09T20:47:29Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2010-06-04T09:29:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=eafdc7d190a944c755a9fe68573c193e6e0217e7'/>
<id>urn:sha1:eafdc7d190a944c755a9fe68573c193e6e0217e7</id>
<content type='text'>
Move the call to vmtruncate to get rid of accessive blocks to the callers
in prepearation of the new truncate calling sequence.  This was only done
for DIO_LOCKING filesystems, so the __blockdev_direct_IO_newtrunc variant
was not needed anyway.  Get rid of blockdev_direct_IO_no_locking and
its _newtrunc variant while at it as just opencoding the two additional
paramters is shorted than the name suffix.

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>fat: convert to use the new truncate convention.</title>
<updated>2010-05-28T02:16:02Z</updated>
<author>
<name>npiggin@suse.de</name>
</author>
<published>2010-05-26T15:05:38Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=459f6ed3b8c74cedeb64e5a854394c0d40eda9cd'/>
<id>urn:sha1:459f6ed3b8c74cedeb64e5a854394c0d40eda9cd</id>
<content type='text'>
Cc: OGAWA Hirofumi &lt;hirofumi@mail.parknet.co.jp&gt;
Cc: Christoph Hellwig &lt;hch@lst.de&gt;
Signed-off-by: Nick Piggin &lt;npiggin@suse.de&gt;
Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>fatfs: ratelimit corruption report</title>
<updated>2010-05-25T15:07:04Z</updated>
<author>
<name>OGAWA Hirofumi</name>
</author>
<published>2010-05-24T21:33:12Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=aaa04b4875f30659a0eb429e0e5203ae7fb7b18e'/>
<id>urn:sha1:aaa04b4875f30659a0eb429e0e5203ae7fb7b18e</id>
<content type='text'>
Signed-off-by: OGAWA Hirofumi &lt;hirofumi@mail.parknet.co.jp&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>fat: Cleanup nls_unload() usage</title>
<updated>2010-03-15T20:49:05Z</updated>
<author>
<name>OGAWA Hirofumi</name>
</author>
<published>2010-03-15T20:48:09Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1bdb6f9199def1c3538c18089e499f5df5ff1747'/>
<id>urn:sha1:1bdb6f9199def1c3538c18089e499f5df5ff1747</id>
<content type='text'>
Other users doesn't check NULL explicitly. So, these doesn't also
check to remove inconsistency.

Signed-off-by: OGAWA Hirofumi &lt;hirofumi@mail.parknet.co.jp&gt;
</content>
</entry>
<entry>
<title>Merge git://git.kernel.org/pub/scm/linux/kernel/git/hirofumi/fatfs-2.6</title>
<updated>2010-03-13T00:35:21Z</updated>
<author>
<name>Linus Torvalds</name>
</author>
<published>2010-03-13T00:35:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9d85929fefd040ca84a5e04ee704d043efcc3c2e'/>
<id>urn:sha1:9d85929fefd040ca84a5e04ee704d043efcc3c2e</id>
<content type='text'>
* git://git.kernel.org/pub/scm/linux/kernel/git/hirofumi/fatfs-2.6:
  fat: Fix stat-&gt;f_namelen
  fat: Fix vfat_lookup()
</content>
</entry>
<entry>
<title>pass writeback_control to -&gt;write_inode</title>
<updated>2010-03-05T18:25:52Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2010-03-05T08:21:37Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a9185b41a4f84971b930c519f0c63bd450c4810d'/>
<id>urn:sha1:a9185b41a4f84971b930c519f0c63bd450c4810d</id>
<content type='text'>
This gives the filesystem more information about the writeback that
is happening.  Trond requested this for the NFS unstable write handling,
and other filesystems might benefit from this too by beeing able to
distinguish between the different callers in more detail.

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>fat: Fix stat-&gt;f_namelen</title>
<updated>2010-02-10T14:49:08Z</updated>
<author>
<name>Kevin Dankwardt</name>
</author>
<published>2010-02-10T14:43:40Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=eeb5b4ae81f4a750355fa0c15f4fea22fdf83be1'/>
<id>urn:sha1:eeb5b4ae81f4a750355fa0c15f4fea22fdf83be1</id>
<content type='text'>
I found that the length of a file name when created cannot exceed 255
characters, yet, pathconf(), via statfs(), returns the maximum as 260.

Signed-off-by: Kevin Dankwardt &lt;k@kcomputing.com&gt;
Signed-off-by: OGAWA Hirofumi &lt;hirofumi@mail.parknet.co.jp&gt;
</content>
</entry>
</feed>
