From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/cryptodev Bug 1552] free miss match in cryptodev
Date: Wed, 25 Sep 2024 16:34:33 +0000 [thread overview]
Message-ID: <bug-1552-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 2028 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1552
Bug ID: 1552
Summary: free miss match in cryptodev
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: cryptodev
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
If GCC function attributes are added to rte_malloc, then Gcc is able to
identify rte_malloc to free mismatches like:
[1319/2957] Compiling C object
drivers/libtmp_rte_crypto_bcmfs.a.p/crypto_bcmfs_bcmfs_device.c.o
In function ‘fsdev_allocate_one_dev’,
inlined from ‘bcmfs_vdev_probe’ at
../drivers/crypto/bcmfs/bcmfs_device.c:283:11:
../drivers/crypto/bcmfs/bcmfs_device.c:142:9: warning: ‘free’ called on pointer
returned from a mismatched allocation function [-Wmismatched-dealloc]
142 | free(fsdev);
| ^~~~~~~~~~~
../drivers/crypto/bcmfs/bcmfs_device.c:102:17: note: returned from ‘rte_calloc’
102 | fsdev = rte_calloc(__func__, 1, sizeof(*fsdev), 0);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In function ‘fsdev_release’,
inlined from ‘bcmfs_vdev_probe’ at
../drivers/crypto/bcmfs/bcmfs_device.c:308:2:
../drivers/crypto/bcmfs/bcmfs_device.c:166:9: warning: ‘free’ called on pointer
returned from a mismatched allocation function [-Wmismatched-dealloc]
166 | free(fsdev);
| ^~~~~~~~~~~
In function ‘fsdev_allocate_one_dev’,
inlined from ‘bcmfs_vdev_probe’ at
../drivers/crypto/bcmfs/bcmfs_device.c:283:11:
../drivers/crypto/bcmfs/bcmfs_device.c:102:17: note: returned from ‘rte_calloc’
102 | fsdev = rte_calloc(__func__, 1, sizeof(*fsdev), 0);
|
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3884 bytes --]
reply other threads:[~2024-09-25 16:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-1552-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).