<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/linux.git/include/trace/events/filelock.h, branch v4.4.151</title>
<subtitle>Linux kernel stable tree (mirror)</subtitle>
<id>https://git.radix-linux.su/kernel/linux.git/atom?h=v4.4.151</id>
<link rel='self' href='https://git.radix-linux.su/kernel/linux.git/atom?h=v4.4.151'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/'/>
<updated>2015-09-21T11:26:45+00:00</updated>
<entry>
<title>locks: change tracepoint for generic_add_lease</title>
<updated>2015-09-21T11:26:45+00:00</updated>
<author>
<name>Jeff Layton</name>
<email>jeff.layton@primarydata.com</email>
</author>
<published>2015-09-21T11:26:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=d11797a0a7acc1fe6a51b1605e166adad04da29b'/>
<id>urn:sha1:d11797a0a7acc1fe6a51b1605e166adad04da29b</id>
<content type='text'>
Add some more helpful info to make it easier to determine why a lease
wasn't granted.

Signed-off-by: Jeff Layton &lt;jeff.layton@primarydata.com&gt;
</content>
</entry>
<entry>
<title>locks: generic_delete_lease doesn't need a file_lock at all</title>
<updated>2014-10-07T18:06:12+00:00</updated>
<author>
<name>Jeff Layton</name>
<email>jlayton@primarydata.com</email>
</author>
<published>2014-08-22T14:18:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=0efaa7e82f02fe69c05ad28e905f31fc86e6f08e'/>
<id>urn:sha1:0efaa7e82f02fe69c05ad28e905f31fc86e6f08e</id>
<content type='text'>
Ensure that it's OK to pass in a NULL file_lock double pointer on
a F_UNLCK request and convert the vfs_setlease F_UNLCK callers to
do just that.

Finally, turn the BUG_ON in generic_setlease into a WARN_ON_ONCE
with an error return. That's a problem we can handle without
crashing the box if it occurs.

Signed-off-by: Jeff Layton &lt;jlayton@primarydata.com&gt;
Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;
</content>
</entry>
<entry>
<title>locks: add some tracepoints in the lease handling code</title>
<updated>2014-06-02T12:09:30+00:00</updated>
<author>
<name>Jeff Layton</name>
<email>jlayton@poochiereds.net</email>
</author>
<published>2014-05-09T18:13:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=62af4f1f7df44ea0bb1a11c94ac9fb384bf1c564'/>
<id>urn:sha1:62af4f1f7df44ea0bb1a11c94ac9fb384bf1c564</id>
<content type='text'>
v2: add a __break_lease tracepoint for non-blocking case

Recently, I needed these to help track down a softlockup when recalling a
delegation, but they might be helpful in other situations as well.

Cc: "J. Bruce Fields" &lt;bfields@fieldses.org&gt;
Signed-off-by: Jeff Layton &lt;jlayton@poochiereds.net&gt;
</content>
</entry>
</feed>
