From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/vhost/virtio Bug 1553] free called on rte_malloc block in vhost
Date: Wed, 25 Sep 2024 16:36:21 +0000 [thread overview]
Message-ID: <bug-1553-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1553
Bug ID: 1553
Summary: free called on rte_malloc block in vhost
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: vhost/virtio
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
If Gcc function attributes are added to rte_malloc, the compiler is able to
detect bugs where free is called on rte_malloc memory such as:
[2737/2957] Compiling C object
examples/dpdk-vhost_blk.p/vhost_blk_vhost_blk.c.o
In function ‘vhost_blk_bdev_construct’,
inlined from ‘vhost_blk_ctrlr_construct.constprop’ at
../examples/vhost_blk/vhost_blk.c:826:16:
../examples/vhost_blk/vhost_blk.c:779:17: warning: ‘free’ called on pointer
returned from a mismatched allocation function [-Wmismatched-dealloc]
779 | free(bdev);
| ^~~~~~~~~~
../examples/vhost_blk/vhost_blk.c:761:16: note: returned from ‘rte_zmalloc’
761 | bdev = rte_zmalloc(NULL, sizeof(*bdev), RTE_CACHE_LINE_SIZE);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3260 bytes --]
next reply other threads:[~2024-09-25 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 16:36 bugzilla [this message]
2024-10-16 20:45 ` [DPDK/vhost/virtio Bug 1553] free called on rte_malloc block in vhost bugzilla
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-1553-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.