linux-toradex.git/fs/nfs/callback.h, branch v3.2.18

NFSv4.1: Fix the callback 'highest_used_slotid' behaviour

2011-08-04T15:55:35+00:00

Currently, there is no guarantee that we will call nfs4_cb_take_slot() even
though nfs4_callback_compound() will consistently call
nfs4_cb_free_slot() provided the cb_process_state has set the 'clp' field.
The result is that we can trigger the BUG_ON() upon the next call to
nfs4_cb_take_slot().

This patch fixes the above problem by using the slot id that was taken in
the CB_SEQUENCE operation as a flag for whether or not we need to call
nfs4_cb_free_slot().
It also fixes an atomicity problem: we need to set tbl->highest_used_slotid
atomically with the check for NFS4_SESSION_DRAINING, otherwise we end up
racing with the various tests in nfs4_begin_drain_session().

Cc: stable@kernel.org [2.6.38+]
Signed-off-by: Trond Myklebust

pnfs: CB_NOTIFY_DEVICEID

2011-05-29T17:52:31+00:00

Note: This functionlaity is incomplete as all layout segments referring to
the 'to be removed device id' need to be reaped, and all in flight I/O drained.

[use be32 res in nfs4_callback_devicenotify]
[use nfs_client to qualify deviceid for cb_notify_deviceid]
[use global deviceid cache for CB_NOTIFY_DEVICEID]
[refactor device cache _lookup_deviceid]
[refactor device cache _find_get_deviceid]
Signed-off-by: Benny Halevy 
[Bug in new global-device-cache code]
[layout_driver MUST set free_deviceid_node if using dev-cache]
Signed-off-by: Boaz Harrosh 
Signed-off-by: Benny Halevy

NFS do not find client in NFSv4 pg_authenticate

2011-01-25T20:26:51+00:00

The information required to find the nfs_client cooresponding to the incoming
back channel request is contained in the NFS layer. Perform minimal checking
in the RPC layer pg_authenticate method, and push more detailed checking into
the NFS layer where the nfs_client can be found.

Signed-off-by: Andy Adamson 
Signed-off-by: Trond Myklebust

pnfs: update nfs4_callback_recallany to handle layouts

2011-01-06T19:46:32+00:00

While here, update the code a bit.

Signed-off-by: Alexandros Batsakis 
Signed-off-by: Fred Isaman 
Signed-off-by: Trond Myklebust

pnfs: CB_LAYOUTRECALL xdr code

2011-01-06T19:46:32+00:00

This is the xdr decoding for CB_LAYOUTRECALL.

Signed-off-by: Alexandros Batsakis 
Signed-off-by: Dean Hildebrand 
Signed-off-by: Marc Eshel 
Signed-off-by: Andy Adamson 
Signed-off-by: Benny Halevy 
Signed-off-by: Fred Isaman 
Signed-off-by: Trond Myklebust

NFS add session back channel draining

2011-01-06T19:46:25+00:00

Currently session draining only drains the fore channel.
The back channel processing must also be drained.

Use the back channel highest_slot_used to indicate that a callback is being
processed by the callback thread.  Move the session complete to be per channel.

When the session is draininig, wait for any current back channel processing
to complete and stop all new back channel processing by returning NFS4ERR_DELAY
to the back channel client.

Drain the back channel, then the fore channel.

Signed-off-by: Andy Adamson 
Signed-off-by: Trond Myklebust

NFS refactor nfs_find_client and reference client across callback processing

2011-01-06T19:46:24+00:00

Fixes a bug where the nfs_client could be freed during callback processing.
Refactor nfs_find_client to use minorversion specific means to locate the
correct nfs_client structure.

In the NFS layer, V4.0 clients are found using the callback_ident field in the
CB_COMPOUND header.  V4.1 clients are found using the sessionID in the
CB_SEQUENCE operation which is also compared against the sessionID associated
with the back channel thread after a successful CREATE_SESSION.

Each of these methods finds the one an only nfs_client associated
with the incoming callback request - so nfs_find_client_next is not needed.

In the RPC layer, the pg_authenticate call needs to find the nfs_client. For
the v4.0 callback service, the callback identifier has not been decoded so a
search by address, version, and minorversion is used.  The sessionid for the
sessions based callback service has (usually) not been set for the
pg_authenticate on a CB_NULL call which can be sent prior to the return
of a CREATE_SESSION call, so the sessionid associated with the back channel
thread is not used to find the client in pg_authenticate for CB_NULL calls.

Pass the referenced nfs_client to each CB_COMPOUND operation being proceesed
via the new cb_process_state structure. The reference is held across
cb_compound processing.

Use the new cb_process_state struct to move the NFS4ERR_RETRY_UNCACHED_REP
processing from process_op into nfs4_callback_sequence where it belongs.

Signed-off-by: Andy Adamson 
Signed-off-by: Trond Myklebust

NFS associate sessionid with callback connection

2011-01-06T19:46:24+00:00

The sessions based callback service is started prior to the CREATE_SESSION call
so that it can handle CB_NULL requests which can be sent before the
CREATE_SESSION call returns and the session ID is known.

Set the callback sessionid after a sucessful CREATE_SESSION.

Signed-off-by: Andy Adamson 
Signed-off-by: Trond Myklebust

nfs41: implement cb_recall_slot

2010-02-10T13:30:59+00:00

Drain the fore channel and reset the max_slots to the new value.

Signed-off-by: Andy Adamson 
Signed-off-by: Trond Myklebust

nfs41: v2 fix cb_recall bug

2009-12-05T18:48:55+00:00

in NFSv4.1 the seqid part of a stateid in CB_RECALL must be 0

Signed-off-by: Alexandros Batsakis 
Signed-off-by: Trond Myklebust