linux-kernel - Re: [PATCH v3] docs: describe how to quickly build a trimmed kernel

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <f53f84b5-9da7-0726-2e1f-f7e81e8ecd24@gmail.com>
Date:   Mon, 6 Mar 2023 15:57:28 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Thorsten Leemhuis <linux@...mhuis.info>,
        Jonathan Corbet <corbet@....net>
Cc:     Randy Dunlap <rdunlap@...radead.org>,
        Lukas Bulwahn <lukas.bulwahn@...il.com>,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        regressions@...ts.linux.dev
Subject: Re: [PATCH v3] docs: describe how to quickly build a trimmed kernel

On 3/6/23 12:40, Thorsten Leemhuis wrote:
>> If your distro config have ``CONFIG_IKCONFIG=y``, you can copy from
>> procfs::
>>
>>     zcat /proc/config.gz > .config
> <snipped>
> 
>> If it isn't the case, you may want to enable the aforementioned config
>> option.
> 
> That or put them in /boot/config-$(uname -r). But well, that is
> something the provider of the running kernel needs to do, so it won't
> help the reader if we mention it here.
> 
> Or do you think the guide should explain this to ensure people can
> pickup their config from there again in case they deleted their build
> artifacts? Hmmm. I currently tend to think that's not worth making the
> text longer for, as at that point it might be better to restart from
> scratch with a distro config anyway.
> 

I think it depends whether someone would pick from /proc/config.gz or
/boot/config. My kernel configuration have CONFIG_IKCONFIG=y but I
often copy the config from the latter instead, since I booted with
arbitrary kernel version when compiling two or three versions, and I
want to ensure that the config used is from correct version (i.e.
I use /boot/config-5.15.x-string to build 5.15.x+1 kernel).

Thanks.

-- 
An old man doll... just what I always wanted! - Clara