** Description changed:
[ Impact ]
* Potential data loss with zfs 2.2.0-rc3 resolved in -rc5, proposal to
update to final
* Ubuntu Mantic shipped 2.2.0-rc3 with approximately 10 additional
cherrypicks, or kernel team created fixes that got contributed &
accepted upstream. At
Public bug reported:
Thanks to the zst module compression, the total install size of
modules+modules-extra is now less than modules alone before.
Continuously all interesting pieces of new support for new hardware and
features lands in modules-extra by default, and then we chase those
forever to
> That is at least one less uncomfortable conversation a sw company has
with a potential customer why their server needs to be rebooted for the
company’s SW solution to use a Linux driver.
What software is it? From which company? Is it proprietary or open
source? Can we try and see if it works on
450-server drop in mantic needs lrm respin to drop it
** Summary changed:
- RM: mantic nvidia-graphics-drivers-390 - Remove from the archive,
unmaintained upstream
+ RM: EOL mantic nvidia-graphics-drivers - Remove from the archive,
unmaintained upstream drivers
** Description changed:
This
I thought 390 is so obsolete, that everyone has migrated to newer ones if their
card supports it.
Thus simply removing it, is best.
Upon upgrade it will be offered to be removed from disk as an obsolete package.
Eventually 6.5+ based jammy kernels will not have it in lrm either.
And we will only
No LRMs build this driver in mantic and it can be safely removed from
the archive.
** Summary changed:
- Remove from the archive, unmaintained upstream
+ RM: mantic nvidia-graphics-drivers-390 - Remove from the archive,
unmaintained upstream
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
John Ledkov ]
* Re-enable zfs encryption
* zsys-setup: generate correct zfs-list.cache for target (LP: #1993318)
-- Dimitri John Ledkov Mon, 28 Nov 2022
16:48:59 +
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux
This still sounds like a duplicate of
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1993318 which
was resolved in ubiquity 23.04.1 & 22.04.19
Specifically, systems installed with zfs using ubiquity older than
22.04.19 on jammy; and older than 23.04.1 on any later release, would
produce
Public bug reported:
Kernels now use zstd compressed modules.
dkms autopkgtest was not expecting that correctly.
autopkgtest was adjusted, and uploaded to proposed but did not migrate
prior to feature freeze.
Please unblock dkms to migrate, to resolve all ongoing dkms failures.
The upload in
Public bug reported:
patch kexec code to validate the signature on the vmlinuz instead of
using hmac.
this will eliminate need for kcapi tools certification.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
Public bug reported:
for fips in clouds it is desired to boot without initrd.
add support for doing all the powerup selfchecks from rootfs instead of
initrd.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: fips
--
You received this bug notification
Public bug reported:
make all certified crypto modules built-in
this will simplify our security policy by a lot, as well as self tests
and validation
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: fips
--
You received this bug notification because you
Public bug reported:
make fips=1 default for kernels built with config_fips
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: fips
** Tags added: fips
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux (Ubuntu)
Milestone: None => ubuntu-23.10
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2036968
Title:
Mantic minimized/minimal cloud images do not receive IP
** Changed in: linux-firmware (Ubuntu)
Milestone: None => ubuntu-23.10
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2036742
Title:
amdgpu crash on Mantic
Status in
[4.918050] kernel: UBSAN: array-index-out-of-bounds in /build/linux-
IPoq5q/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3669:4
is not good
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware
In unapproved queue
https://launchpad.net/ubuntu/mantic/+queue?queue_state=1_text=alsa-
ucm-conf
** Changed in: alsa-ucm-conf (Ubuntu Mantic)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
[ Impact ]
* HWE for Raspberry Pi 5 https://raspberrypi.com/5
[ Test Plan ]
* Private builds tested on all existing/supported Raspberry Pi SKUs in
armhf & arm64 variants
* No regressions on any existing SKUs
* Test that Raspberry Pi 5 boards work
[ Where problems
Packages website is unable to search and list things for kernels. This
is because we have too many kernels of similar names with too many
files.
If you navigate to Linux, a given release, given binary name, and check
file listing you will see correct data.
E.g.
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2036968
Title:
Mantic minimized/minimal cloud images do not receive
analysis at https://github.com/canonical/cloud-init/issues/4451
identified systemd regression that is affecting mantic
the kernel workaround is here for virtio-net, but not for all other NIC types,
i.e. e1000
and will likely affect other users too, not just cloud-init use case.
Request to
@mate I agree with that concern w.r.t. sending random pe binaries to
linux code path.
Separately in Mantic we are reverting zimg boot image format. Kernel
itself fails to kexec it correctly. And mantic kexec tools do not
support this image format correctly. Thus at this point grub 2.12 has
best
** Also affects: kdump-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Matching subscriptions: Maintainer
https://bugs.launchpad.net/bugs/2037398
Title:
Unable
** Also affects: kexec-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
Matching subscriptions: Maintainer
https://bugs.launchpad.net/bugs/2037398
Title:
** Changed in: kdump-tools (Ubuntu)
Status: New => Incomplete
** Changed in: kexec-tools (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
$ sudo /tmp/tmp.u3jP6LAlnj/usr/local/sbin/kexec --debug -l -c
/boot/vmlinuz-6.5.0-6-generic
arch_process_options:178: command_line: (null)
arch_process_options:180: initrd: (null)
arch_process_options:182: dtb: (null)
arch_process_options:185: console: (null)
Try gzip decompression.
kernel:
-6 kernel is respun, migration of -7 or higher is good
** Tags removed: block-proposed-mantic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2037398
Title:
kexec enable to
Public bug reported:
nvidia-graphics-drivers-535 lower than in lunar
meaning we need to sru 535.113 into mantic, before turning on upgrades.
** Affects: nvidia-graphics-drivers-535 (Ubuntu)
Importance: Undecided
Status: New
** Affects: ubuntu-release-upgrader (Ubuntu)
** Also affects: broadcom-sta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2013236
Title:
b43 driver conflicts with bcmwl
In Ubuntu we recommend to only install broadcom-sta-dkms.
It ships modprobe.d snippet that does prevent automatic loading of b43 driver.
# cat /etc/modprobe.d/broadcom-sta-dkms.conf
# wl module from Broadcom conflicts with the following modules:
blacklist b43
blacklist b43legacy
blacklist b44
** Changed in: linux (Ubuntu)
Milestone: None => ubuntu-23.10
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2037398
Title:
kexec enable to load/kdump zstd compressed zimg
** Changed in: snapd (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: snapd (Ubuntu Jammy)
Status: Confirmed => Incomplete
** Changed in: zfs-linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubuntu)
Status: New => Fix Released
** Changed in: ubiquity (Ubuntu Jammy)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
https://lists.ubuntu.com/archives/kernel-team/2023-September/143157.html
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Signatures are smaller, and do not use problematic RSA-PKCS#1.5 padding.
(SHA-2 standard) SHA512 is also very problematic, because it has no
protection against length extension attacks anymore.
Upgrade to SHA3-512 as used by snap assertions, and is of the same
length & same
** Changed in: linux (Ubuntu)
Milestone: None => later
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2037741
Title:
Improve kernel module signing strength
Status in linux package
I think the fix is https://github.com/tseliot/ubuntu-drivers-
common/pull/90/files
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2013236
Title:
b43 driver conflicts with bcmwl
** Changed in: linux (Ubuntu Mantic)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2038522
Title:
disable shiftfs
Status in linux package in
Public bug reported:
new bug
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2038528
Title:
testing bot
ubuntu kernel team does not handle which drivers do or do not get
included in the initrd.
Since this is stuff that affects generic, these should be added by
default for modules=most mode by initramfs-tools.
please contact ubuntu foundations team about this.
** Package changed: linux (Ubuntu) =>
note that probe-bcache is just a userspace tool that is called as part
of udev processing devices, and it is fairly simple tool that hardly
does anything when there are no bcache devices. so this does look
suspicious.
** Also affects: bcache-tools (Ubuntu)
Importance: Undecided
Studying this more, this is likely to only affect trying to run
libc6-s390 that is from 18.04 bionic or older. As later versions of
libc6-s390 wrap 64bit syscall, instead of calling 32bit syscall
directly.
However, ideally we would drop all s390 (31 bit) binaries from Ubuntu,
and turn off COMPAT
** Changed in: apparmor (Ubuntu)
Status: Confirmed => Invalid
** Changed in: apparmor (Ubuntu Lunar)
Status: Confirmed => Invalid
** Changed in: maas
Status: Fix Committed => Fix Released
** Changed in: apparmor
Status: Fix Committed => Fix Released
--
You received
Can you please try refresh to channel 23.10/beta or --revision 1474 and
let me know if this improves things?
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received th
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2034688
Title:
installation of kernel headers fail with "Read-only file
Fix under review https://lists.ubuntu.com/archives/kernel-
team/2023-October/146015.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2038567
Title:
Disable restricting unprivileged
** Summary changed:
- Mantic 6.5.0-7 kernel causes regression in LXD container usage
+ Disable restricting unprivileged change_profile by default, due to LXD
latest/snap not yet compatible with this new apparmor feature
** Changed in: lxd (Ubuntu)
Importance: Undecided => High
** Changed
** Changed in: util-linux (Ubuntu Mantic)
Status: New => Triaged
** Changed in: util-linux (Ubuntu Mantic)
Importance: Undecided => Critical
** Changed in: systemd (Ubuntu Mantic)
Status: Confirmed => Incomplete
** Changed in: linux (Ubuntu Mantic)
Status: Incomplete =>
I don't understand the comment about bumblebee as it has a tonne of
alternatives:
# apt show bumblebee-nvidia | grep Depends
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
Depends: bumblebee (= 3.2.1-29), nvidia-driver-binary | nvidia-
driver-525 |
There are partial NBS remains of 440-server in the archive that must be
removed.
** Changed in: bumblebee (Ubuntu)
Status: New => In Progress
** Also affects: nvidia-graphics-drivers-440-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
** Changed in: nvidia-graphics-drivers-418-server (Ubuntu)
Status: Incomplete => New
** Changed in: nvidia-graphics-drivers-450-server (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
@vorlon I don't understand adding bumbleebee to this bug, as I am not
requesting to remove it, and it has many aternative depends. These are
updated in
https://launchpad.net/ubuntu/+source/bumblebee/3.2.1-29ubuntu1 in
proposed.
** Changed in: bumblebee (Ubuntu)
Status: In Progress => Fix
@vorlon you did reverse-depends on the wrong package, -450 & -450-server
are not the same.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/2035189
Title:
RM: EOL
** Description changed:
This legacy driver had the last update on 2022.11.22, and is EOL
upstream. We should remove it from the archive before the next LTS,
maybe even before Mantic is released.
We're planning on migrating the kernel from fbdev drivers to using
simpledrm, but this
libcamera is not shipped on the images, and will be SRUed once tested.
** Changed in: pipewire (Ubuntu)
Status: Triaged => Invalid
** Changed in: libcamera (Ubuntu)
Milestone: None => mantic-updates
--
You received this bug notification because you are a member of Kernel
Packages,
** Changed in: linux (Ubuntu)
Milestone: None => ubuntu-23.10
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Current suspects are out of date apparmor features in livecd-rootfs
pending https://launchpad.net/ubuntu/+source/livecd-rootfs/23.10.55
kernel, apparmor, snapd, lxd, snapd again having fits about all of them
because of:
..
Make
Possibly have to remove NBS first https://ubuntu-archive-
team.ubuntu.com/nbs.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/2035189
Title:
RM: EOL mantic
418-server & 440-server ready to remove from mantic
$ reverse-depends -b src:nvidia-graphics-drivers-418-server
No reverse dependencies found
$ reverse-depends src:nvidia-graphics-drivers-418-server
No reverse dependencies found
$ reverse-depends -b src:nvidia-graphics-drivers-440-server
No
** Also affects: linux-aws (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-gcp (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oracle (Ubuntu)
Importance:
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2038587
Title:
Turning COMPAT_32BIT_TIME off on ppc64el
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2038583
Title:
Turning COMPAT_32BIT_TIME off on s390x
** Changed in: util-linux (Ubuntu Mantic)
Milestone: None => ubuntu-23.10
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: linux-oracle (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-aws (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-gcp (Ubuntu)
Importance:
Public bug reported:
This will prevent existing armhf binaries to operate correctly, if they
are still using 32bit time.
24.04 LTS is likely to be used for 10 years. And if allowed to overrun
and remain active in the field in 2038 can lead to catastrophic failure
in the field due to these
Public bug reported:
This will prevent existing s390 binaries to operate correctly, if they
are still using 32bit time.
24.04 LTS is likely to be used for 10 years. And if allowed to overrun
and remain active in the field in 2038 can lead to catastrophic failure
in the field due to these
Public bug reported:
This will prevent existing armhf binaries to operate correctly, if they
are still using 32bit time.
24.04 LTS is likely to be used for 10 years. And if allowed to overrun
and remain active in the field in 2038 can lead to catastrophic failure
in the field due to these
** Tags added: 32bit-time
** Tags added: y2038
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2038579
Title:
Turning COMPAT_32BIT_TIME off on amd64
Status in linux package in Ubuntu:
Public bug reported:
This will prevent existing 32-bit powerpcle binaries to operate
correctly, if they are still using 32bit time. And even exists?
24.04 LTS is likely to be used for 10 years. And if allowed to overrun
and remain active in the field in 2038 can lead to catastrophic failure
in
** Also affects: linux-ibm (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-intel-iotg (Ubuntu)
Importance: Undecided
Status: New
** Also affects: intel
Importance: Undecided
Status: New
--
You received this bug notification because you are a
Public bug reported:
This will prevent existing i386 binaries to operate correctly, if they
are still using 32bit time.
24.04 LTS is likely to be used for 10 years. And if allowed to overrun
and remain active in the field in 2038 can lead to catastrophic failure
in the field due to these
Public bug reported:
This will prevent (?!) binaries to operate correctly, if they are still
using time32 but maybe riscv32 ABI uses 64-bit time_t anyway?
24.04 LTS is likely to be used for 10 years. And if allowed to overrun
and remain active in the field in 2038 can lead to catastrophic
Consensus from maintainers is that it's a mistake that this option is on
for riscv64, especially since compat is off.
** Also affects: linux-riscv (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-starfive (Ubuntu)
Importance: Undecided
Status: New
** Also
This will notably affect libc6-s390
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2038583
Title:
Turning COMPAT_32BIT_TIME off on s390x
Status in Ubuntu on IBM z Systems:
New
Status
** Changed in: protection-domain-mapper (Ubuntu)
Status: Incomplete => New
** Changed in: qrtr (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to qrtr in Ubuntu.
** Summary changed:
- [MIR] protection-domain-mapper
+ [MIR] protection-domain-mapper & qrtr
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to qrtr in Ubuntu.
https://bugs.launchpad.net/bugs/2038942
Title:
[MIR] protection-domain-mapper
** Description changed:
[Availability]
- The package qrtr is already in Ubuntu universe.
- The package qrtr build for the architectures it is designed to work on.
+ The package protection-domain-mapper is already in Ubuntu universe.
+ The package protection-domain-mapper build for the
dropped some stray todo's from the description
** Description changed:
[Availability]
The package protection-domain-mapper is already in Ubuntu universe.
The package protection-domain-mapper build for the architectures it is
designed to work on.
It currently builds and works for
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because
** Changed in: qrtr (Ubuntu)
Assignee: Dimitri John Ledkov (xnox) => (unassigned)
** Changed in: protection-domain-mapper (Ubuntu)
Assignee: Dimitri John Ledkov (xnox) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages,
#4 Enablement of isolation/hardening features should be considered (e.g. as
part of the systemd service)
#6 Consider putting a condition into the systemd service, to make it run only
when relevant hardware is detected
Addressed in a very strict manner in
#2 The package should get a team bug subscriber before being promoted
kernel-packages team is subscribed to both packages.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to qrtr in Ubuntu.
https://bugs.launchpad.net/bugs/2038942
Title:
https://lore.kernel.org/linux-
crypto/20231022182208.188714-1-dimitri.led...@canonical.com/T/#t
** Description changed:
- Signatures are smaller, and do not use problematic RSA-PKCS#1.5 padding.
+ Currently we use RSA + SHA2-512 for signing.
- (SHA-2 standard) SHA512 is also very problematic,
** Also affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2038582
Title:
Turning COMPAT_32BIT_TIME off on
** Also affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/2038586
Title:
Turning COMPAT_32BIT_TIME off on
I believe reproducer is:
wget
https://images.maas.io/ephemeral-v3/candidate/mantic/amd64/20231004.1/ga-23.10/generic/boot-kernel
wget
https://images.maas.io/ephemeral-v3/candidate/mantic/amd64/20231004.1/ga-23.10/generic/boot-initrd
qemu-system-x86_64 -m 4G -smp 2 -nic
*** This bug is a duplicate of bug 2040181 ***
https://bugs.launchpad.net/bugs/2040181
** This bug has been marked a duplicate of bug 2040181
upgrade zfs-linux to 2.2.0 final
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
I think if linux-headers package produces /usr/src/linux-
headers-4.15.0-219-generic/vmlinux file everything will "just" work for
everybody.
Although stuff might be surprised if it is not a full vmlinux but just
btf info.
But this might even fix generating btf info for dkms modules.
--
You
Separately, please do note that switch from kvm kernel to generic is
resolving the hundreds of bug reports of "works with generic / every
other cloud, doesn't work with kvm". Also note that probably the
baseline comparison shouldn't be the kvm kernel => as we know kvm kernel
has never provided
Is lxd / zfs now installed by default in the minimal images? It seems
like some zfs things are loaded by default.
Also counting processes alone, may or may not increase memory usage.
Example: having N agetty, doesn't actually have memory cost of each
individual agetty, does it?
--
You received
Additionally if something is built into the kernel that is optional at
runtime, and resource intensive, we can make it modularization. But not
sure that will win us anything if it gets autoloaded by default. Thus
maybe some of the things listed should also be blacklisted to prevent
auto-loading on
** Patch removed: "zfs-fix-ubsan-warnings.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2033385/+attachment/5696047/+files/zfs-fix-ubsan-warnings.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in
** Description changed:
[SRU Justfication]
[Impact]
Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress,
and -67 is immune. FW API -64 supported by oem-5.14, and -67 in v5.16.
Not reproducible on every platform with AX211 installed, and the chances
of such
I've picked up the PR into a bileto ppa
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4831
it seems to work for me correctly. If one has MOK dkms key enrolled or
secureboot disabled, one can use zfs-dkms package from the above ppa as
a solution. Please test it and let me know.
I
given how zfs works, to me this is normal and expected.
Also this is expected on btrfs, and on xfs with cow turned on.
zfs is copy on write filesystem, thus calling fallocate to "reserve" a
large amount of free space doesn't make sense. As the created file is
immutable in zfs, and any writes to
However there is now also this:
https://github.com/openzfs/zfs/pull/13338/files
which seems to indicate that my / zfs understanding of the fallocate
kernel flags are not what is done on other filesystems (and expected by
stuff).
If needed, we can look into pulling in
imho, mysql should still gain zfs specific knowledge that doing
fallocate on CoW filesystems doesn't do what one expects it to do.
** Changed in: mysql-8.0 (Ubuntu)
Status: Invalid => Triaged
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug
** Changed in: mysql-8.0 (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969247
Title:
fallocate with FALLOC_FL_ZERO_RANGE produces
Public bug reported:
[Impact]
* Upstream stable point release update with bugfixes, performance
fixes, and newer kernel support as will be needed in the future hwe
kernels.
[Test Plan]
* autopkgtest pass
* kernel regression zfs testsuite pass
* zsys integration test pass
[Where
yeap that's bad.
** Changed in: zfs-linux (Ubuntu)
Status: Confirmed => Triaged
** Changed in: zfs-linux (Ubuntu)
Importance: Wishlist => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
1301 - 1400 of 1812 matches
Mail list logo
