Skip to contentSkip to conversation

Makedumpfile and kernel support

DISCUSSION Louis Bouchard 2 participants 3 messages May 21, 2015 – May 27, 2015

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hello,

- From time to time, on the distribution side, we get reports that makedumpfile says the kernel version is not supported with the following message :

"The kernel version is not supported.
The created dumpfile may be incomplete. "

Depending on the kernel and makedumpfile versions, it can be either disregarded or it requires fixing on the distribution. For instance, with Kumagai's help, I backported the required commits so makedumpfile on Jessie (1.5.3) would not complain about Jessie's kernels (3.16).

While we can review each patch to identify those who have specific kernel requirements, would it be possible to identify a way to highlight those patches so they become easily identifiable for potential backport ?

Maybe something like "[kernel]" in the git log or specific mention in the commit log. I would like to avoid going back to upstream to confirm that the proper patches are being identified.

Any comments, toughts, concerns ?

Kind regards,

...Louis

- --
Louis Bouchard
Software engineer, Cloud & Sustaining eng. Canonical Ltd
Ubuntu developer Debian Maintainer
GPG : 429D 7A3B DD05 B6F8 AF63 B9C4 8B3D 867C 823E 7A61 -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJVXaQAAAoJEIs9hnyCPnphYbMP/21fhl1pHNcToYH5c2casXTM D794dqwGzSSgXNWPueTajW/7OyvEEryN6izUfOUQ3ACJ10c0zzv/GQ6mjrIoKLz8 +xhml3gM0Tu3oJsKz5fHDbkKAx9X8604fQSB5Vrsz23Tr/MaNH2ASV000PE7HvY5 uIupEQMsluVV8EeLtjI1NPGNKwk9ZpwgCK4ogKCD0k3Gqn0JGB/bA6T0dpqjPGkm At+nDUMNpADYkWd6sm9pem1GqgUJMNjgyu9P/vKxGCd++uUvmXolZT0BXXJhebKg U8BNCxf/l/dhfXx5++GMMVCtD8Po/oDU2/x3C7MefrTaRlZmHTzEAhWr/BPp3I8J vPK+emrS8b5WcrWY3eq3dvL1gnW0k8ysppUEntgmXF5u1XlDopyoLeDuCXhjrTz8 +y4OHzp2TxX10hZPP6T60YM64AyRsDzJoU1UTk6WMtDxfvy1MW0ynQ5K8jSQHMnO 1GWEPFF2gXmAmMkWh7KxPbjOvBriJurwo4YDjf7kiu9XWCUzSN/o3QV4ywxYS9Nf Yf8W/zSiEL6z0pODSuNgFis9t610vKdGLPAS97JX3CA2wn1jSfwP7eCXc81Jf1iJ +O10J4I5/G04iCOaVk0muEywwfeq5GcXsSj0u/YwCZEP1TzWAEhyEZEzn+k4RQJU 6R88MEn7+Zcuz+gvxXBk
=10mW
-----END PGP SIGNATURE-----

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#1 lore raw

Hello Louis,

Quoted 15 lines

- From time to time, on the distribution side, we get reports that makedumpfile says the kernel version is not supported with the following message :

"The kernel version is not supported.
The created dumpfile may be incomplete. "

Depending on the kernel and makedumpfile versions, it can be either disregarded or it requires fixing on the distribution. For instance, with Kumagai's help, I backported the required commits so makedumpfile on Jessie (1.5.3) would not complain about Jessie's kernels (3.16).

While we can review each patch to identify those who have specific kernel requirements, would it be possible to identify a way to highlight those patches so they become easily identifiable for potential backport ?

Quoted 5 lines

Maybe something like "[kernel]" in the git log or specific mention in the commit log. I would like to avoid going back to upstream to confirm that the proper patches are being identified.

Any comments, toughts, concerns ?

How about inserting a label like "* Required for kernel X.YY" into the first line of the commit log ?

It's better if contributors write it by themselves, otherwise I'll add it when merging.

Thanks,
Atsushi Kumagai

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

#2 lore raw

Hello,

Quoted 26 lines · Atsushi Kumagai

Hello Louis,

Quoted 15 lines

- From time to time, on the distribution side, we get reports that makedumpfile says the kernel version is not supported with the following message :

"The kernel version is not supported.
The created dumpfile may be incomplete. "

Depending on the kernel and makedumpfile versions, it can be either disregarded or it requires fixing on the distribution. For instance, with Kumagai's help, I backported the required commits so makedumpfile on Jessie (1.5.3) would not complain about Jessie's kernels (3.16).

While we can review each patch to identify those who have specific kernel requirements, would it be possible to identify a way to highlight those patches so they become easily identifiable for potential backport ?

Quoted 5 lines

Maybe something like "[kernel]" in the git log or specific mention in the commit log. I would like to avoid going back to upstream to confirm that the proper patches are being identified.

Any comments, toughts, concerns ?

How about inserting a label like "* Required for kernel X.YY" into the first line of the commit log ?

Quoted 7 lines

It's better if contributors write it by themselves, otherwise I'll add it when merging.

Thanks,
Atsushi Kumagai

First of all, sorry for the late reply.

I think that this would be a very good solution. I just don't want to impose the burden on you. So if people provide kernel specific patches, they should identify to which kernel it relates to as it is proposed above.

Thanks for the suggestion.

Kind regards,

...Louis

Signature · 10 lines
Louis Bouchard
Software engineer, Cloud & Sustaining eng.
Canonical Ltd
Ubuntu developer                       Debian Maintainer
GPG : 429D 7A3B DD05 B6F8 AF63  B9C4 8B3D 867C 823E 7A61

_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec