SUNRPC: gss_alloc_msg - choose _either_ a v0 message or a v1 message
Add the missing 'break' to ensure that we don't corrupt a legacy 'v0' type message by appending the 'v1'. Cc: Bruce Fields <bfields@fieldses.org> Cc: stable@vger.kernel.org Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
This commit is contained in:
parent
8313164c36
commit
5fccc5b52e
|
@ -482,6 +482,7 @@ gss_alloc_msg(struct gss_auth *gss_auth,
|
||||||
switch (vers) {
|
switch (vers) {
|
||||||
case 0:
|
case 0:
|
||||||
gss_encode_v0_msg(gss_msg);
|
gss_encode_v0_msg(gss_msg);
|
||||||
|
break;
|
||||||
default:
|
default:
|
||||||
gss_encode_v1_msg(gss_msg, service_name, gss_auth->target_name);
|
gss_encode_v1_msg(gss_msg, service_name, gss_auth->target_name);
|
||||||
};
|
};
|
||||||
|
|
Loading…
Reference in a new issue