DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH] devtools: suppress checkpatch warning on some kernel macro
Date: Tue, 4 Apr 2023 15:18:36 +0200	[thread overview]
Message-ID: <CAJFAV8w4Y-wfPUS3MXs4NTsxRrZgFwuLmGvjv+dmJf_UaV3OdQ@mail.gmail.com> (raw)
In-Reply-To: <fe7799c6-2953-9fe8-63ca-92bcdf977191@amd.com>

On Tue, Apr 4, 2023 at 3:01 PM Ferruh Yigit <ferruh.yigit@amd.com> wrote:
>
> On 4/4/2023 1:36 PM, David Marchand wrote:
> > Kernel checkpatch.pl is confused about RTE_BUILD_BUG_ON() and warns as if
> > our code was calling the kernel macro BUG_ON().
> >
> > This does not make sense in the DPDK userspace code and the Linux kernel
> > module hosted in our repository (kernel/linux/kni) won't make it upstream.
> >
> > Disable this warning.
> >
> > Signed-off-by: David Marchand <david.marchand@redhat.com>
>
> Sounds reasonable,
> Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
>
>
> Is there any occurrence in the public CI, as reference?

I caught it when preparing submission of:
https://patchwork.dpdk.org/project/dpdk/patch/20230404124840.1898-2-david.marchand@redhat.com/
dpdk.org checkpath did not catch it, so it is probably lagging a bit.


For reference, in my environment, this looks like:
### [PATCH] malloc: rework heap destroy

WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely
unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible)
instead of BUG() or variants
#23: FILE: lib/eal/common/malloc_heap.c:1389:
+    RTE_BUILD_BUG_ON(offsetof(struct malloc_heap, lock) != 0);

total: 0 errors, 1 warnings, 23 lines checked

0/1 valid patch


-- 
David Marchand


  reply	other threads:[~2023-04-04 13:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-04 12:36 David Marchand
2023-04-04 13:00 ` Ferruh Yigit
2023-04-04 13:18   ` David Marchand [this message]
2023-04-23 13:55   ` Thomas Monjalon

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=CAJFAV8w4Y-wfPUS3MXs4NTsxRrZgFwuLmGvjv+dmJf_UaV3OdQ@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=thomas@monjalon.net \
    /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).