<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/source/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in expected_stderr</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>54f11924e4854177b357af499ebc447dc8c3c590 - kconfig: prevent out-of-bounds user input for numeric options</title>
        <link>http://kernelsources.org:8080/source/history/linux/scripts/kconfig/tests/err_num_bounds/expected_stderr#54f11924e4854177b357af499ebc447dc8c3c590</link>
        <description>kconfig: prevent out-of-bounds user input for numeric optionsCurrently, user input of out-of-bounds values for &apos;int&apos; and &apos;hex&apos; optionsis possible, leading to later silent failures in Kconfig if that value isused in a comparison, or a warning by GCC or error by Clang if used in theC code.Let&apos;s factor out the out-of-bounds check on constants, so that it can bereused for checking user input.The frontend will now reject an attempted user input of an out-of-boundsnumeric value, similarly to how a value outside the active &apos;range&apos; alreadydoes.For migration of existing configurations, a .config file with anout-of-bounds numeric value will be allowed for now, but will warn theuser when read in by confdata.cAssisted-by: LLMSigned-off-by: Julian Braha &lt;julianbraha@gmail.com&gt;Reviewed-by: Nicolas Schier &lt;n.schier@fritz.com&gt;Link: https://patch.msgid.link/20260915211508.291790-5-julianbraha@gmail.comSigned-off-by: Nathan Chancellor &lt;nathan@kernel.org&gt;

            List of files:
            /linux/scripts/kconfig/tests/err_num_bounds/expected_stderr</description>
        <pubDate>Tue, 15 Sep 2026 23:15:07 +0200</pubDate>
        <dc:creator>Julian Braha &lt;julianbraha@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>a5e84d6f6df1fdb64c06fdb64894199aaf5ec899 - kconfig: check for out-of-bounds numeric constants</title>
        <link>http://kernelsources.org:8080/source/history/linux/scripts/kconfig/tests/err_num_bounds/expected_stderr#a5e84d6f6df1fdb64c06fdb64894199aaf5ec899</link>
        <description>kconfig: check for out-of-bounds numeric constantsThe Kconfig interpreter internally represents constants as strings, thenattempts to parse them as 64-bit signed integers for &apos;int&apos; options, and64-bit unsigned integers for &apos;hex&apos; options.However, there is currently no check that the conversion succeeds, leadingto failures when the values are actually used. For example:  config LARGE_INT    int    default 10000000000000000000  config BUGGED_INT_COMPARISON    bool    default y if LARGE_INT &lt; 2Obviously 10000000000000000000 is larger than 2, but the Kconfiginterpreter will fallback to comparing the two values with strcmp() afterthe numeric conversion fails, causing the first character, &apos;1&apos;, to becompared with &apos;2&apos;, and giving the wrong result.Since none of these out-of-bounds values are used as constants anywhere inthe tree, we can already make these error out.Assisted-by: LLMSigned-off-by: Julian Braha &lt;julianbraha@gmail.com&gt;Reviewed-by: Nicolas Schier &lt;n.schier@fritz.com&gt;Link: https://patch.msgid.link/20260915211508.291790-3-julianbraha@gmail.comSigned-off-by: Nathan Chancellor &lt;nathan@kernel.org&gt;

            List of files:
            /linux/scripts/kconfig/tests/err_num_bounds/expected_stderr</description>
        <pubDate>Tue, 15 Sep 2026 23:15:05 +0200</pubDate>
        <dc:creator>Julian Braha &lt;julianbraha@gmail.com&gt;</dc:creator>
    </item>
</channel>
</rss>
