From: Dan Carpenter <dan.carpenter@oracle.com>
To: Dan McDonald <danmcd@joyent.com>
Cc: smatch@vger.kernel.org
Subject: Re: Intel i40e code finds smatch bug
Date: Tue, 19 Jan 2021 21:55:47 +0300 [thread overview]
Message-ID: <20210119185547.GN2696@kadam> (raw)
In-Reply-To: <38E556EE-C173-4935-80DF-51DC4FE8C90E@joyent.com>
On Tue, Jan 19, 2021 at 12:22:50PM -0500, Dan McDonald wrote:
> We in illumos are in the midst of updating our i40e code from Intel upstream. We found a bug in smatch while building it. It's documented here in:
>
> https://www.illumos.org/issues/13457
>
> A colleague recommended I include a toy program, try the smatch `master` branch on a Linux distro, and submit the toy to this list. Its source is attached, ready to compile (without incident) and smatch (with one incident, but not two). You'll see two cases of potential failure, but only one (the one Intel source uses to confirm proper compilation) breaks smatch. Look for the KEBE comments.
>
> Once this bug gets fixed, I suspect we'll also be updating our branch of smatch as well. :)
>
> Thanks,
> Dan
>
Unfortunately Sparse doesn't support #pragma pack. This was reported to
the Sparse list last February and the response was that pragma pack is
disgusting so don't use it.
http://tw.spinics.net/lists/linux-sparse/msg10816.html
I wish I could give you better news than that...
Luk recently was working on better support of packed structs (which have
been a known issue for a while) but I doubt that will help here.
regards,
dan carpenter
next prev parent reply other threads:[~2021-01-19 18:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 17:22 Intel i40e code finds smatch bug Dan McDonald
2021-01-19 18:55 ` Dan Carpenter [this message]
2021-01-19 19:12 ` Dan McDonald
2021-01-19 20:51 ` Dan McDonald
2021-01-19 21:42 ` Luc Van Oostenryck
2021-01-19 21:49 ` Dan McDonald
2021-01-21 8:49 ` Dan Carpenter
2021-01-25 15:10 ` Dan Carpenter
2021-01-25 16:33 ` Luc Van Oostenryck
2021-01-25 16:41 ` Dan McDonald
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=20210119185547.GN2696@kadam \
--to=dan.carpenter@oracle.com \
--cc=danmcd@joyent.com \
--cc=smatch@vger.kernel.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.