mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git
synced 2026-04-05 00:08:32 -04:00
crypto: qat - fix warning on adf_pfvf_pf_proto.c
Building the QAT driver with -Wmaybe-uninitialized triggers warnings in
qat_common/adf_pfvf_pf_proto.c. Specifically, the variables blk_type,
blk_byte, and byte_max may be used uninitialized in handle_blkmsg_req():
make M=drivers/crypto/intel/qat W=1 C=2 "KCFLAGS=-Werror" \
KBUILD_CFLAGS_KERNEL=-Wmaybe-uninitialized \
CFLAGS_MODULE=-Wmaybe-uninitialized
...
warning: ‘byte_max’ may be used uninitialized [-Wmaybe-uninitialized]
warning: ‘blk_type’ may be used uninitialized [-Wmaybe-uninitialized]
warning: ‘blk_byte’ may be used uninitialized [-Wmaybe-uninitialized]
Although the caller of handle_blkmsg_req() always provides a req.type
that is handled by the switch, the compiler cannot guarantee this.
Add a default case to the switch statement to handle an invalid req.type.
Fixes: 673184a2a5 ("crypto: qat - introduce support for PFVF block messages")
Signed-off-by: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
Reviewed-by: Ahsan Atta <ahsan.atta@intel.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
This commit is contained in:
committed by
Herbert Xu
parent
90ca8d3596
commit
994689b8f9
@@ -148,6 +148,16 @@ static struct pfvf_message handle_blkmsg_req(struct adf_accel_vf_info *vf_info,
|
||||
blk_byte = FIELD_GET(ADF_VF2PF_SMALL_BLOCK_BYTE_MASK, req.data);
|
||||
byte_max = ADF_VF2PF_SMALL_BLOCK_BYTE_MAX;
|
||||
break;
|
||||
default:
|
||||
dev_err(&GET_DEV(vf_info->accel_dev),
|
||||
"Invalid BlockMsg type 0x%.4x received from VF%u\n",
|
||||
req.type, vf_info->vf_nr);
|
||||
resp.type = ADF_PF2VF_MSGTYPE_BLKMSG_RESP;
|
||||
resp.data = FIELD_PREP(ADF_PF2VF_BLKMSG_RESP_TYPE_MASK,
|
||||
ADF_PF2VF_BLKMSG_RESP_TYPE_ERROR) |
|
||||
FIELD_PREP(ADF_PF2VF_BLKMSG_RESP_DATA_MASK,
|
||||
ADF_PF2VF_UNSPECIFIED_ERROR);
|
||||
return resp;
|
||||
}
|
||||
|
||||
/* Is this a request for CRC or data? */
|
||||
|
||||
Reference in New Issue
Block a user