BMC/Intel-BMC/linux.git/fs/ceph/mds_client.c, branch dev

ceph: switch some GFP_NOFS memory allocation to GFP_KERNEL

2015-06-25T08:49:31+00:00

GFP_NOFS memory allocation is required for page writeback path. But there is no need to use GFP_NOFS in syscall path and readpage path Signed-off-by: Yan, Zheng

ceph: pre-allocate data structure that tracks caps flushing

2015-06-25T08:49:31+00:00

Signed-off-by: Yan, Zheng

ceph: re-send flushing caps (which are revoked) in reconnect stage

2015-06-25T08:49:31+00:00

if flushing caps were revoked, we should re-send the cap flush in client reconnect stage. This guarantees that MDS processes the cap flush message before issuing the flushing caps to other client. Signed-off-by: Yan, Zheng

ceph: track pending caps flushing globally

2015-06-25T08:49:31+00:00

So we know TID of the oldest pending caps flushing. Later patch will send this information to MDS, so that MDS can trim its completed caps flush list. Tracking pending caps flushing globally also simplifies syncfs code. Signed-off-by: Yan, Zheng

ceph: track pending caps flushing accurately

2015-06-25T08:49:30+00:00

Previously we do not trace accurate TID for flushing caps. when MDS failovers, we have no choice but to re-send all flushing caps with a new TID. This can cause problem because MDS can has already flushed some caps and has issued the same caps to other client. The re-sent cap flush has a new TID, which makes MDS unable to detect if it has already processed the cap flush. This patch adds code to track pending caps flushing accurately. When re-sending cap flush is needed, we use its original flush TID. Signed-off-by: Yan, Zheng

ceph: ratelimit warn messages for MDS closes session

2015-06-25T08:49:30+00:00

Signed-off-by: Yan, Zheng

ceph: simplify two mount_timeout sites

2015-06-25T08:49:29+00:00

No need to bifurcate wait now that we've got ceph_timeout_jiffies(). Signed-off-by: Ilya Dryomov Reviewed-by: Alex Elder Reviewed-by: Yan, Zheng

libceph: store timeouts in jiffies, verify user input

2015-06-25T08:49:29+00:00

There are currently three libceph-level timeouts that the user can specify on mount: mount_timeout, osd_idle_ttl and osdkeepalive. All of these are in seconds and no checking is done on user input: negative values are accepted, we multiply them all by HZ which may or may not overflow, arbitrarily large jiffies then get added together, etc. There is also a bug in the way mount_timeout=0 is handled. It's supposed to mean "infinite timeout", but that's not how wait.h APIs treat it and so __ceph_open_session() for example will busy loop without much chance of being interrupted if none of ceph-mons are there. Fix all this by verifying user input, storing timeouts capped by msecs_to_jiffies() in jiffies and using the new ceph_timeout_jiffies() helper for all user-specified waits to handle infinite timeouts correctly. Signed-off-by: Ilya Dryomov Reviewed-by: Alex Elder

ceph: exclude setfilelock requests when calculating oldest tid

2015-06-25T08:49:29+00:00

setfilelock requests can block for a long time, which can prevent client from advancing its oldest tid. Signed-off-by: Yan, Zheng

ceph: don't pre-allocate space for cap release messages

2015-06-25T08:49:29+00:00

Previously we pre-allocate cap release messages for each caps. This wastes lots of memory when there are large amount of caps. This patch make the code not pre-allocate the cap release messages. Instead, we add the corresponding ceph_cap struct to a list when releasing a cap. Later when flush cap releases is needed, we allocate the cap release messages dynamically. Signed-off-by: Yan, Zheng