The fix has been released in the form of 5.4.0-40-generic on focal, and
5.3.0-62-generic on Eoan.
** Changed in: linux (Ubuntu Eoan)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug
The commit has landed in 5.3.0-56-generic on eoan and 5.4.0-38-generic
on focal, currently in -proposed.
Verification for each kernel:
I set the sysctl kernel.core_pattern to "|" with:
$ sudo sysctl kernel.core_pattern="|"
I then compiled the following reproducer:
int main()
{
*(int*)33 =
Sudip's commit landed in mainline last week, in time for 5.7-rc3:
commit db973a7289dad24e6c017dcedc6aee886579dc3a
Author: Sudip Mukherjee
Date: Mon Apr 20 18:14:20 2020 -0700
Subject: coredump: fix null pointer dereference on coredump
As of this morning, it has been queued up in Greg-KH's
Sudip Mukherjee made a more elegant fix than I did, and he posted it to
the fsdevel mailing list:
https://lore.kernel.org/linux-
fsdevel/20200416194612.21418-1-sudipm.mukher...@gmail.com/
I got an email saying that this has now been pulled into the -mm tree.
I will update when this patch
I managed to figure out what was going on, and made a patch to fix the
problem. I sent it upstream for feedback:
Cover Letter:
https://lore.kernel.org/linux-fsdevel/20200220051015.14971-1-matthew.ruff...@canonical.com/
Patch:
The regression was introduced by the following commit:
commit 315c69261dd3fa12dbc830d4fa00d1fad98d3b03
Author: Paul Wise
Date: Fri Aug 2 21:49:05 2019 -0700
Subject: coredump: split pipe command whitespace before expanding template
You can read it here:
Yes, you are absolutely correct. I can reproduce this now, when
kernel.core_pattern is set to "|".
I can also confirm that the first kernel that this is broken in is 5.3,
as it works fine in 5.2 and below.
I will look into this and hopefully get this fixed for you. Thanks for
reporting!
After previous comment I checked my system settings and find what affect to
this bug.
I usually disable system core dump in all linux distributions using
kernel.core_pattern=| in sysctl.conf
When kernel.core_pattern has default all ok.
So kernel.core_pattern=| cause this bug. It occurs since
I cannot reproduce this. I compiled the reproducer program and tested on
a Eoan VM running in KVM, with the same 5.3.0-29-generic kernel:
ubuntu@ubuntu:~$ ./socktest
Segmentation fault (core dumped)
ubuntu@ubuntu:~$ tail /var/log/kern.log
Feb 14 04:00:41 ubuntu kernel: [ 134.951620]
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863086
Title:
unkillable process (kernel NULL pointer dereference)
To manage notifications about this
10 matches
Mail list logo
