<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/fs/dlm, branch v3.13.1</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/fs/dlm?h=v3.13.1</id>
<link rel='self' href='https://git.amat.us/linux/atom/fs/dlm?h=v3.13.1'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2013-11-19T21:39:05Z</updated>
<entry>
<title>genetlink: only pass array to genl_register_family_with_ops()</title>
<updated>2013-11-19T21:39:05Z</updated>
<author>
<name>Johannes Berg</name>
<email>johannes.berg@intel.com</email>
</author>
<published>2013-11-19T14:19:31Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c53ed7423619b4e8108914a9f31b426dd58ad591'/>
<id>urn:sha1:c53ed7423619b4e8108914a9f31b426dd58ad591</id>
<content type='text'>
As suggested by David Miller, make genl_register_family_with_ops()
a macro and pass only the array, evaluating ARRAY_SIZE() in the
macro, this is a little safer.

The openvswitch has some indirection, assing ops/n_ops directly in
that code. This might ultimately just assign the pointers in the
family initializations, saving the struct genl_family_and_ops and
code (once mcast groups are handled differently.)

Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>dlm: Avoid that dlm_release_lockspace() incorrectly returns -EBUSY</title>
<updated>2013-10-16T15:32:42Z</updated>
<author>
<name>Bart Van Assche</name>
<email>bvanassche@acm.org</email>
</author>
<published>2013-10-16T12:20:25Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a97f4a66d8ee4faf0f31cc4ad3f4aa0baef23fc7'/>
<id>urn:sha1:a97f4a66d8ee4faf0f31cc4ad3f4aa0baef23fc7</id>
<content type='text'>
When dlm_release_lockspace(ls, 1) is invoked on a busy system
immediately after the last dlm_unlock() AST has finished it can occur
that lkb_idr_is_local() is invoked for the unlocked LKB since removal
from ls_lkbidr only occurs after the AST has returned. If that happens
dlm_release_lockspace(ls, 1) will return -EBUSY instead of releasing
the lockspace. Fix this race condition by changing lkb_idr_is_local()
such that it only returns true for LKB's that have not yet been
unlocked.

Signed-off-by: Bart Van Assche &lt;bvanassche@acm.org&gt;
Signed-off-by: David Teigland &lt;teigland@redhat.com&gt;
</content>
</entry>
<entry>
<title>dlm: remove signal blocking</title>
<updated>2013-08-12T20:22:43Z</updated>
<author>
<name>David Teigland</name>
<email>teigland@redhat.com</email>
</author>
<published>2013-08-12T20:22:43Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c6ca7bc91d51582ff9e8ab29f675dbc3c40f5742'/>
<id>urn:sha1:c6ca7bc91d51582ff9e8ab29f675dbc3c40f5742</id>
<content type='text'>
The signal blocking was incorrect and unnecessary
so just remove it.

Signed-off-by: David Teigland &lt;teigland@redhat.com&gt;
</content>
</entry>
<entry>
<title>dlm: WQ_NON_REENTRANT is meaningless and going away</title>
<updated>2013-07-30T14:24:24Z</updated>
<author>
<name>Tejun Heo</name>
<email>tj@kernel.org</email>
</author>
<published>2013-07-30T12:40:24Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ededf305a8d843c12038ae48eb68529016b3e91f'/>
<id>urn:sha1:ededf305a8d843c12038ae48eb68529016b3e91f</id>
<content type='text'>
dbf2576e37 ("workqueue: make all workqueues non-reentrant") made
WQ_NON_REENTRANT no-op and the flag is going away.  Remove its usages.

This patch doesn't introduce any behavior changes.

Signed-off-by: Tejun Heo &lt;tj@kernel.org&gt;
Signed-off-by: David Teigland &lt;teigland@redhat.com&gt;
</content>
</entry>
<entry>
<title>dlm: Avoid LVB truncation</title>
<updated>2013-06-26T16:38:02Z</updated>
<author>
<name>Bart Van Assche</name>
<email>bvanassche@acm.org</email>
</author>
<published>2013-06-26T12:27:57Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=cfa805f6f19639b37ee877085770a396b70f2da1'/>
<id>urn:sha1:cfa805f6f19639b37ee877085770a396b70f2da1</id>
<content type='text'>
For lockspaces with an LVB length above 64 bytes, avoid truncating
the LVB while exchanging it with another node in the cluster.

Signed-off-by: Bart Van Assche &lt;bvanassche@acm.org&gt;
Signed-off-by: David Teigland &lt;teigland@redhat.com&gt;
</content>
</entry>
<entry>
<title>dlm: log an error for unmanaged lockspaces</title>
<updated>2013-06-25T17:53:20Z</updated>
<author>
<name>David Teigland</name>
<email>teigland@redhat.com</email>
</author>
<published>2013-06-25T17:48:01Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=696b3d84605e5546cbddefdc95b9099f908fd56e'/>
<id>urn:sha1:696b3d84605e5546cbddefdc95b9099f908fd56e</id>
<content type='text'>
Log an error message if the dlm user daemon exits
before all the lockspaces have been removed.

Signed-off-by: David Teigland &lt;teigland@redhat.com&gt;
</content>
</entry>
<entry>
<title>dlm: config: using strlcpy instead of strncpy</title>
<updated>2013-06-25T17:53:06Z</updated>
<author>
<name>Zhao Hongjiang</name>
<email>zhaohongjiang@huawei.com</email>
</author>
<published>2013-06-20T10:59:51Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ad917e7f821855a2f223131bb6c90ca6c9240bf3'/>
<id>urn:sha1:ad917e7f821855a2f223131bb6c90ca6c9240bf3</id>
<content type='text'>
for NUL terminated string, need alway set '\0' in the end.

Signed-off-by: Zhao Hongjiang &lt;zhaohongjiang@huawei.com&gt;
Signed-off-by: David Teigland &lt;teigland@redhat.com&gt;
</content>
</entry>
<entry>
<title>dlm: remove duplicated include from lowcomms.c</title>
<updated>2013-06-19T14:52:09Z</updated>
<author>
<name>Wei Yongjun</name>
<email>yongjun_wei@trendmicro.com.cn</email>
</author>
<published>2013-06-19T02:49:50Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=06452eb0538827d2158945d20e3d33e359884437'/>
<id>urn:sha1:06452eb0538827d2158945d20e3d33e359884437</id>
<content type='text'>
Remove duplicated include.

Signed-off-by: Wei Yongjun &lt;yongjun_wei@trendmicro.com.cn&gt;
Signed-off-by: David Teigland &lt;teigland@redhat.com&gt;
</content>
</entry>
<entry>
<title>dlm: disable nagle for SCTP</title>
<updated>2013-06-14T18:07:11Z</updated>
<author>
<name>Mike Christie</name>
<email>michaelc@cs.wisc.edu</email>
</author>
<published>2013-06-14T09:56:14Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=86e92ad299fb0be359efdd61812944497d4d8d52'/>
<id>urn:sha1:86e92ad299fb0be359efdd61812944497d4d8d52</id>
<content type='text'>
For TCP we disable Nagle and I cannot think of why it would be needed
for SCTP. When disabled it seems to improve dlm_lock operations like it
does for TCP.

Signed-off-by: Mike Christie &lt;michaelc@cs.wisc.edu&gt;
Signed-off-by: David Teigland &lt;teigland@redhat.com&gt;
</content>
</entry>
<entry>
<title>dlm: retry failed SCTP sends</title>
<updated>2013-06-14T18:07:11Z</updated>
<author>
<name>Mike Christie</name>
<email>michaelc@cs.wisc.edu</email>
</author>
<published>2013-06-14T09:56:13Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5d6898714fe2ce485e95ac74479ed40ebd8d5748'/>
<id>urn:sha1:5d6898714fe2ce485e95ac74479ed40ebd8d5748</id>
<content type='text'>
Currently if a SCTP send fails, we lose the data we were trying
to send because the writequeue_entry is released when we do the send.
When this happens other nodes will then hang waiting for a reply.

This adds support for SCTP to retry the send operation.

I also removed the retry limit for SCTP use, because we want
to make sure we try every path during init time and for longer
failures we want to continually retry in case paths come back up
while trying other paths. We will do this until userspace tells us
to stop.

Signed-off-by: Mike Christie &lt;michaelc@cs.wisc.edu&gt;
Signed-off-by: David Teigland &lt;teigland@redhat.com&gt;
</content>
</entry>
</feed>
