wang di 3b2f75fd59 staging/lustre/ost: check pre 2.4 echo client in obdo validation ... Because old echo client still uses o_id/o_seq for objid, but new echo client will uses FID for the objid. Add OBD_CONNECT_FID for 2.4 echo client, so 2.4 OST will convert o_id/o_seq to FID if the request from old echo client. Add local flag OBD_FL_OSTID for o_flags to indicate OST does not support FID yet, then echo client will still send o_id/o_seq to OST. cleanup ost_validate_obdo [picked client part for upstream kernel submission] Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-3187 Lustre-change: http://review.whamcloud.com/6287 Signed-off-by: wang di <di.wang@intel.com> Reviewed-by: Andreas Dilger <andreas.dilger@intel.com> Reviewed-by: Mike Pershin <mike.pershin@intel.com> Signed-off-by: Peng Tao <tao.peng@emc.com> Signed-off-by: Andreas Dilger <andreas.dilger@intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2013-06-03 11:26:36 -07:00
..
include/linux	staging/lustre: adapt proc_dir_entry change	2013-05-30 20:49:44 +09:00
lnet
lustre	staging/lustre/ost: check pre 2.4 echo client in obdo validation	2013-06-03 11:26:36 -07:00
Kconfig
Makefile
TODO