Oops; I missed a refresh before posting my previous comment. Sorry.
The change should address the issue in crash, as /proc/version would be
a substring of a 'Linux version' string in vmlinux.
Marking as Fix Committed.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
** Ch
Andy mentioned this is known and there's a fix in the works (LP bug
unknown at the moment).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/2009595
Title:
DEP8 failure in lunar
Status in
Some options/considerations to address this (need input from the kernel team),
given there might be impact to (other) userspace tools:
1) Make `linux_banner` like `linux_proc_banner`, i.e., append version
signature.
Fixes this issue; expands regression potential to other userspace
tools.)
Perhap
Note: this is not an issue in the more common, dumpfile form (w/ core dump),
since it does not check `/proc/version`.
1) live system form:
$ sudo crash -st ./usr/lib/debug/boot/vmlinux-6.1.0-16-generic
WARNING: ./usr/lib/debug/boot/vmlinux-6.1.0-16-generic
and /proc/version do not match!
GDB session with crash from git.
(gdb) p pc.namelist
$11 = 0x7fffed7f "../usr/lib/debug/boot/vmlinux-6.1.0-16-generic"
(gdb) p kt.proc_version
$12 = "Linux version 6.1.0-16-generic (buildd@lcy02-amd64-014)
(x86_64-linux-gnu-gcc-12 (Ubuntu 12.2.0-14ubuntu2) 12.2.0, GNU ld (GNU Binutils
for U
This is apparently a regression due to (ubuntu-only) kernel commit [1]
commit e9ec6b526c6a ("UBUNTU: SAUCE: (no-up) version: Implement
version_signature proc file.")
It modifies the contents of `/proc/version` by appending a version signature
(available individually in `/proc/version_signature`,
$ git fetch -v
From https://git.savannah.nongnu.org/git/dmidecode
= [up to date]master -> origin/master
$ git log --oneline dmidecode-3-4..origin/master
6ca381c1247c dmidecode: Do not let --dump-bin overwrite an existing file
d8cfbc808f38 dmidecode: Write the whole dump file a
Hi Craig,
Thanks for testing and the details.
> The following command did not work : sudo apt install --allow-
downgrades dmidecode/jammy-updates
Alternatively, you can download/install this deb package, to revert your
instance back to the version in jammy-updates [1].
https://launchpad.net/ubu
Hi Craig,
You can e.g., either download/install/remove the package from Kinetic in
Jammy (its deps work on Jammy) or copy the DMI tables into a Kinetic
container.
Option 1) Kinetic package on Jammy
$ wget
https://launchpad.net/ubuntu/+archive/primary/+files/dmidecode_3.4-1_amd64.deb
$ sudo apt
Hi. Can you please test Kinetic?
It has dmidecode 3.4 which is the latest in Ubuntu, Debian, and upstream
git AFAICT.
Thanks!
** Changed in: dmidecode (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
$ git log --oneline -2 Ubuntu-fips-5.4.0-1060.68..Ubuntu-fips-5.4.0-1061.69 --
drivers/char/random.c
58ce102c669e UBUNTU: SAUCE: random: fallback to CRNG while DRBG is not yet
initialized
9579b4bc92c5 UBUNTU: SAUCE: random: Use Crypto API DRBG for urandom in FIPS mode
$ git log --oneline -2 Ubun
Marking this bug as Fix Released:
The mentioned patch was applied in 5.4.0-1061.69,
and is present is 5.4.0-1068.77 (in fips-updates).
--
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/198148
Hi Hans,
Thanks for the pointer to the synthetic reproducer!
It provided accurate and consistent results considering
the kernel versions reported (not) to exhibit the issue.
The Azure test kernel with the 3 patches [1] to address
that shows the same (good) results as the Azure kernel
prior to th
Hi Ivan,
Yes, I just checked its changelog, which includes commits for this LP
bug number (below).
Thanks!
```
linux (5.4.0-135.152) focal; urgency=medium
* focal/linux: 5.4.0-135.152 -proposed tracker (LP: #1997412)
* containerd sporadic timeouts (LP: #1996678)
- epoll: call final ep
** Changed in: linux (Ubuntu)
Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned)
--
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/1863044
Title:
qla2xxx no longer dete
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
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/1873074
Title:
kernel panic hit by kube-proxy iptables-save/restor
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
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/1884766
Title:
use-after-free in af_alg_accept() due to bh_lock_so
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1883962
Title:
apparmor reference leak causes refcount_t overflo
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu)
Status: Fix Released => Invalid
--
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/1
Verification done on jammy-proposed.
1) a system/hardware vendor tested and confirmed that:
- systems with SMBIOS 3.5 report the new fields as expected;
- systems with SMBIOS < 3.4 keep the old fields as expected.
2) I tested on several physical and virtual machines, and:
- systems with
ack VM
cheers,
Mauricio
** Changed in: dmidecode (Ubuntu Kinetic)
Status: In Progress => Fix Released
** Changed in: dmidecode (Ubuntu Kinetic)
Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned)
** Changed in: dmidecode (Ubuntu Jammy)
Assignee: (unassigned) => Ma
The fix has been released on Xenial ESM (kernel version 4.4.0-224.257).
$ git log --oneline -1 341e4f5e9e07
341e4f5e9e07 UBUNTU: SAUCE: fuse: fix bad !inode in fuse_direntplus_link()
$ git describe --contains 341e4f5e9e07
Ubuntu-4.4.0-224.257~6
** Changed in: linux (Ubuntu Xenial)
Status
Hey Jeremy,
Understood; thanks for clarifying!
I thought that maybe having upstream input could be helpful
(as Julian mentioned to avoid diverging further), but if it
is so much different nowadays, as you mentioned, it likely
won't be that helpful anyway.
By the way, appreciate that "newbie" sta
** Changed in: linux (Ubuntu Focal)
Status: In Progress => 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/1981487
Title:
kernel BUG/Oops errors from modprobe while t
** Patch added: "lp1986852_dmidecode.debdiff"
https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1986852/+attachment/569/+files/lp1986852_dmidecode.debdiff
** Tags added: se-sru-sponsor-mfo
--
You received this bug notification because you are a member of Kernel
Packages, which is
Packages built successfully on supported architectures with
-updates/-proposed on ppa:mfo/build & ppa:mfo/build-proposed.
Uploaded to jammy. Debdiff attached for reference.
** Description changed:
+ [Impact]
+
+ * Support the SMBIOS 3.4 and 3.5 specifications in Jammy
+to enable new hardw
Hi Jeremy,
It seems the PR in rhboot's grub2 hasn't been reviewed yet;
just mentions from other folks who also found it helpful.
Would you consider sending this to the grub-devel list? (i.e., upstream gnu's
grub2)
It looks like it wasn't yet (search results only cover rhboot).
By the way, this
[Focal/FIPS][PATCH v2] UBUNTU: SAUCE: random: fallback to CRNG while DRBG is
not yet initialized
(code-style change)
--
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/1981487
Title:
kernel
The patchset in comment #2
[Focal/FIPS][PATCH 0/4] Fix kernel BUG/Oops errors from modprobe while the
DRBG has not yet initialized (focal/fips-updates)
is now superseded by patch:
[Focal/FIPS][PATCH] UBUNTU: SAUCE: random: fallback to CRNG while DRBG is not
yet initialized
--
You received
** Description changed:
[Impact]
* The Focal FIPS kernel in fips-updates hits kernel BUG/Oops
errors during boot with the FIPS OpenSSL library installed
(but those don't cause issues), when it runs modprobe with
request_module() when looking up crypto algorithms/modules.
** Description changed:
Backport the support for SMBIOS 3.4 and 3.5 specifications
in Ubuntu Kinetic (dmidecode 3.4) to Jammy (dmidecode 3.3)
to enable new hardware in the LTS release per SRU policy [1].
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases
+
+ P.S.: SRU te
(Ubuntu)
Importance: Undecided
Assignee: Mauricio Faria de Oliveira (mfo)
Status: In Progress
** Affects: dmidecode (Ubuntu Jammy)
Importance: Undecided
Status: Invalid
** Affects: dmidecode (Ubuntu Kinetic)
Importance: Undecided
Assignee: Mauricio Faria de
For reference purposes, I'm attaching a dmesg log with debugging boot
options to:
- print initcalls entry/return
- print calls to __request_module() while the FIPS DRBG is uninitialized
Method / boot options:
fips=1
random.fips_urandom_drbg_crypto_noload=0
random.fips_ur
** Description changed:
[Impact]
* The Focal FIPS kernel in fips-updates hits kernel BUG/Oops
errors during boot with the FIPS OpenSSL library installed
(but those don't cause issues), when it runs modprobe with
request_module() when looking up crypto algorithms/modules.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
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/1981487
Title:
kernel BUG/Oops errors from modprobe while the DRBG has n
[Focal/FIPS][PATCH 0/4] Fix kernel BUG/Oops errors from modprobe while
the DRBG has not yet initialized (focal/fips-updates)
--
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/1981487
Title:
(unassigned) => Mauricio Faria de Oliveira (mfo)
** Description changed:
[Impact]
- * The Focal FIPS kernel in fips-updates hits kernel BUG/Oops
-errors during boot with the FIPS OpenSSL library installed
-(but those don't cause issues), when it runs modprobe with
-request_modu
Public bug reported:
[Impact]
* The Focal FIPS kernel in fips-updates hits kernel BUG/Oops
errors during boot with the FIPS OpenSSL library installed
(but those don't cause issues), when it runs modprobe with
request_module() when looking up crypto algorithms/modules.
* The modprob
> So far this has happened only once, hasn't been reproduced with same
nor later kernels.
Ok, thanks.
So, the issue might have happened due a transient hardware condition,
not being reproducible even with the same kernel version.
Let's close this bug, then, as it doesn't seem to be software/kern
Hi Jonathan. Done! That needs some Ubuntu groups/membership.
** Also affects: linux (Ubuntu Bionic)
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/bu
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e0caaf75d443e02e55e146fd75fe2efc8aed5540
commit e0caaf75d443e02e55e146fd75fe2efc8aed5540
Author: Trond Myklebust
Date: Tue Feb 8 13:38:23 2022 -0500
NFS: LOOKUP_DIRECTORY is also ok with symlinks
Commit ac79
Assiging to the linux source package, and marking as confirmed per comment #5.
Thanks for the detailed report and test steps.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notifi
Reassigning to package snapd per ownership of rules file.
$ grep -r 'snap auto-import' /lib/udev/rules.d/
/lib/udev/rules.d/66-snapd-autoimport.rules:3:RUN+="/usr/bin/unshare -m
/usr/bin/snap auto-import --mount=/dev/%k"
$ dpkg -S /lib/udev/rules.d/66-snapd-autoimport.rules
snapd: /lib/udev/
Hi Vincent,
Thanks for the bug report.
> when attaching new volume to host. systemd-udevd trigger
> unshare process to run snap import command on new volumes and it fail.
> volume finally map to host. it doesn't affect volume usage.
> but some udev rule need to check for this strange behavior.
Your attachments came through after I sent last comment.
You could get to a shell in order to run the commands?
CurrentDmesg.txt does show an interesting error (but
it starts in the middle of the flood) going to ext4/
scsi/ata/intel DMA, which is the DMAR handler/thing.
Having messages from befo
Hi Michael,
Thanks for reporting this bug.
We'd need some kernel messages to understand where it's coming from.
It looks like the Gen8 Microserver has iLO / serial console support.
Can you please check whether you can setup a serial console on it?
Then you might need linux kernel option 'consol
Hi Byron,
Thanks for reporting this bug.
Looking at the attached files, they don't seem to have a kernel stack
trace to provide insight about the crash; let's try to get it.
Do you see kernel messages in your monitor when the issue happens, that
you could take a picture and upload?
That might b
*** This bug is a duplicate of bug 1966803 ***
https://bugs.launchpad.net/bugs/1966803
Hey Nemir,
That's great news; thanks for testing!
I'll set this bug as a dup of 1966803.
** This bug has been marked a duplicate of bug 1966803
xfs: Fix deadlock between AGI and AGF when target_ip exis
If you could test 5.4.0-110 that would be nice to confirm whether or not
it's the same issue, and if so, and mark it as duplicate.
Theoretically this might be a different issue also fixed in 5.13.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
No hurry, and thanks.
Yes, the fix is already applied since/in v5.5 and later.
~/git/linux$ git describe --contains 93597ae8dac0149b5c00b787cba6bf7ba213e666
v5.5-rc1~8^2~31
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi Nemir,
Thanks for reporting a bug and the detailed zip file.
Could you please test 5.4.0-100 [1] from focal-proposed? [2]
...
One of the stack traces in your `kernel_trace.txt` file [3]
similarly matches a stack trace from bug 1966803 comment 2 [4]
(from iput() to xfs_buf_lock()) that is fix
Note for other readers / observation:
The kernel/OS in bug description are RHEL 8, not Ubuntu.
[4.18.0-240.el8.x86_64]
But per the comment/link at the end [1] it seems this bug
will be used for a lpfc driver update (fixing that error).
"""
Patches pushed upstream 4/12/22:
https://lore.kernel.or
APPLIED: [SRU][Xenial][PATCH] UBUNTU: SAUCE: fuse: fix bad !inode in
fuse_direntplus_link()
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi Tuomas,
Thanks for the bug report.
What is the kernel version n the previous/successful boot log? (comment
#2)
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
[SRU][Xenial][PATCH] UBUNTU: SAUCE: fuse: fix bad !inode in
fuse_direntplus_link()
--
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/1970482
Title:
Xenial: kernel BUG/Oops/crash in fuse_rea
Analysis:
---
Kernel BUG:
Apr 21 11:39:31 web-12667 kernel: BUG: unable to handle kernel NULL
pointer dereference at 02c0
Apr 21 11:39:31 web-12667 kernel: IP: []
fuse_readdir+0x376/0x700
...
Apr 21 11:39:31 web-12667 kernel: Oops: [#5] SMP
x (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Xenial)
Importance: High
Assignee: Mauricio Faria de Oliveira (mfo)
Status: In Progress
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Also affects: linux (Ubuntu Xenial)
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => New
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu Xenial)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which
For documentation purposes,
(after working on items related to bug 1802021 / 1872021 / this bug)
The stack traces in this issue would suggest a duplicate of bug 1802021,
fixed in kernel 4.15.0-47.50, but this happens in 4.15.0-96, which has
that fix.
So, looking at comments #5 and #6, the issue s
This seems to be a nouveau/nvidia drivers topic.
I'm not a graphics expert, but if I recall correctly,
the opensource `nouveau` driver is usually disabled in
favor of the proprietary `nvidia` drivers, which seem
to work better on the Nvidia cards/gpus.
I can't provide the detailed steps right now
Thanks!
The picture in comment #4 contains the full stack trace.
Some technical analysis for reference. Don't worry about it.
Please see the next comment for suggestions, for now.
...
When returning to userspace from the exit_group() syscall
(as per: orig rax == 0xe7 == 231 -> sys_exit_group; s
Thanks for the bug report.
Can you please upload a picture of the screen during freeze?
We need more information from the 'kernel panic' message.
** Package changed: linux-signed-hwe-5.4 (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received
Verification done for bionic-proposed.
There are no verification steps, but the description shows what to check for:
- It currently doesn't parse the downstream WHENCE.ubuntu file.
- Fix that and cleanup any errors flagged by the checker.
Note: these must be performed on the git repo per dep on
The package in bionic-proposed has been verified by an user
with access to the relevant device; 2 interfaces up/running.
# apt install linux-firmware
...
Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64
linux-firmware all 1.173.21 [74.8 MB]
...
Setting up linux-firmware (1.173.21
https://lists.ubuntu.com/archives/kernel-team/2022-February/128061.html
** Description changed:
[Impact]
- * Missing firmware for Intel ICE driver on Bionic,
-which is supported by the HWE kernel from Focal.
-
+ * Missing firmware for Intel ICE driver on Bionic,
+ which is suppo
Bionic test package:
$ dpkg-deb -c linux-firmware_1.173.20+test20220214b1_all.deb | grep -w ice
drwxr-xr-x root/root 0 2022-02-13 23:10 ./lib/firmware/intel/ice/
drwxr-xr-x root/root 0 2022-02-13 23:10 ./lib/firmware/intel/ice/ddp/
-rw-r--r-- root/root577796 2022-02-13 23:10
x27; on
bugs.lp.net).
** Affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux-firmware (Ubuntu Bionic)
Importance: Medium
Assignee: Mauricio Faria de Oliveira (mfo)
Status: In Progress
** Affects: linux-firmware (Ubuntu Focal)
I
Hey You-Sheng Yang @vicamo,
Friendly poke :) Could you please verify linux-firmware in impish-
proposed?
This verification seems to block the linux-firmware SRU on impish, and
that blocks a larger SRU on focal.
Thanks!
--
You received this bug notification because you are a member of Kernel
Pa
The issue seems to be in subiquity (server installer) not the linux
kernel, per the 'error' screenshot (thanks!)
Marking the subiquity project as affected, and linux as invalid.
** Also affects: subiquity
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: In
Verified bionic, focal, and hirsute (hwe kernel in focal) with steps in
comment #1.
The kernel packages in -updates hit the issue.
The kernel packages in -proposed don't hit it.
ubuntu@mfo-aufs-bionic:~/aufs$ uname -rv
4.15.0-163-generic #171-Ubuntu SMP Fri Nov 5 11:55:11 UTC 2021
ubuntu@mfo-auf
Reviewed and uploaded to Focal. Thanks @joalif!
(debdiff in bug 1942784)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1921403
Title:
makedumpfile does not create dmesg file in /
Reviewed and uploaded to Focal. Thanks @joalif!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1942784
Title:
makedumpfile falls back to cp on focal with 5.11 kernel
Status in ma
Hi Eric,
Answering this as I'm working on it now. :)
Yes, this has been considered and tested by Jo
in the other bug 1942784 comment 7.
Thanks for your attention to the bug/compatibility matrix.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
** Summary changed:
- makedumpfile not properly working on focal with 5.11 kernel
+ makedumpfile falls back to cp on focal with 5.11 kernel
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net
** Description changed:
+ [IMPACT]
- [DESCRIPTION]
makedumpfile does not create the dmesg. in /var/crash.
This happens only on 5.10+ kernel because 5.10 kernel introduces a new
lockless ringbuffer.
+
+ [FIX]
This issue has been addressed upstream with commits :
[1] c617ec633392([P
** Description changed:
[IMPACT]
When running Focal with the hwe 5.11 kernel makedumpfile is not working as it
should.
Instead of compressing the dump makedumpfile falls back to cp.
This can create problems on systems with very large RAM and result into
exhausting all storage on the h
Hey Jo,
Thanks for finding out the real patch/fix,
and testing on the supported architectures!
The debdiff looks good; I'll review/sponsor later!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launch
[H/F/B][PATCH 0/1] aufs: fix kernel bug with apparmor and fuseblk
https://lists.ubuntu.com/archives/kernel-team/2021-October/125163.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/19484
Test with bionic-proposed (4.15.0-162.170)
---
Original:
# ../openat
Killed
[ 442.526300] BUG: unable to handle kernel NULL pointer dereference at
0010
...
[ 442.539854] CPU: 1 PID: 5644 Comm: openat Not tainted 4.15.0-162-generic
#170-Ubuntu
[ 442.540733] Hardware name: QEMU St
Hirsute doesn't ship aufs anymore; no testing needed, just patching.
commit 4fb9ce7538c89f81e3fa5bfae881c9b49e7137e0
Author: Seth Forshee
Date: Fri Feb 19 14:46:24 2021 -0600
UBUNTU: [Config] CONFIG_AUFS_FS=n
We're keeping aufs in the source tree for backports but disabling
it sta
Test with focal-proposed (5.4.0-90.101)
---
Original:
# ../openat
Killed
[ 286.989830] BUG: kernel NULL pointer dereference, address: 0010
...
[ 286.996507] CPU: 2 PID: 5529 Comm: openat Not tainted 5.4.0-90-generic
#101-Ubuntu
[ 286.997358] Hardware name: QEMU Standard PC (i440F
** Description changed:
[Impact]
* AppArmor-enabled applications on the aufs filesystem
might hit a kernel bug when getting file attributes.
* The aufs filesystem explicitly assigns a NULL pointer
to `struct path.mnt` for `vfs_getattr()`, which calls
into AppArmor that
Steps to Reproduce:
1) test app
# cat openat.c
#include
#include
int main() {
int rc;
rc = openat(AT_FDCWD, "test", O_RDWR | O_CREAT | S_IRWXU);
if (rc < 0) {
perror("openat");
? do_sys_open+0x1ba/0x2e0
__x64_sys_openat+0x20/0x30
do_syscall_64+0x5e/0x200
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x4a06fa
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Bionic)
Importance: Low
Assignee: Mauricio Fari
Steps to reproduce:
---
Ubuntu 18.04 image in AWS r5.metal instance type.
$ lsb_release -cs
bionic
$ dmesg | grep DMI:
[0.00] DMI: Amazon EC2 r5.metal/Not Specified, BIOS 1.0 10/16/2017
$ uname -rv
5.4.0-1045-aws #47~18.04.1-Ubuntu SMP Tue Apr 13 15:58:14 UTC 2021
$ sudo add-apt-reposi
** Attachment added: "serial-console-output.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1946149/+attachment/5532619/+files/serial-console-output.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
We've got a serial console log from AWS Support through our Support team
(special thanks to Pedro Principeza and our former colleague Mark Thomas.)
The problem is definitely not the ext4/jbd2 patchset as suspected
(although it's unclear how reverting it caused the kernel to boot;
maybe build envir
Hey Kleber,
Thanks for confirming.
I guess there might be something wrong with the boot process on r5.metal,
specifically:
- there's no issue with kexec boot, just with normal boot (same code and
from/to versions)
- there's no issue with normal boot on similar instance types (r5d.metal,
r5.24x
Hi Kleber,
Thanks for the info.
The impact on bionic/generic is also exclusively on aws r5.metal or
broader?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1946149
Title:
Bionic/li
Ian,
Do you/team have contacts in here or AWS that could help with that?
I think that other lines of investigation now, after our findings
and apparent inconsistencies, would be based on speculation, and
we're better trying to get real information/logs from the system
with AWS Support.
cheers,
M
Today I wanted to try and instrument the boot process a bit,
since we have no serial console in the nitro metal instances.
I was looking for pstore_blk (hoping we could panic_on_warn
or panic_on_oops), but it's only available in 5.8+ it seems.)
So I decided to start with grub, and keep a progress
For the record, 4.15.0-1113-aws works in r5.metal w/ kexec.
Booted it 10 times successfully from both 5.4.0-1058-aws
and 4.15.0-1113-aws (itself.)
(not that it was expected to make a difference as the issue
happens on normal boot, which doesn't have previous kernel.)
Right after that, in the sam
BTW, do you know of the differences between r5.metal and r5.24xlarge?
Per the specs they seem to be the same as in cpu/ram/nic/_nvme_ storage,
but differ in baremetal vs nitro hypervisor?
The reason I ask is because downgrading from 5.4.0-1056-aws to 4.15.0-1113-aws
worked/booted fine on r5.24xla
It looks like it's not a problem with the patchset in general,
maybe it's specific to aws 4.15?
The patchset is in 5.4.0-1058-aws and it booted fine here too.
I'll check the patchset in 4.15.0-1113-aws.
A difference from your comment is that I could _not_ boot it
after 5.4.0-1058-aws, which worke
Hey Ian, thanks for the bug report! I'm checking this on AWS.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1946149
Title:
Bionic/linux-aws Boot failure downgrading from Bionic/linu
Setting tag verification-done-bionic.
Test results with stress-ng: 2420 PASSED, 0 FAILED.
Test results w/ (x)fstests: no regressions in data=ordered and
data=journal (below).
---
Bionic, data=ordered: no regression.
$ ./fstests-check-logs.sh prop-ordered/xfstests.log*
Kernel version: 4.15.0-16
Setting tag verification-done-focal.
Test results with stress-ng: 700 PASSED, 0 FAILED.
Test results w/ (x)fstests: no regressions in data=ordered and
data=journal (below).
---
Focal, data=ordered: no regression.
$ ./fstests-check-logs.sh prop-ordered/xfstests.log*
Kernel version: 5.4.0-89-gen
Just updating the numbers for Focal / Original in comment #9
(the issue did happen more times overnight.)
[ 10.018315] rc.local[744]: 61 FAILED
[ 10.018882] rc.local[744]:1186 PASSED
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
Patches posted for SRU.
[B/F][PATCH 0/5] ext4/jbd2: data=journal: write-protect pages on transaction
commit
https://lists.ubuntu.com/archives/kernel-team/2021-September/123963.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Summary changed:
- ext4 journal recovery fails w/ data=journal + journal_checksum + mmap
+ ext4 journal recovery fails w/ data=journal + mmap
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
101 - 200 of 718 matches
Mail list logo
