linux-kernel - Re: kconfig: list unknown symbols in the old .config

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Sun, 20 Aug 2023 11:30:57 +0900
From:   Sergey Senozhatsky <senozhatsky@...omium.org>
To:     Jesse T <mr.bossman075@...il.com>
Cc:     Sergey Senozhatsky <senozhatsky@...omium.org>,
        Masahiro Yamada <masahiroy@...nel.org>,
        Tomasz Figa <tfiga@...omium.org>, linux-kbuild@...r.kernel.org,
        linux-kernel@...r.kernel.org, Randy Dunlap <rdunlap@...radead.org>
Subject: Re: kconfig: list unknown symbols in the old .config

On (23/08/19 15:54), Jesse T wrote:
> > We recently were hit (unnecessarily hard) when after kernel uprev we
> > figured that something wasn't working. The root cause was a rename of
> > the CONFIG_FOO option between kernel releases, which make oldconfig
> > doesn't warn/notify about.
> >
> > Would it be possible to add either a new --listunknown mode to conf or
> > to somehow make it conf_warning("unknown symbol: %s\n", line) when it
> > reads a line from oldconf that it cannot sym_find()?
> 
> This makes sense and I brought up this scenario a couple of days ago
> on a recent patch.
> I can make a patch for this if needed.

I posted an RFC patch a couple of days ago
https://lore.kernel.org/all/20230817012007.131868-1-senozhatsky@chromium.org/T/#u