DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 111] There maybe some risks to printf the addr of the map page
Date: Tue, 27 Nov 2018 12:35:24 +0000	[thread overview]
Message-ID: <bug-111-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=111

            Bug ID: 111
           Summary: There maybe some risks to printf  the addr of the map
                    page
           Product: DPDK
           Version: 17.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: andy01011501@163.com
  Target Milestone: ---

In the funtion pci_unmap_resource,the requested_addr will be print and this may
cause some risks like the code below:

void pci_unmap_resource(void *requested_addr, size_t size)
{
        if (requested_addr == NULL)
                return;

        /* Unmap the PCI memory resource of device */
        if (munmap(requested_addr, size)) {
                RTE_LOG(ERR, EAL, "%s(): cannot munmap(%p, 0x%lx): %s\n",
                        __func__, requested_addr, (unsigned long)size,
                        strerror(errno));
        } else
                RTE_LOG(DEBUG, EAL, "  PCI memory unmapped at %p\n",
                                requested_addr);
}

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2018-11-27 12:35 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-111-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).