This thread sheds more light on why it is a good idea to disable a.out support:
https://lore.kernel<email address hidden>/
Specifically, the coredump support is broken/buggy and that's addressed in this patch:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=08300f4402abc0eb3bc9c91b27a529836710d32d
a.out support, in general, is now deprecated and will likely be removed in a few upstream releases:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eac616557050737a8d6ef6fe0322d0980ff0ffde
Since we only had a.out enabled in i386 and armhf configs, I think we're better off simply disabling the config option, rather than backporting the patch that rips out coredumping. We'll do this for Xenial and newer releases.
This thread sheds more light on why it is a good idea to disable a.out support:
https:/ /lore.kernel<email address hidden>/
Specifically, the coredump support is broken/buggy and that's addressed in this patch:
https:/ /git.kernel. org/pub/ scm/linux/ kernel/ git/torvalds/ linux.git/ commit/ ?id=08300f4402a bc0eb3bc9c91b27 a529836710d32d
a.out support, in general, is now deprecated and will likely be removed in a few upstream releases:
https:/ /git.kernel. org/pub/ scm/linux/ kernel/ git/torvalds/ linux.git/ commit/ ?id=eac61655705 0737a8d6ef6fe03 22d0980ff0ffde
Since we only had a.out enabled in i386 and armhf configs, I think we're better off simply disabling the config option, rather than backporting the patch that rips out coredumping. We'll do this for Xenial and newer releases.