From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Gagandeep Singh <g.singh@nxp.com>
Subject: |WARNING| pw110059 [PATCH 01/14] crypto/dpaa2_sec: fix fle buffer leak
Date: Fri, 22 Apr 2022 05:52:19 +0200 (CEST) [thread overview]
Message-ID: <20220422035219.3BCC8120DB4@dpdk.org> (raw)
In-Reply-To: <20220422035100.3180870-1-g.singh@nxp.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/110059
_coding style issues_
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#50:
Subject: [PATCH 01/14] crypto/dpaa2_sec: fix fle buffer leak
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#100:
Driver allocates a fle buffer for each packet
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#102:
there are enqueue failures, then code should free the fle buffers.
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#104:
Fixes: b15cbf5b2d88 ("crypto/dpaa2_sec: fix fle buffer leak")
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#130: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:68:
+free_fle(const struct qbman_fd *fd)
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#132: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:70:
+ struct qbman_fle *fle;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#132: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:70:
+ struct qbman_fle *fle;
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#140: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:78:
+ fle = (struct qbman_fle *)DPAA2_IOVA_TO_VADDR(DPAA2_GET_FD_ADDR(fd));
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#140: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:78:
+ fle = (struct qbman_fle *)DPAA2_IOVA_TO_VADDR(DPAA2_GET_FD_ADDR(fd));
WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#141: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:79:
+ op = (struct rte_crypto_op *)DPAA2_GET_FLE_ADDR((fle - 1));
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#141: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:79:
+ op = (struct rte_crypto_op *)DPAA2_GET_FLE_ADDR((fle - 1));
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#142: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:80:
+ /* free the fle memory */
WARNING:TYPO_SPELLING: 'FLE' may be misspelled - perhaps 'FILE'?
#144: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:82:
+ priv = (struct ctxt_priv *)(size_t)DPAA2_GET_FLE_CTXT(fle - 1);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#144: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:82:
+ priv = (struct ctxt_priv *)(size_t)DPAA2_GET_FLE_CTXT(fle - 1);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#145: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:83:
+ rte_mempool_put(priv->fle_pool, (void *)(fle-1));
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#145: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:83:
+ rte_mempool_put(priv->fle_pool, (void *)(fle-1));
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#147: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:85:
+ rte_free((void *)(fle-1));
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#158: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1538:
+ /* freeing the fle buffers */
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#160: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1540:
+ free_fle(&fd_arr[loop]);
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#171: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1885:
+ /* freeing the fle buffers */
WARNING:TYPO_SPELLING: 'fle' may be misspelled - perhaps 'file'?
#173: FILE: drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c:1887:
+ free_fle(&fd_arr[loop]);
total: 0 errors, 21 warnings, 59 lines checked
parent reply other threads:[~2022-04-22 3:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220422035100.3180870-1-g.singh@nxp.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220422035219.3BCC8120DB4@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=g.singh@nxp.com \
--cc=test-report@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).