<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/fs/dlm, branch v3.1</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/fs/dlm?h=v3.1</id>
<link rel='self' href='https://git.amat.us/linux/atom/fs/dlm?h=v3.1'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2011-07-26T05:49:19Z</updated>
<entry>
<title>Merge branch 'for-3.1' of git://linux-nfs.org/~bfields/linux</title>
<updated>2011-07-26T05:49:19Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2011-07-26T05:49:19Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=2dad3206db5c3832cde1f58650027fea3ff7adf3'/>
<id>urn:sha1:2dad3206db5c3832cde1f58650027fea3ff7adf3</id>
<content type='text'>
* 'for-3.1' of git://linux-nfs.org/~bfields/linux:
  nfsd: don't break lease on CLAIM_DELEGATE_CUR
  locks: rename lock-manager ops
  nfsd4: update nfsv4.1 implementation notes
  nfsd: turn on reply cache for NFSv4
  nfsd4: call nfsd4_release_compoundargs from pc_release
  nfsd41: Deny new lock before RECLAIM_COMPLETE done
  fs: locks: remove init_once
  nfsd41: check the size of request
  nfsd41: error out when client sets maxreq_sz or maxresp_sz too small
  nfsd4: fix file leak on open_downgrade
  nfsd4: remember to put RW access on stateid destruction
  NFSD: Added TEST_STATEID operation
  NFSD: added FREE_STATEID operation
  svcrpc: fix list-corrupting race on nfsd shutdown
  rpc: allow autoloading of gss mechanisms
  svcauth_unix.c: quiet sparse noise
  svcsock.c: include sunrpc.h to quiet sparse noise
  nfsd: Remove deprecated nfsctl system call and related code.
  NFSD: allow OP_DESTROY_CLIENTID to be only op in COMPOUND

Fix up trivial conflicts in Documentation/feature-removal-schedule.txt
</content>
</entry>
<entry>
<title>locks: rename lock-manager ops</title>
<updated>2011-07-21T00:23:19Z</updated>
<author>
<name>J. Bruce Fields</name>
<email>bfields@redhat.com</email>
</author>
<published>2011-07-21T00:21:59Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8fb47a4fbf858a164e973b8ea8ef5e83e61f2e50'/>
<id>urn:sha1:8fb47a4fbf858a164e973b8ea8ef5e83e61f2e50</id>
<content type='text'>
Both the filesystem and the lock manager can associate operations with a
lock.  Confusingly, one of them (fl_release_private) actually has the
same name in both operation structures.

It would save some confusion to give the lock-manager ops different
names.

Signed-off-by: J. Bruce Fields &lt;bfields@redhat.com&gt;
</content>
</entry>
<entry>
<title>dlm: don't limit active work items</title>
<updated>2011-07-19T19:22:32Z</updated>
<author>
<name>David Teigland</name>
<email>teigland@redhat.com</email>
</author>
<published>2011-07-18T20:28:34Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=10d1459fafbb02a18e7bc8f2c384a9e973560b00'/>
<id>urn:sha1:10d1459fafbb02a18e7bc8f2c384a9e973560b00</id>
<content type='text'>
Allow multiple workqueue items (locks with callbacks) to be
processed concurrently.  There should be no reason not to
take advantage of this workqueue feature.

Signed-off-by: David Teigland &lt;teigland@redhat.com&gt;
</content>
</entry>
<entry>
<title>dlm: use workqueue for callbacks</title>
<updated>2011-07-15T17:30:43Z</updated>
<author>
<name>David Teigland</name>
<email>teigland@redhat.com</email>
</author>
<published>2011-04-05T18:16:24Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=23e8e1aaacb10d9f05e44a93e10ea4ee5b3838a5'/>
<id>urn:sha1:23e8e1aaacb10d9f05e44a93e10ea4ee5b3838a5</id>
<content type='text'>
Instead of creating our own kthread (dlm_astd) to deliver
callbacks for all lockspaces, use a per-lockspace workqueue
to deliver the callbacks.  This eliminates complications and
slowdowns from many lockspaces sharing the same thread.

Signed-off-by: David Teigland &lt;teigland@redhat.com&gt;
</content>
</entry>
<entry>
<title>dlm: remove deadlock debug print</title>
<updated>2011-07-14T17:31:49Z</updated>
<author>
<name>David Teigland</name>
<email>teigland@redhat.com</email>
</author>
<published>2011-07-14T17:31:49Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=883ba74f43092823d0ed4c6b21f0171e9b334607'/>
<id>urn:sha1:883ba74f43092823d0ed4c6b21f0171e9b334607</id>
<content type='text'>
gfs2 recently began using this feature heavily,
creating more debug output than we want to see.

Signed-off-by: David Teigland &lt;teigland@redhat.com&gt;
</content>
</entry>
<entry>
<title>dlm: improve rsb searches</title>
<updated>2011-07-12T21:02:09Z</updated>
<author>
<name>David Teigland</name>
<email>teigland@redhat.com</email>
</author>
<published>2011-07-07T19:05:03Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=3881ac04ebf94268ba3d6e486aa524fd41f893a9'/>
<id>urn:sha1:3881ac04ebf94268ba3d6e486aa524fd41f893a9</id>
<content type='text'>
By pre-allocating rsb structs before searching the hash
table, they can be inserted immediately.  This avoids
always having to repeat the search when adding the struct
to hash list.

This also adds space to the rsb struct for a max resource
name, so an rsb allocation can be used by any request.
The constant size also allows us to finally use a slab
for the rsb structs.

Signed-off-by: David Teigland &lt;teigland@redhat.com&gt;
</content>
</entry>
<entry>
<title>dlm: keep lkbs in idr</title>
<updated>2011-07-11T13:43:45Z</updated>
<author>
<name>David Teigland</name>
<email>teigland@redhat.com</email>
</author>
<published>2011-07-06T22:00:54Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=3d6aa675fff9eee5a6339d67b355b63a6d69565f'/>
<id>urn:sha1:3d6aa675fff9eee5a6339d67b355b63a6d69565f</id>
<content type='text'>
This is simpler and quicker than the hash table, and
avoids needing to search the hash list for every new
lkid to check if it's used.

Signed-off-by: David Teigland &lt;teigland@redhat.com&gt;
</content>
</entry>
<entry>
<title>dlm: fix kmalloc args</title>
<updated>2011-07-11T13:40:53Z</updated>
<author>
<name>David Teigland</name>
<email>teigland@redhat.com</email>
</author>
<published>2011-07-11T13:40:53Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a22ca4806822154c163c6f220f4c2a05adf96fc7'/>
<id>urn:sha1:a22ca4806822154c163c6f220f4c2a05adf96fc7</id>
<content type='text'>
The gfp and size args were switched.

Signed-off-by: David Teigland &lt;teigland@redhat.com&gt;
</content>
</entry>
<entry>
<title>dlm: don't do pointless NULL check, use kzalloc and fix order of arguments</title>
<updated>2011-07-11T13:39:42Z</updated>
<author>
<name>Jesper Juhl</name>
<email>jj@chaosbits.net</email>
</author>
<published>2011-07-10T20:54:31Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5d70828a7703b1f68e2fd4ce4b42b28d9623f52b'/>
<id>urn:sha1:5d70828a7703b1f68e2fd4ce4b42b28d9623f52b</id>
<content type='text'>
In fs/dlm/lock.c in the dlm_scan_waiters() function there are 3 small
issues:

1) There's no need to test the return value of the allocation and do a
memset if is succeedes. Just use kzalloc() to obtain zeroed memory.

2) Since kfree() handles NULL pointers gracefully, the test of
'warned' against NULL before the kfree() after the loop is completely
pointless. Remove it.

3) The arguments to kmalloc() (now kzalloc()) were swapped. Thanks to
Dr. David Alan Gilbert for pointing this out.

Signed-off-by: Jesper Juhl &lt;jj@chaosbits.net&gt;
Signed-off-by: David Teigland &lt;teigland@redhat.com&gt;
</content>
</entry>
<entry>
<title>dlm: dump address of unknown node</title>
<updated>2011-07-06T21:37:23Z</updated>
<author>
<name>Masatake YAMATO</name>
<email>yamato@redhat.com</email>
</author>
<published>2011-07-04T03:25:51Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=bcaadf5c1ac4ff84b52174a84adb86a1e3e806dd'/>
<id>urn:sha1:bcaadf5c1ac4ff84b52174a84adb86a1e3e806dd</id>
<content type='text'>
When the dlm fails to make a network connection to another
node, include the address of the node in the error message.

Signed-off-by: Masatake YAMATO &lt;yamato@redhat.com&gt;
Signed-off-by: David Teigland &lt;teigland@redhat.com&gt;
</content>
</entry>
</feed>
