protocol/rpc: move latest added procedures to the end of the array
While looking at the newly introduced procedures FALLOCATE and DISCARD, it seems that these were added with already existing procedure numbers. This makes the protocol incompatible with existing roll-outs. It is very confusing when new procedures are added somewhere in the middle of the array. This will cause the number of existing procedures to change. It is much preferred to add new procedures at the end of the array. This changes not only corrects the enum that generates the procedure numbers, but also the ordering in the client and server fops-array for clarity. Correcting this greatly simplifies adding support for these new procedures in Wireshark and will prevent confusion to the people reading network traces (with or without Wireshark). Change-Id: Ib9e7978531d016c7230d756b855cb94cb0793b0f BUG: 974976 Signed-off-by: Niels de Vos <ndevos@redhat.com> Reviewed-on: http://review.gluster.org/5215 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Brian Foster <bfoster@redhat.com> Reviewed-by: Anand Avati <avati@redhat.com>
This commit is contained in:
parent
74fe305727
commit
eb6b81e1fc
@ -53,11 +53,11 @@ enum gf_fop_procnum {
|
||||
GFS3_OP_SETATTR,
|
||||
GFS3_OP_FSETATTR,
|
||||
GFS3_OP_READDIRP,
|
||||
GFS3_OP_FALLOCATE,
|
||||
GFS3_OP_DISCARD,
|
||||
GFS3_OP_RELEASE,
|
||||
GFS3_OP_RELEASEDIR,
|
||||
GFS3_OP_FREMOVEXATTR,
|
||||
GFS3_OP_FALLOCATE,
|
||||
GFS3_OP_DISCARD,
|
||||
GFS3_OP_MAXVALUE,
|
||||
} ;
|
||||
|
||||
|
@ -6083,11 +6083,11 @@ char *clnt3_3_fop_names[GFS3_OP_MAXVALUE] = {
|
||||
[GFS3_OP_SETATTR] = "SETATTR",
|
||||
[GFS3_OP_FSETATTR] = "FSETATTR",
|
||||
[GFS3_OP_READDIRP] = "READDIRP",
|
||||
[GFS3_OP_FALLOCATE] = "FALLOCATE",
|
||||
[GFS3_OP_DISCARD] = "DISCARD",
|
||||
[GFS3_OP_RELEASE] = "RELEASE",
|
||||
[GFS3_OP_RELEASEDIR] = "RELEASEDIR",
|
||||
[GFS3_OP_FREMOVEXATTR] = "FREMOVEXATTR",
|
||||
[GFS3_OP_FALLOCATE] = "FALLOCATE",
|
||||
[GFS3_OP_DISCARD] = "DISCARD",
|
||||
};
|
||||
|
||||
rpc_clnt_prog_t clnt3_3_fop_prog = {
|
||||
|
@ -5987,11 +5987,11 @@ rpcsvc_actor_t glusterfs3_3_fop_actors[] = {
|
||||
[GFS3_OP_SETATTR] = { "SETATTR", GFS3_OP_SETATTR, server3_3_setattr, NULL, 0},
|
||||
[GFS3_OP_FSETATTR] = { "FSETATTR", GFS3_OP_FSETATTR, server3_3_fsetattr, NULL, 0},
|
||||
[GFS3_OP_READDIRP] = { "READDIRP", GFS3_OP_READDIRP, server3_3_readdirp, NULL, 0},
|
||||
[GFS3_OP_FALLOCATE] = { "FALLOCATE", GFS3_OP_FALLOCATE, server3_3_fallocate, NULL, 0},
|
||||
[GFS3_OP_DISCARD] = { "DISCARD", GFS3_OP_DISCARD, server3_3_discard, NULL, 0},
|
||||
[GFS3_OP_RELEASE] = { "RELEASE", GFS3_OP_RELEASE, server3_3_release, NULL, 0},
|
||||
[GFS3_OP_RELEASEDIR] = { "RELEASEDIR", GFS3_OP_RELEASEDIR, server3_3_releasedir, NULL, 0},
|
||||
[GFS3_OP_FREMOVEXATTR] = { "FREMOVEXATTR", GFS3_OP_FREMOVEXATTR, server3_3_fremovexattr, NULL, 0},
|
||||
[GFS3_OP_FALLOCATE] = { "FALLOCATE", GFS3_OP_FALLOCATE, server3_3_fallocate, NULL, 0},
|
||||
[GFS3_OP_DISCARD] = { "DISCARD", GFS3_OP_DISCARD, server3_3_discard, NULL, 0},
|
||||
};
|
||||
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user