automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: longli@linuxonhyperv.com
Subject: |WARNING| pw113613 [PATCH 10/17] net/mana: implement memory registration
Date: Fri,  1 Jul 2022 11:05:59 +0200 (CEST)	[thread overview]
Message-ID: <20220701090559.1D811120787@dpdk.org> (raw)
In-Reply-To: <1656666167-26035-11-git-send-email-longli@linuxonhyperv.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/113613

_coding style issues_


WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#55: 
MANA hardware has iommu built-in, that provides hardware safe access to user

WARNING:TYPO_SPELLING: 'registartion' may be misspelled - perhaps 'registration'?
#57: 
expensive operation, this patch implements a two level memory registartion

WARNING:VSPRINTF_SPECIFIER_PX: Using vsprintf specifier '%px' potentially exposes the kernel memory layout, if you don't really need the address please consider using '%p'.
#246: FILE: drivers/net/mana/mp.c:50:
+	DRV_LOG(DEBUG, "MR (2nd) lkey %u addr %px len 0x%lx",
+		ibv_mr->lkey, ibv_mr->addr, ibv_mr->length);

WARNING:VSPRINTF_SPECIFIER_PX: Using vsprintf specifier '%px' potentially exposes the kernel memory layout, if you don't really need the address please consider using '%p'.
#430: FILE: drivers/net/mana/mr.c:90:
+			DRV_LOG(DEBUG, "MR lkey %u addr %px len 0x%lx",
+				ibv_mr->lkey, ibv_mr->addr, ibv_mr->length);

total: 0 errors, 4 warnings, 0 checks, 573 lines checked
Warning in drivers/net/mana/mp.c:
Using %l format, prefer %PRI*64 if type is [u]int64_t

           reply	other threads:[~2022-07-01  9:06 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1656666167-26035-11-git-send-email-longli@linuxonhyperv.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=20220701090559.1D811120787@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=longli@linuxonhyperv.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).