linux.git/fs/ceph/caps.c, branch v3.17

ceph: replace comma with a semicolon

2014-07-24T08:04:46+00:00

Replace a comma between expression statements by a semicolon. This changes
the semantics of the code, but given the current indentation appears to be
what is intended.

A simplified version of the Coccinelle semantic patch that performs this
transformation is as follows:
// 
@r@
expression e1,e2;
@@

 e1
-,
+;
 e2;
// 

Signed-off-by: Himangi Saraogi 
Acked-by: Julia Lawall 
Signed-off-by: Ilya Dryomov

mds: check cap ID when handling cap export message

2014-06-06T01:29:55+00:00

handle following sequence of events:
- mds0 exports an inode to mds1. client receives the cap import
  message from mds1. caps from mds0 are removed while handling
  the cap import message.
- mds1 exports an inode to mds0. client receives the cap export
  message from mds1. handle_cap_export() adds placeholder caps
  for mds0
- client receives the first cap export message (for exporting
  inode from mds0 to mds1)

Signed-off-by: Yan, Zheng

ceph: handle cap import atomically

2014-06-06T01:29:53+00:00

cap import messages are processed by both handle_cap_import() and
handle_cap_grant(). These two functions are not executed in the same
atomic context, so they can races with cap release.

The fix is make handle_cap_import() not release the i_ceph_lock when
it returns. Let handle_cap_grant() release the lock after it finishes
its job.

Signed-off-by: Yan, Zheng

ceph: pre-allocate ceph_cap struct for ceph_add_cap()

2014-06-06T01:29:53+00:00

So that ceph_add_cap() can be used while i_ceph_lock is locked.
This simplifies the code that handle cap import/export.

Signed-off-by: Yan, Zheng

ceph: update inode fields according to issued caps

2014-06-06T01:29:52+00:00

Cap message and request reply from non-auth MDS may carry stale
information (corresponding locks are in LOCK states) even they
have the newest inode version. So client should update inode fields
according to issued caps.

Signed-off-by: Yan, Zheng

ceph: queue vmtruncate if necessary when handing cap grant/revoke

2014-06-06T01:29:51+00:00

cap grant/revoke message from non-auth MDS can update inode's size
and truncate_seq/truncate_size. (the message arrives before auth
MDS's cap trunc message)

Signed-off-by: Yan, Zheng

ceph: avoid releasing caps that are being used

2014-04-28T19:55:01+00:00

To avoid releasing caps that are being used, encode_inode_release()
should send implemented caps to MDS.

Signed-off-by: Yan, Zheng 
Reviewed-by: Sage Weil

ceph: set mds_wanted when MDS reply changes a cap to auth cap

2014-04-05T04:07:12+00:00

When adjusting caps client wants, MDS does not record caps that are
not allowed. For non-auth MDS, it does not record WR caps. So when
a MDS reply changes a non-auth cap to auth cap, client needs to set
cap's mds_wanted according to the reply.

Signed-off-by: Yan, Zheng

ceph: make sure write caps are registered with auth MDS

2014-04-05T04:07:05+00:00

Only auth MDS can issue write caps to clients, so don't consider
write caps registered with non-auth MDS as valid.

Signed-off-by: Yan, Zheng

ceph: add imported caps when handling cap export message

2014-01-21T08:30:31+00:00

Version 3 cap export message includes information about the imported
caps. It allows us to add the imported caps if the corresponding cap
import message still hasn't been received.

This allow us to handle situation that the importer MDS crashes and
the cap import message is missing.

Signed-off-by: Yan, Zheng