From: Philip Li <philip.li@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: fs/proc/task_nommu.c:67:55: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Mon, 25 May 2020 08:08:54 +0800 [thread overview]
Message-ID: <20200525000854.GA29958@intel.com> (raw)
In-Reply-To: <20200524190415.zb5v5dlp6jxhb42y@ltop.local>
[-- Attachment #1: Type: text/plain, Size: 1510 bytes --]
On Sun, May 24, 2020 at 09:04:15PM +0200, Luc Van Oostenryck wrote:
> Hi,
>
> I'm wondering why Sparse error/warning messages are often subtly
> corrupted. For exemple:
>
> > sparse warnings: (new ones prefixed by >>)
> >
> > >> fs/proc/task_nommu.c:67:55: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected struct refcount_struct const [usertype] *r @@ got sstruct refcount_struct const [usertype] *r @@
>
> The ending part "got sstruct" is wrong, parse correctly emits "got struct".
>
> > >> fs/proc/task_nommu.c:68:43: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void const *objp @@ got struct sighand_struct [noderevoid const *objp @@
>
> It's wrong here too: "got struct sighand_struct [noderevoid const *objp"
> It looks like starting with the 'expected' part and ending with the 'got' part.
>
> It's not something new but I never bothered to repport.
> It only happens with the part prefixed by '>>', I've never seen this sort of
> corruption in the other parts.
Thanks Luc for pointing out this, we will fix this in earliest time
to make report correct.
>
> It's maybe related to some substitution that is made to replace ": warning:"
> or ": error:" by ": sparse:" but since the flag -fdiagnostic-prefix is used
> the result is the redundant ": sparse: sparse:".
Thanks for the hint, we will check code logic.
>
> Best regards,
> -- Luc Van Oostenryck (sparse's maintainer)
next parent reply other threads:[~2020-05-25 0:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200524190415.zb5v5dlp6jxhb42y@ltop.local>
2020-05-25 0:08 ` Philip Li [this message]
2020-05-24 14:59 fs/proc/task_nommu.c:67:55: sparse: sparse: incorrect type in argument 1 (different address spaces) kbuild test robot
2020-05-24 14:59 ` kbuild test robot
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=20200525000854.GA29958@intel.com \
--to=philip.li@intel.com \
--cc=kbuild-all@lists.01.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.