Re: [PATCH 0/3] Include kernel config by default
Am 26.01.2013 14:34, schrieb Alexander Holler: Hello, I've seen too many systems where the config to build the used kernel got lost and people were unable to diagnose problems or to rebuild a modified or updated kernel. It's a subject which worries me since several years. Therefor I finally prepared the following patch(es) to include the config by default, make it by default accessible through /proc/config.gz, to hide the option to not include the config below "embedded" and to remove all now unnecessary IKCONFIG_* options from 174 defconfigs (almost all of them enabled those options explicit). I've already posted that two times before (https://lkml.org/lkml/2012/7/25/2 and https://lkml.org/lkml/2012/10/18/132) without even getting a single response. So I don't know if it's a totally foolish idea, if nobody is interested, or if the previous patches just weren't seen by anybody. I've now added the maintainers of the two large architectures (x86 and arm), the master himself and a few other people to cc (sorry if I've missed any important person), and I made the subject more clearly. Maybe this will provoke at least a single response. ;) To add a last note: I really only care about the first patch which sets the default to y. The other two patches are more or less "nice to have" (imho) and the third patch could be even splitted into 14 patches (one for every architecture) or even 174 singles patches (one for every board(-type). If requested I would split the third patch. But now I'm finished. ;) So if no one responses (or feels responsible), I won't bother again through sending them again. Regards, Alexander -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/3] Include kernel config by default
Am 26.01.2013 14:34, schrieb Alexander Holler: Hello, I've seen too many systems where the config to build the used kernel got lost and people were unable to diagnose problems or to rebuild a modified or updated kernel. It's a subject which worries me since several years. Therefor I finally prepared the following patch(es) to include the config by default, make it by default accessible through /proc/config.gz, to hide the option to not include the config below embedded and to remove all now unnecessary IKCONFIG_* options from 174 defconfigs (almost all of them enabled those options explicit). I've already posted that two times before (https://lkml.org/lkml/2012/7/25/2 and https://lkml.org/lkml/2012/10/18/132) without even getting a single response. So I don't know if it's a totally foolish idea, if nobody is interested, or if the previous patches just weren't seen by anybody. I've now added the maintainers of the two large architectures (x86 and arm), the master himself and a few other people to cc (sorry if I've missed any important person), and I made the subject more clearly. Maybe this will provoke at least a single response. ;) To add a last note: I really only care about the first patch which sets the default to y. The other two patches are more or less nice to have (imho) and the third patch could be even splitted into 14 patches (one for every architecture) or even 174 singles patches (one for every board(-type). If requested I would split the third patch. But now I'm finished. ;) So if no one responses (or feels responsible), I won't bother again through sending them again. Regards, Alexander -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/3] Include kernel config by default
Hi, [CC'd extract-ikconfig creator] > I've seen too many systems where the config to build the used kernel got > lost and people were unable to diagnose problems or to rebuild a modified > or updated kernel. It's a subject which worries me since several years. I'm strongly in favour of such a change. The actual config is simply very important for traceability. In a recent case of mine I simply built the kernel on an external HDD and did not copy the config file on deployment (e.g. to /boot). With that kernel build tree then unavailable, I then realized that this kernel fortunately did have IKCONFIG_PROC enabled, thus configs.ko was available for (re-)use. However an argument could be made that the default setting should be the bare-minimum needed to provide this information source in emergency cases (i.e., a manual run of scripts/extract-ikconfig would be in order and easily acceptable). $ ls -l kernel/configs.ko -rw-r--r-- 1 root root 35788 Jan 25 18:43 kernel/configs.ko IMHO more than 32kB for the proc/config.gz module arguably is quite a bit of code for it to painlessly be enabled by default given availability of other methods of retrieval. However, now that I think of it ISTR that using extract-ikconfig on my bzImage did NOT work yet loading configs.ko of the same install successfully provided a /proc/config.gz. Huh?? If this is the case, then one or both of these things ought to be done: - make extract-ikconfig not fail in such a case - [failing the prior one] enable /proc/config.gz by default, too Aww wait: I was mistaken in thinking that the config data is statically included in the kernel and configs.ko then is about providing /proc only. This not being the case (config data itself is provided by *module*, too) explains both my extract-ikconfig failure on the static kernel image and the size of configs.ko, so additionally enabling /proc/config.gz in this module most likely is a non-issue. However, this means that extract-ikconfig is missing a user error message indicating that the reason for lookup failure perhaps is that the setting is module-based and thus cannot be found in image (extract-ikconfig's header comments don't fully document this fact either). Will be creating a commit for this eventually (or do you want to add such thing to your patchset now? ;). Thanks for your effort, Andreas Mohr -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH 0/3] Include kernel config by default
Hello, I've seen too many systems where the config to build the used kernel got lost and people were unable to diagnose problems or to rebuild a modified or updated kernel. It's a subject which worries me since several years. Therefor I finally prepared the following patch(es) to include the config by default, make it by default accessible through /proc/config.gz, to hide the option to not include the config below "embedded" and to remove all now unnecessary IKCONFIG_* options from 174 defconfigs (almost all of them enabled those options explicit). I've already posted that two times before (https://lkml.org/lkml/2012/7/25/2 and https://lkml.org/lkml/2012/10/18/132) without even getting a single response. So I don't know if it's a totally foolish idea, if nobody is interested, or if the previous patches just weren't seen by anybody. I've now added the maintainers of the two large architectures (x86 and arm), the master himself and a few other people to cc (sorry if I've missed any important person), and I made the subject more clearly. Maybe this will provoke at least a single response. ;) Regards, Alexander -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH 0/3] Include kernel config by default
Hello, I've seen too many systems where the config to build the used kernel got lost and people were unable to diagnose problems or to rebuild a modified or updated kernel. It's a subject which worries me since several years. Therefor I finally prepared the following patch(es) to include the config by default, make it by default accessible through /proc/config.gz, to hide the option to not include the config below embedded and to remove all now unnecessary IKCONFIG_* options from 174 defconfigs (almost all of them enabled those options explicit). I've already posted that two times before (https://lkml.org/lkml/2012/7/25/2 and https://lkml.org/lkml/2012/10/18/132) without even getting a single response. So I don't know if it's a totally foolish idea, if nobody is interested, or if the previous patches just weren't seen by anybody. I've now added the maintainers of the two large architectures (x86 and arm), the master himself and a few other people to cc (sorry if I've missed any important person), and I made the subject more clearly. Maybe this will provoke at least a single response. ;) Regards, Alexander -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 0/3] Include kernel config by default
Hi, [CC'd extract-ikconfig creator] I've seen too many systems where the config to build the used kernel got lost and people were unable to diagnose problems or to rebuild a modified or updated kernel. It's a subject which worries me since several years. I'm strongly in favour of such a change. The actual config is simply very important for traceability. In a recent case of mine I simply built the kernel on an external HDD and did not copy the config file on deployment (e.g. to /boot). With that kernel build tree then unavailable, I then realized that this kernel fortunately did have IKCONFIG_PROC enabled, thus configs.ko was available for (re-)use. However an argument could be made that the default setting should be the bare-minimum needed to provide this information source in emergency cases (i.e., a manual run of scripts/extract-ikconfig would be in order and easily acceptable). $ ls -l kernel/configs.ko -rw-r--r-- 1 root root 35788 Jan 25 18:43 kernel/configs.ko IMHO more than 32kB for the proc/config.gz module arguably is quite a bit of code for it to painlessly be enabled by default given availability of other methods of retrieval. However, now that I think of it ISTR that using extract-ikconfig on my bzImage did NOT work yet loading configs.ko of the same install successfully provided a /proc/config.gz. Huh?? If this is the case, then one or both of these things ought to be done: - make extract-ikconfig not fail in such a case - [failing the prior one] enable /proc/config.gz by default, too Aww wait: I was mistaken in thinking that the config data is statically included in the kernel and configs.ko then is about providing /proc only. This not being the case (config data itself is provided by *module*, too) explains both my extract-ikconfig failure on the static kernel image and the size of configs.ko, so additionally enabling /proc/config.gz in this module most likely is a non-issue. However, this means that extract-ikconfig is missing a user error message indicating that the reason for lookup failure perhaps is that the setting is module-based and thus cannot be found in image (extract-ikconfig's header comments don't fully document this fact either). Will be creating a commit for this eventually (or do you want to add such thing to your patchset now? ;). Thanks for your effort, Andreas Mohr -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
