CVS log for pvfs2/src/server/proto-error.sm
	Help

Request diff between arbitrary revisions / Display revisions graphically

Merged robust security code into Orange-Branch.

merge with Orange-Branch

merge with Orange-Branch

Namespace collision of ENCODING_DEFAULT with an in-tree kernel module in newer (circa 2.6.33) kernels, just a #define rename.

initial merge with Orange-Branch. much will be broken

merged in changes from summer at LANL

merge bugfix from head.

fix segv on proto mismatch.

merging hints/events code into trunk.

reverse merge from HEAD.

reverse merge from HEAD to directio branch

Fix bug in BMI reference counting.  Previously the server was responsible
for both incrementing and decrementing count while working on a state
machine, but this leaves a window of time between completion of
testunexpected() and the start of a state machine.  If a connection was
reset during this window it could cause state machine to try to use
non-existent BMI address, with some odd results.

This patch adds a flag that the server can use to have BMI automatically
increment reference count on any unexpected message before it is passed to
the server for processing.

Reverse merged and ported to HEAD.

state machine permission checking code cleanup

Updated security checking in state machines.  Added flags where needed.

modified permission checking to use callbacks instead of flags. added custom
checks to the io and small-io state machines.

hints and events.

Big pile-o' changes to make Pete go mad.

The main changes are the implementation of the stuffed create path (now just the create state machine and operation), and the beginnings of the "unstuff" operation.

This also includes the request scheduler and state machine cleanups (required for using prelude with batch_remove) and whatever else I may have happened to change along the way.

This code is able to create files, but writing to them is almost guaranteed to break.

Sam's prelude and scheduler updates

The normal path for a server request operation is to jump to the prelude state machine, which tries schedule the request based on the handle+fsid.  This meant that the request scheduler code had a switch/case returning the handle+fsid for each request we defined.  The function was also overloaded with a readonly parameter (whether the request modified any objects on the server), and a scheduling policy parameter (as the return code), which specified whether the request scheduling could be bypassed for this request.

I moved all that to a per-request parameter structure, that gets specified within the server state machine for the request.  Now there is one array of server requests (moved to pvfs2-server-req.c) which the request scheduler and prelude state machine can poke at to get parameters (defined in the state machine for that request), and based decisions on.

The patch includes some other minor changes:

* A fix to the BMI addr ref count increment/decrement.  Previously, the addr ref count was being incremented/decremented in the prelude/final-response state machines.  That requires that those state machines get invoked, which I don't want to have to depend on.  I've moved the INC call to the unexpected_sm, and the DEC call to where the state machine gets finished in the server.  That way we don't have to worry about whether we're using prelude/final-response.

* Cleanup of the request scheduler.  The way we were changing the mode from normal to admin was sort of embedded into the request scheduling code, so we had to hack the mode change from prelude_sm instead of in setparam.  Also, the request scheduler had to be aware of the setparam fields in the request.  I've moved the mode change code to separate request scheduler and job calls.  I think something similar could be done for the timer code (it doesn't really belong in the request scheduler), but I'll leave that for another patch.

* Changed the way we compile the server binary in Makefile.in to allow for multiple object files.

minor change allows state actions to not be declared at the top of *.sm files.

Merge HEAD changes to TAS-branch.

merge of the WALT3 branch to HEAD.  This patch changes the way state actions
are represented as C structures (what statecomp generates).  It also changes
the main state action parameter from a s_op on the server or an sm_p on the client
to a unified smcb pointer (state machine control block) for all state actions (both client and server).  Finally, initial support for concurrent state machines has
been added to allow state actions to be invoked concurrently .. a first step for
server-to-server.

walt3 reverse merge from head includes merges of pw's sm changes (no state declarations), cleanup of state machine code, and other general merging/fixes.

update to current CVS version because statecomp modifications are neat for my work, thanks!

Remove forward declarations of states.

add hints to job layer

Simple pint/ls/cp/diff test works

Everything compiles.   Crap!  Now I have to see if it runs!!!

removing compile errors

correcting compile errors

updated to support SM control block interface

Reverse merge from trunk to lockd-branch...

reverse merge of branch

merge sync coalescing branch.

fix deadlock bugs in coalescing code.  add proper state machine debugging.

updates to my event changes to bring them inline with trunk

merge changes from trunk since branch point into branch.  Effectively moves the branchpoint to the latest trunk.

[pcarns]: do a couple things here:
- implements the retry and timeout configuration file options
( http://www.beowulf-underground.org/pipermail/pvfs2-developers/2005-June/001287.html )

- It turns out that it wasn't necessary for clients to choose a value if
  multiple file systems disagree on timeouts.  Instead they just store
  independent settings for each FS.

- This patch adds --client-job-timeout and --server-job-timeout options to
  genconfig (each toggle both flow and bmi timeouts)

- A few operations were multiplying the default client timeout by 5 on the
  premise that those particular operations may take a while.  I removed those
  special cases and instead increased the default client timeout values for
  everything.  My reasoning is that if any one operation can take a long time,
  then by extension any other operation could take an equally long time because
  of queueing behind the slow ones.

* added event logging for states
* moved state debug code to state-machine so all state start/end
points get debug messages automatically
* added textlog stuff.  This allows us to write the default event
queue out to a text file that can be converted to slog2 later.

- applied Nathan's expandtab patch (expandtab-2.patch.gz)

  first referenced at:
  http://www.beowulf-underground.org/pipermail/pvfs2-developers/2004-July/000745.html

add a mechanism for a server to send a generic response back to the client
when it receives a request with a bad version number or encoding type, so
that the user gets a clear error message at the application level too