Hi Petar,
Thanks for the bug report.
Unfortunately there's little details about the error.
Could you please post a picture of your compute screen
once the 5.4 kernel fails to boot?
(after you removed the 'quiet' and 'splash' options in
the grub editor, and pressed ctrl-x to boot.)
Mainly
Hey Martin.
The issues reported on comment 1 and commment 24 have different stack
trace signatures, and do not seem to be the same issue at all.
I'll thus mark this bug as Invalid as apparently you couldn't reproduce
the original issue anymore.
If the new issue is still present with the latest
Oops, please remove the --dry-run from apt install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895563
Title:
Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic
To manage
Hey Brendan,
Thanks for reporting this bug.
It looks like the crashdump files didn't come through?
Could you please try to reproduce with the 5.8 kernel from Groovy on
your Bionic install?
These are the steps to install it.
Please remove the .list file as soon as you install the packages, to
** Changed in: ubiquity (Ubuntu)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => Low
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are
it.
** Affects: ubiquity (Ubuntu)
Importance: Low
Assignee: Mauricio Faria de Oliveira (mfo)
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895351
Title:
prepare plugin does
Hi Łukasz,
The arm64/armhf builds are successful now.
I noticed and was checking this on Monday, and even LP PPAs had a very long
wait to start building on ARM at least (mine took 10h+ waiting).
I guess this problem might have failed the builds back on upload approval date,
and then had no
Marking X/F/G as Fix Released.
X/F got the patch via stable updates, thus no LP tag / bot messages.
Xenial version: 4.4.0-189.219
Focal version: 5.4.0-45.49
Groovy version: 5.8 and later.
** Changed in: linux (Ubuntu Xenial)
Status: Fix Committed => Fix Released
** Changed in: linux
Also marking Ubuntu / Groovy as Fix Released, as Groovy/devel has the
5.8 kernel already, which ships the fix.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Groovy)
Status: Won't Fix => Fix Released
--
You received this bug
The autopkgtests failures for sbuild on focal-proposed
are all addressed/passed; the Pending SRU page is clear
for focal/deboostrap. [1]
Thanks @mruffell for the ping to re-trigger the sbuild
failed tests (that debootstrap groovy) now that groovy's
procenv has the fix for GCC 10.
cheers,
Thanks for verifying focal-proposed (and adding the tag.)
Oh, I forgot to mark Groovy as Fix Released on comment #15; doing it
now.
** Changed in: util-linux (Ubuntu Groovy)
Status: Fix Committed => Triaged
** Changed in: util-linux (Ubuntu Groovy)
Status: Triaged => Fix Released
Autopkgstests failures:
- gfs2-utils/ppc64el: unrelated; I'll take a look (it held groovy's proposed
migration weeks ago.)
- systemd: likely unrelated, see bug 1892358 (success rate dropped)
- tracker: flaky; now passing.
- kopanocore: flaky; now passing.
--
You received this bug notification
With the -proposed package: (pass = 15, fail = 0, total = 15)
---
$ dpkg -s librados2 | grep ^Version:
Version: 14.2.11-0ubuntu0.19.10.1~cloud2
$ for i in $(seq 1 15); do
sudo ceph tell 'mon.*' injectargs '--mon-allow-pool-delete=true'
sudo LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/ceph/ \
Steps to build the test case:
$ sudo add-apt-repository -s cloud-archive:train-proposed
$ sudo apt update
$ apt source ceph
$ cd ceph-14.2.11
$ sed 's/-DWITH_TESTS=OFF/-DWITH_TESTS=ON/' -i debian/rules
$ dch -l '+withtestson' 'Enable building tests.'
$ sudo apt build-dep -y ceph
$
Corey, thanks.
The packages in train-proposed look good -- the test-case always passes.
cheers,
Mauricio
$ dpkg -s librados2 | grep ^Version:
Version: 14.2.11-0ubuntu0.19.10.1~cloud2
$ sudo ceph mon versions
{
"ceph version 14.2.11 (f7fdb2f52131f54b891a2ec99d8205561242cdaf) nautilus
Just for documentation purposes,
The test-case has to be rebuilt with the new source package; attaching it.
The old test-case/v14.2.9-based doesn't run in new packages/v14.2.11-based.
Old test-case:
$ time sudo LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/ceph/ \
~/ceph_test_rados_api_misc \
Uploaded to Focal.
Seyeong, could you please update the Test Case section of the SRU template
to reflect the usage of Ubuntu commands and not upstream/built commands?
Thanks,
Mauricio
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Groovy now has the fix released in util-linux 2.36-2ubuntu1. Focal can
now move on.
I've changed the debdiff slightly on the DEP3 headers and version
number, small nitpicks.
The package builds fine on all architectures in a PPA, and testing is
successful:
focal-release / fail:
$ dpkg -s
This should be fixed with rsyslog 8.2001.0-1ubuntu1.1 in focal-updates.
** Changed in: rsyslog (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Oh, and for "Eoan" (5.3/linux-hwe on Bionic), all good with stress-ng as
well.
$ uname -rv
5.3.0-66-generic #60-Ubuntu SMP Tue Aug 11 08:42:43 UTC 2020
$ ./stress-ng --version && ./stress-ng --af-alg 0 --timeout 2h 2>&1 | tee
../stress-ng.log.eoan-bionic-proposed
stress-ng, version 0.11.14 (gcc
I've also ran stress-ng as in comment #1 (below) on 4 CPUs for 8 hours
on X/B/F.
No signs of issues: it finishes successfully and no weird messages in
the kernel logs.
$ sudo modprobe -a \
$(modinfo \
/lib/modules/$(uname -r)/kernel/crypto/*.ko \
Verification done on "eoan" (5.3/linux-hwe on Bionic)
$ uname -rv
5.3.0-65-generic #59-Ubuntu SMP Tue Jul 28 07:27:41 UTC 2020
$ sudo make-bcache --bdev $DEV --block 8k
...
[ 103.766185] bcache: bcache_device_init() bcache0: sb/logical block size
(8192) greater than page size (4096) falling
Verification done for bionic-proposed.
The reporter user confirmed that the organic reproducer (Varnish Cache
Plus with the Crypto vmod) ran successfully over the weekend with the
4.15.0-114-generic kernel, to approximately 3 days (2d 20h runtime.)
The same workload used to trigger the bug with
Verification done for Focal.
$ uname -rv
5.4.0-43-generic #47-Ubuntu SMP Sat Aug 8 06:34:35 UTC 2020
$ sudo make-bcache --bdev $DEV --block 8k
...
[ 71.251993] bcache: bcache_device_init() bcache0: sb/logical block size
(8192) greater than page size (4096) falling back to device logical block
Verification done for Focal.
$ uname -rv
5.4.0-43-generic #47-Ubuntu SMP Sat Aug 8 06:34:35 UTC 2020
$ ./aa-refcnt-af_alg &
$ sudo insmod kmod.ko
...
[ 171.672847] accept() :: comm = aa-refcnt-af_al, pid = 1600,
sk->sk_security->label->count = 0x583
[ 171.674249] release() :: comm =
Verification done for Bionic.
$ uname -rv
4.15.0-113-generic #114-Ubuntu SMP Sun Aug 9 07:27:58 UTC 2020
$ ./aa-refcnt-af_alg &
$ sudo insmod kmod.ko
...
[ 335.387236] release() :: comm = aa-refcnt-af_al, pid = 5764,
Verification done for Bionic.
$ uname -rv
4.15.0-113-generic #114-Ubuntu SMP Sun Aug 9 07:27:58 UTC 2020
$ sudo make-bcache --bdev $DEV --block 8k
...
[ 18.467465] bcache: bcache_device_init() bcache0: sb/logical block size
(8192) greater than page size (4096) falling back to device logical
Hi Seyeong,
The proposed-migration of util-linux in groovy is blocked on one last
autopkgtest of gfs2-utils failing on ppc64el (the 'mount' test times
out; reproducible even w/ previous versions) [1, 2]
This is new and unrelated to these changes (not uploaded to groovy), but
prevents uploading
In an interesting overnight timing event, that rsyslog upload has been
accepted to focal-proposed.
Sure enough, it built with librelp-dev_1.5.0-1ubuntu2.
And the configure stage enables the option:
checking for relpSrvSetTlsConfigCmd... yes
checking for relpSrvSetTlsConfigCmd... (cached) yes
Er, actually s/Invalid/Fix Committed/, so to document that this bug
(behavior of input parameter 'tls.tlscfgcmd' not supported) will be
fixed/gets fixed on rsyslog 8.2001.0-1ubuntu1.1 (in focal-proposed.)
** Changed in: rsyslog (Ubuntu Focal)
Status: In Progress => Fix Committed
** Tags
Verification/comparison steps to ensure that the modified
rsyslog package is built and working correctly, given its
importance in the distribution:
1) Compare test suite results in build logs
2) Compare configuration options in build logs
3) Compare packages' control file and contents
All look
** Patch added: "lp1888926-focal-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1888926/+attachment/5399433/+files/lp1888926-focal-v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Jorge,
Thanks for tracking this down in the build history.
> I suspect that the rsyslog package was built against and older librelp
version.
You're right, the build log shows 'librelp-dev_1.4.0-2'
in the package installs/'Build environment' section.
I slightly modified the changelog entry,
** Changed in: util-linux (Ubuntu Groovy)
Status: Confirmed => Fix Committed
** Changed in: util-linux (Ubuntu Focal)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Seyeong,
Thanks for the updated debdiffs and reporting Debian bug 966106
(Please feel free to comment in the LP bug when you report a Debian bug.)
Per the Debian maintainer, they recently stopped shipping/installing rename.ul,
on 2.35.2-5.
Fortunately this only affects Groovy and later (non
Hi Anand,
Yes, that patch is available since 4.4.0-185.215.
Please note that this version if for the linux-image-4.4.0-185-generic
package.
You mentioned version numbers for the linux-generic meta package (which
pulls in linux-image--generic package as a dependency.)
Either way, the first
** Tags added: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888926
Title:
tls.tlscfgcmd not recognized; rebuild rsyslog against librelp 1.5.0
To manage notifications about this
The systemd upload has been accepted into bionic-proposed,
and udev-udeb depends on likmod2-udeb. All good.
Package: udev-udeb
Source: systemd
Version: 237-3ubuntu10.42
...
Depends: libblkid1-udeb (>= 2.31), libc6-udeb (>= 2.27), libkmod2-udeb,
util-linux-udeb
The existing d-i upload to
That cleared up the autopkgtest regression.
systemd [bionic/i386]
Version TriggersDateDurationRequester Result
237-3ubuntu10.41kmod/24-1ubuntu3.5 2020-07-29 23:55:56 UTC
1h 03m 06s mfo pass ...
--
You received this bug
The failing autopkgtest is in the 'upstream' tests
(search for 'TEST RUN: Job-related tests' twice.)
It's very probably unrelated: apparently the testsuite.service
ended unexpectedly, due to a SIGCHLD because the sleep.service
(the child iiuic) got a SIGTERM unexpectedly too, and finished.
Verification done on xenial-proposed.
The kernel in -proposed logs the block size change.
The kernel in -updates fails.
xenial-proposed:
---
$ uname -rv
4.4.0-187-generic #217-Ubuntu SMP Tue Jul 21 04:18:15 UTC 2020
$ apt-cache madison linux-image-4.4.0-187-generic
Verification done on bionic-proposed.
The shlibs file of libkmod2 contains the udeb line:
$ pull-lp-debs libkmod2 bionic
$ dpkg-deb --control libkmod2_24-1ubuntu3.5_amd64.deb dir
$ cat dir/shlibs
libkmod 2 libkmod2
udeb: libkmod 2 libkmod2-udeb
Then building systemd in a
Finally, with the kmod change, plus the systemd rebuild,
now d-i builds successfully on all archs in the PPA [1].
[1] https://launchpad.net/~mfo/+archive/ubuntu/lp1889297/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Apparenlty the systemd package in the upload queue will be reviewed.
For my test packages, @ddstreet told me that a pure no-change rebuild
of systemd would FTBFS on arm64 due to bug #1886197.
So I added that patch to this systemd "almost no-change rebuild" patch.
** Patch removed:
With the test packages for kmod and systemd in this PPA [1]
I can confirm that udev-udeb now Depends: on libkmod2-udeb.
>From the build log:
Package: udev-udeb
...
Depends: libblkid1-udeb (>= 2.31), libc6-udeb (>= 2.27), libkmod2-udeb,
util-linux-udeb
Just uploaded kmod to Bionic.
[1]
> High
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889297
Title:
Bionic: debian-installer FTBFS
Currently building the packages on PPA to verify all three
parts (kmod, systemd, d-i) work correctly with the changes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889297
Title:
Bionic:
In addition to comment #18 that explains why the autopkgtests failures are
unrelated,
I triggered re-runs with debootstrap package in -updates, which hits the same
errors.
Thus confirming this is not a regression with debootstrap in -proposed.
cheers,
Mauricio
pbuilder/bionic
There's a systemd upload for Bionic with this version number already.
I guess that is a larger change that may be intended for post-release,
while this change is needed for release, so d-i builds w/ new kernels.
So, keeping the same number for now, in case this needs to trump that.
** Patch
** Patch added: "lp1889297_bionic_kmod.debdiff"
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1889297/+attachment/5396663/+files/lp1889297_bionic_kmod.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
uild on systemd, after kmod is
built/available in archive.
** Affects: kmod (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: kmod (Ubuntu Bionic)
Importance: High
Assignee: Mauricio Faria de Oliveira (mfo)
Status: In Progress
** Also affects: kmod (Ubu
Uploaded debootstrap to Bionic/Focal. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772556
Title:
d-i netinstall fails due to missing apt-transport-https package
To manage notifications
** Description changed:
[Impact]
When installing over the network using a netinstall image with pxe boot
and with an https apt mirror, the installer fails with the error:
Debootstrap error
couldn't find these debs: apt-transport-https
Check /var/log/syslog or see
Hi Matthew and SRU team,
Performed additional testing for the deboostrap package upload,
checking for regressions in variants (minbase, buildd, default.)
This compares the logs of debootstrap variants in a mirror that
supports both HTTP and HTTPS.
For HTTP: no differences in the logs / no
Bionic
==
Original
$ dpkg -s debootstrap | grep Version:
Version: 1.0.95ubuntu0.6
$ tail -n1 *-$version-*.log
==> debootstrap-updates-bionic--http.log <==
I: Base system installed successfully.
==> debootstrap-updates-bionic--https.log <==
E: Couldn't find these debs:
Focal
=
Original
$ dpkg -s debootstrap | grep Version:
Version: 1.0.118ubuntu1.1
$ tail -n1 *-$version-*.log
==> debootstrap-updates-focal--http.log <==
I: Base system installed successfully.
==> debootstrap-updates-focal--https.log <==
E: Couldn't find these debs:
Hi Sebastian, don't worry, we'll use the synthetic reproducer for the
verification steps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867916
Title:
Regression in kernel 4.15.0-91 causes kernel
** Tags added: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772556
Title:
d-i netinstall fails due to missing apt-transport-https package
To manage notifications about this bug
Verification done on "Disco" (linux-hwe-5.0)
---
# uname -rv
5.0.0-58-generic #62~18.04.1-Ubuntu SMP Tue Jul 14 03:37:30 UTC 2020
For some other reason the kprobes module is not picking up on accept,
only on release. This is unrelated to this patchset.
I used kprobe events instead, which is
Indeed; I was hoping to check what's under the root port just in case,
but acknowledge that might not be helpful / have too much stuff under,
being a desktop system. Let's see. :)
Per the repeated messages I'd imagine this is a device-related error,
but wanted to check the kernel version log in
Hi Pedro,
It's curious that the message is repeatedly showing up at the rate of a few
seconds.
It would initially suggest something might be wrong with the PCI device.
(As Alex mentioned the errors are correctable, so not a serious issue,
but the fact they're being repeatedly logged doesn't
tu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a mem
Hi Seyeong,
Thanks for the debdiffs!
They look good in general but need a few fixes:
1) groovy-proposed has util-linux 2.35.2-9ubuntu1 (debdiff used groovy-
updates / 2.35.2-7ubuntu3)
2) the DEP3 headers should be before a triple-dash "---" line per [1].
I'd suggest moving it to
know if you'd like pointers about the procedure to report
bugs to the Debian Bug Tracking System (BTS).
cheers,
Mauricio
** Changed in: util-linux (Ubuntu Groovy)
Status: In Progress => Confirmed
** Changed in: util-linux (Ubuntu Groovy)
Assignee: Mauricio Faria de Oliveira (
No worries! Thanks for getting back to this bug report. Marking it as
Invalid.
** Changed in: util-linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Patch applied upstream [1].
Next steps are to apply it downstream in Debian and Ubuntu.
[1] https://git.kernel.org/pub/scm/utils/util-linux/util-
linux.git/commit/?id=477239ce0d60384642b51c950688136fdefec815
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
| 2.35.2-5ubuntu3 | groovy | source
** Also affects: util-linux (Ubuntu Groovy)
Importance: Medium
Assignee: Mauricio Faria de Oliveira (mfo)
Status: In Progress
** Also affects: util-linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: util
nux (Ubuntu)
Importance: Undecided => Medium
** Changed in: util-linux (Ubuntu)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18863
Hey Sebastian! Great; thanks for testing!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867916
Title:
Regression in kernel 4.15.0-91 causes kernel panic with Bcache
To manage notifications about
Test kernels with the fix are available in:
https://people.canonical.com/~mfo/lp1867916/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867916
Title:
Regression in kernel 4.15.0-91 causes kernel
[X/B/D/E/F][PATCH 0/1] bcache: fix oops for block size > page size
https://lists.ubuntu.com/archives/kernel-team/2020-July/111846.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867916
Title:
Focal / Testing
=
modified
$ uname -rv
5.4.0-41-generic #45+lp1867916.1 SMP Mon Jul 6 16:41:46 -03 2020
$ sudo make-bcache --bdev $DEV --block 8k
[ 29.593270] bcache: bcache_device_init() bcache0: sb/logical block size
(8192) greater than page size (4096) falling back to device
Xenial / Testing
==
modified
$ uname -rv
4.4.0-186-generic #216+lp1867916.1 SMP Mon Jul 6 18:45:47 -03 2020
$ sudo make-bcache --bdev $DEV --block 8k
[ 60.860259] bcache: bcache_device_init() bcache0: sb/logical block size
(8192) greater than page size (4096) falling back to
Medium
Assignee: Mauricio Faria de Oliveira (mfo)
Status: In Progress
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Importance: Undecide
Bionic / Testing
==
modified
$ uname -rv
4.15.0-110-generic #111+lp1867916.1 SMP Mon Jul 6 19:09:14 -03 2020
$ sudo make-bcache --bdev $DEV --block 8k
[ 22.066760] bcache: bcache_device_init() bcache0: sb/logical block size
(8192) greater than page size (4096) falling back to
Disco / Testing
=
* Using the linux-hwe-5.0 from "Disco" (EOL) on Bionic for the 5.0
kernel.
modified
$ uname -rv
5.0.0-57-generic #61~18.04.1+lp1867916.1 SMP Mon Jul 6 19:27:05 -03 2020
$ sudo make-bcache --bdev $DEV --block 8k
[ 109.818171] bcache: bcache_device_init() bcache0:
Eoan / Testing
modified
$ uname -rv
5.3.0-63-generic #57+lp1867916.1 SMP Mon Jul 6 18:33:27 -03 2020
$ sudo make-bcache --bdev $DEV --block 8k
[ 29.620685] bcache: bcache_device_init() bcache0: sb/logical block size
(8192) greater than page size (4096) falling back to device
Verification done on Eoan.
The apparmor label refcnt inc/dec-rements properly on accept()/release(), no
leaks.
$ lsb_release -cs
eoan
$ uname -rv
5.3.0-63-generic #57-Ubuntu SMP Thu Jul 2 10:38:35 UTC 2020
$ apt-cache policy linux-image-$(uname -r)
linux-image-5.3.0-63-generic:
...
***
This fix has already been released as part of the kernel stable updates.
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Opinion
** Changed in: linux (Ubuntu Xenial)
Status: Opinion => Fix Released
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Fix
Hi Matthew,
This looks like the symptoms of an Intel processor errata,
'Unexpected Page Faults in Guest Virtualization Environment'.
It should be fixed with Intel microcode updates of 2019/11/15.
This has been shipped on Ubuntu intel-microcode package
version 3.20191115.1ubuntu0.18.04.1 for
Bionic: testing
==
original:
$ uname -rv
4.15.0-107-generic #108-Ubuntu SMP Mon Jun 8 17:51:33 UTC 2020
$ ./stress-ng --version
stress-ng, version 0.11.14 (gcc 7.5, x86_64 Linux 4.15.0-107-generic)
$ ./stress-ng --af-alg 0 --timeout 1h
Eoan: testing
original:
$ uname -rv
5.3.0-62-generic #56-Ubuntu SMP Tue Jun 23 11:20:52 UTC 2020
$ ./stress-ng --version
stress-ng, version 0.11.14 (gcc 9.2, x86_64 Linux 5.3.0-62-generic)
$ ./stress-ng --af-alg 0 --timeout 1h 2>&1 | tee
Xenial
==
original:
$ uname -rv
4.4.0-185-generic #215-Ubuntu SMP Mon Jun 8 21:53:19 UTC 2020
$ ./stress-ng --version
stress-ng, version 0.11.14 (gcc 5.4, x86_64 Linux 4.4.0-185-generic)
$ ./stress-ng --af-alg 0 --timeout 30m 2>&1 | tee
Common to all test runs: stress-ng version,
and command to load as many crypto modules
as found/possible in the system.
$ ./stress-ng --version
stress-ng, version 0.11.14 ()
$ sudo modprobe -a \
$(modinfo \
/lib/modules/$(uname -r)/kernel/crypto/*.ko \
[E/F/Unstable][PATCH 0/1] crypto: fix regression/use-after-free in
af_alg_accept()
https://lists.ubuntu.com/archives/kernel-team/2020-June/111620.html
[E/F/Unstable][PATCH 1/1] crypto: af_alg - fix use-after-free in
af_alg_accept() due to bh_lock_sock()
Disco: testing
=
original:
$ uname -rv
5.0.0-38-generic #41-Ubuntu SMP Tue Dec 3 00:27:35 UTC 2019
$ ./stress-ng --version
stress-ng, version 0.11.14 (gcc 8.3, x86_64 Linux 5.0.0-38-generic)
$ ./stress-ng --af-alg 0
Focal: testing
=
$ ./stress-ng --version
stress-ng, version 0.11.14 (gcc 9.3, x86_64 Linux 5.4.0-38-generic)
$ sudo modprobe -a \
$(modinfo \
/lib/modules/$(uname -r)/kernel/crypto/*.ko \
/lib/modules/$(uname -r)/kernel/arch/*/crypto/*.ko \
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
** Changed in: linux (Ubuntu Bionic)
** Description changed:
[Impact]
- * Users of the Linux kernel's crypto userspace API
-reported BUG() / kernel NULL pointer dereference
-errors after kernel upgrades.
+ * Users of the Linux kernel's crypto userspace API
+ reported BUG() / kernel NULL pointer dereference
+
+ SYSC_accept4+0xff/0x210
+ SyS_accept+0x10/0x20
+ do_syscall_64+0x73/0x130
+ entry_SYSCALL_64_after_hwframe+0x3d/0xa2
** Also affects: linux (Ubuntu Groovy)
Importance: Medium
Assignee: Mauricio Faria de Oliveira (mfo)
Status: Confirmed
** Also affects: linux
)
Status: Won't Fix => In Progress
** Changed in: linux (Ubuntu Eoan)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Eoan)
Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)
--
You received this bug notification because you are a member of Ubuntu
Bu
Martin, thanks.
I'll set the bug status to Incomplete for now,
and we can change it if you hit the issue again.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Martin,
Could you please test if the problem still happens with the latest
kernel version in focal-proposed? (currently 5.4.0-40-generic)
Something along these lines,
$ echo 'deb http://archive.ubuntu.com/ubuntu bionic-proposed main restricted' |
sudo tee
: Mauricio Faria de Oliveira (mfo)
Status: Confirmed
** Tags: sts
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Mauricio Faria de Oliv
** Tags added: sts
** Changed in: linux (Ubuntu Groovy)
Status: Won't Fix => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883962
Title:
apparmor reference leak causes refcount_t
[B][PATCH 0/1] Fix apparmor reference leak via AF_ALG
https://lists.ubuntu.com/archives/kernel-team/2020-June/36.html
[B][PATCH 1/1] apparmor: check/put label on apparmor_sk_clone_security()
https://lists.ubuntu.com/archives/kernel-team/2020-June/37.html
[F][PATCH 1/1] apparmor:
After a few hours with the reproducer running on the original kernel,
the kernel errors about the reference count are observed:
Focal:
-
$ uname -rv
5.4.0-38-generic #42-Ubuntu SMP Mon Jun 8 14:14:24 UTC 2020
$ ./aa-refcnt-af_alg
[ 9581.048189] [ cut here ]
[
kprobes module to monitor the apparmor label reference count.
** Attachment added: "kmod.c"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883962/+attachment/5385006/+files/kmod.c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Monitoring the label reference count with the kprobes module:
- original kernel: the counter keeps increasing on every pair of
accept()/release() syscalls.
- modified kernel: the counter keeps stable.
Focal:
-
original)
$ uname -rv
5.4.0-38-generic #42-Ubuntu SMP Mon Jun 8 14:14:24 UTC
Test Case:
-
$ cat aa-refcnt-af_alg.c
#include
#include
#include
#include
#include
int main() {
int sockfd;
struct sockaddr_alg sa;
/* Setup the crypto API socket */
sockfd = socket(AF_ALG, SOCK_SEQPACKET, 0);
if (sockfd < 0) {
perror("socket");
501 - 600 of 1696 matches
Mail list logo
