<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/fs/cifs/file.c, branch linux-3.3.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.3.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.3.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2012-04-13T16:13:54Z</updated>
<entry>
<title>CIFS: Fix VFS lock usage for oplocked files</title>
<updated>2012-04-13T16:13:54Z</updated>
<author>
<name>Pavel Shilovsky</name>
</author>
<published>2012-03-28T17:56:19Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=49c8ca7ade694f65de205adc08c23a710244b6b0'/>
<id>urn:sha1:49c8ca7ade694f65de205adc08c23a710244b6b0</id>
<content type='text'>
commit 66189be74ff5f9f3fd6444315b85be210d07cef2 upstream.

We can deadlock if we have a write oplock and two processes
use the same file handle. In this case the first process can't
unlock its lock if the second process blocked on the lock in the
same time.

Fix it by using posix_lock_file rather than posix_lock_file_wait
under cinode-&gt;lock_mutex. If we request a blocking lock and
posix_lock_file indicates that there is another lock that prevents
us, wait untill that lock is released and restart our call.

Acked-by: Jeff Layton &lt;jlayton@redhat.com&gt;
Signed-off-by: Pavel Shilovsky &lt;piastry@etersoft.ru&gt;
Signed-off-by: Steve French &lt;sfrench@us.ibm.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>CIFS: Fix a spurious error in cifs_push_posix_locks</title>
<updated>2012-04-02T17:32:07Z</updated>
<author>
<name>Pavel Shilovsky</name>
</author>
<published>2012-03-17T06:46:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a9f67ccd865caae489bf3f000fbac2004e43ba3e'/>
<id>urn:sha1:a9f67ccd865caae489bf3f000fbac2004e43ba3e</id>
<content type='text'>
commit ce85852b90a214cf577fc1b4f49d99fd7e98784a upstream.

Signed-off-by: Pavel Shilovsky &lt;piastry@etersoft.ru&gt;
Reviewed-by: Jeff Layton &lt;jlayton@redhat.com&gt;
Reported-by: Ben Hutchings &lt;ben@decadent.org.uk&gt;
Signed-off-by: Steve French &lt;sfrench@us.ibm.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>CIFS: Respect negotiated MaxMpxCount</title>
<updated>2012-04-02T17:32:07Z</updated>
<author>
<name>Pavel Shilovsky</name>
</author>
<published>2012-03-20T09:55:09Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ffb07758cafb009b64fc7db20a26d0561496c112'/>
<id>urn:sha1:ffb07758cafb009b64fc7db20a26d0561496c112</id>
<content type='text'>
commit 10b9b98e41ba248a899f6175ce96ee91431b6194 upstream.

Some servers sets this value less than 50 that was hardcoded and
we lost the connection if when we exceed this limit. Fix this by
respecting this value - not sending more than the server allows.

Reviewed-by: Jeff Layton &lt;jlayton@samba.org&gt;
Signed-off-by: Pavel Shilovsky &lt;piastry@etersoft.ru&gt;
Signed-off-by: Steve French &lt;smfrench@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>CIFS: Do not kmalloc under the flocks spinlock</title>
<updated>2012-03-07T03:50:15Z</updated>
<author>
<name>Pavel Shilovsky</name>
</author>
<published>2012-03-05T06:39:20Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d5751469f210d2149cc2159ffff66cbeef6da3f2'/>
<id>urn:sha1:d5751469f210d2149cc2159ffff66cbeef6da3f2</id>
<content type='text'>
Reorganize the code to make the memory already allocated before
spinlock'ed loop.

Cc: stable@vger.kernel.org
Reviewed-by: Jeff Layton &lt;jlayton@redhat.com&gt;
Signed-off-by: Pavel Shilovsky &lt;piastry@etersoft.ru&gt;
Signed-off-by: Steve French &lt;sfrench@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>CIFS: Add descriptions to the brlock cache functions</title>
<updated>2011-12-09T04:04:47Z</updated>
<author>
<name>Pavel Shilovsky</name>
</author>
<published>2011-11-07T13:11:24Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9a5101c8968c7b3e7de5564af6358d7332cf9a6b'/>
<id>urn:sha1:9a5101c8968c7b3e7de5564af6358d7332cf9a6b</id>
<content type='text'>
Signed-off-by: Pavel Shilovsky &lt;piastry@etersoft.ru&gt;
Signed-off-by: Steve French &lt;sfrench@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>CIFS: Cleanup byte-range locking code style</title>
<updated>2011-11-04T05:53:21Z</updated>
<author>
<name>Pavel Shilovsky</name>
</author>
<published>2011-10-29T13:17:59Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a88b470773bc5b640292d8be7b8e7e1011a86639'/>
<id>urn:sha1:a88b470773bc5b640292d8be7b8e7e1011a86639</id>
<content type='text'>
Reorder parms of cifs_lock_init, trivially simplify getlk code and
remove extra {} in cifs_lock_add_if.

Cc: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;
Acked-by: Jeff Layton &lt;jlayton@samba.org&gt;
Signed-off-by: Pavel Shilovsky &lt;piastry@etersoft.ru&gt;
Signed-off-by: Steve French &lt;sfrench@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>CIFS: Simplify setlk error handling for mandatory locking</title>
<updated>2011-11-04T05:53:15Z</updated>
<author>
<name>Pavel Shilovsky</name>
</author>
<published>2011-10-29T13:17:58Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=161ebf9fcca967e7396bb076af5ed18539497a3f'/>
<id>urn:sha1:161ebf9fcca967e7396bb076af5ed18539497a3f</id>
<content type='text'>
Now we allocate a lock structure at first, then we request to the server
and save the lock if server returned OK though void function - it prevents
the situation when we locked a file on the server and then return -ENOMEM
from setlk.

Signed-off-by: Pavel Shilovsky &lt;piastry@etersoft.ru&gt;
Acked-by: Jeff Layton &lt;jlayton@samba.org&gt;
Signed-off-by: Steve French &lt;sfrench@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>CIFS: Fix the VFS brlock cache usage in posix locking case</title>
<updated>2011-10-30T03:03:14Z</updated>
<author>
<name>Pavel Shilovsky</name>
</author>
<published>2011-10-29T13:17:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5079276066cc421b48a6a63a54a34775979e8506'/>
<id>urn:sha1:5079276066cc421b48a6a63a54a34775979e8506</id>
<content type='text'>
Request to the cache in FL_POSIX case only.

Signed-off-by: Pavel Shilovsky &lt;piastry@etersoft.ru&gt;
Signed-off-by: Steve French &lt;smfrench@gmail.com&gt;
</content>
</entry>
<entry>
<title>CIFS: Remove extra mutex_unlock in cifs_lock_add_if</title>
<updated>2011-10-28T19:09:23Z</updated>
<author>
<name>Pavel Shilovsky</name>
</author>
<published>2011-10-26T19:41:04Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d12799b4c3c4d1e65d7fdbb5d91538c92d6863dd'/>
<id>urn:sha1:d12799b4c3c4d1e65d7fdbb5d91538c92d6863dd</id>
<content type='text'>
to prevent the mutex being unlocked twice if we interrupt a blocked lock.

Signed-off-by: Pavel Shilovsky &lt;piastry@etersoft.ru&gt;
Signed-off-by: Steve French &lt;smfrench@gmail.com&gt;
</content>
</entry>
<entry>
<title>CIFS: Make cifs_push_locks send as many locks at once as possible</title>
<updated>2011-10-24T18:11:55Z</updated>
<author>
<name>Pavel Shilovsky</name>
</author>
<published>2011-10-22T11:33:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=32b9aaf1a53b3c8d435f86339b01b3968520cb0a'/>
<id>urn:sha1:32b9aaf1a53b3c8d435f86339b01b3968520cb0a</id>
<content type='text'>
that reduces a traffic and increases a performance.

Signed-off-by: Pavel Shilovsky &lt;piastry@etersoft.ru&gt;
Acked-by: Jeff Layton &lt;jlayton@redhat.com&gt;
Signed-off-by: Steve French &lt;smfrench@gmail.com&gt;
</content>
</entry>
</feed>
