linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: linux-sparse@vger.kernel.org, Alexey Gladkov <gladkov.alexey@gmail.com>
Subject: Re: [PATCH] dissect: use struct symbol::visited/inspected instead of ::examined/evaluated
Date: Wed, 29 Jul 2020 17:34:13 +0200	[thread overview]
Message-ID: <20200729153413.GB4360@redhat.com> (raw)
In-Reply-To: <20200729145132.81479-1-luc.vanoostenryck@gmail.com>

On 07/29, Luc Van Oostenryck wrote:
>
> The dissect client uses struct symbol's fields 'examined' & 'evaluated'
> to avoid reprocessing the same symbols. But these fields are used
> internally by sparse for type examination & evaluation and despite
> dissect not doing these operations explicitly, they can be done
> implicitly

Yes. For example, test_dissect.c calls show_typename() and this can
lead to examine/evaluate.

I didn't bother to fix this because test_dissect.c is the very basic
debugging tool.

> So, add a new field to struct symbol: 'inspected' and use it, as
> well as the existing 'visited', instead of 'evaluated' & 'examined'.

Thanks! Looks good to me.

> Note: when used on the kernel, this patch avoids a lot of warnings:
> 	"warning: r_member bad sym type=7 kind=0"
> 	"warning: r_member bad mem->kind = 0"
>       and creates substantially more normal output.

So this is test-dissect, sindex should be fine even without this patch.

Acked-by: Oleg Nesterov <oleg@redhat.com>


  reply	other threads:[~2020-07-29 15:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-29 14:51 [PATCH] dissect: use struct symbol::visited/inspected instead of ::examined/evaluated Luc Van Oostenryck
2020-07-29 15:34 ` Oleg Nesterov [this message]
2020-07-29 15:48   ` Luc Van Oostenryck

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=20200729153413.GB4360@redhat.com \
    --to=oleg@redhat.com \
    --cc=gladkov.alexey@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.com \
    /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).