** Changed in: linux
Status: New => Fix Released
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2103981
Title:
Mouse cursor flashes using the 'xe' DRM driver
Status in Linux:
Fix Released
Status in Mutter:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Plucky:
Fix Released
Bug description:
Mouse cursor flashes (vanishes) on Intel Lunar Lake, during periods of
slow screen updates like when only a terminal cursor is flashing.
Workaround: xe.enable_psr=0
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2103981/+subscriptions
понедельник
[Bug 2106179] Re: Bluetooth dongle CSR 8510 A10 V5.0 unusable with kernel 6.8.0-57
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2106179
Title:
Bluetooth dongle CSR 8510 A10 V5.0 unusable with kernel 6.8.0-57
Status in linux package in Ubuntu:
Incomplete
Bug description:
bluetooth dongle CSR 8510 A10 V5.0 not seen by blueman and it cannot
be used. Version 6.8.0-51 is OK and I can use it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2106179/+subscriptions
Status: New => Incomplete
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2106179
Title:
Bluetooth dongle CSR 8510 A10 V5.0 unusable with kernel 6.8.0-57
Status in linux package in Ubuntu:
Incomplete
Bug description:
bluetooth dongle CSR 8510 A10 V5.0 not seen by blueman and it cannot
be used. Version 6.8.0-51 is OK and I can use it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2106179/+subscriptions
[Bug 2106352] Re: Audio freezes/loops (UBSAN DAPM errors) on Acer Chromebook 14 (Edgar) / Atom x5-E8000 / RT5650
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2106352
Title:
Audio freezes/loops (UBSAN DAPM errors) on Acer Chromebook 14 (Edgar)
/ Atom x5-E8000 / RT5650
Status in linux package in Ubuntu:
Incomplete
Bug description:
Audio freezes/loops (UBSAN DAPM errors) on Acer Chromebook 14 (Edgar)
/ Atom x5-E8000 / RT5650 (SOF) with Kernel 6.8 / 6.11
Hardware:
System: Acer Chromebook 14 (CB3-431)
Board Name: GOOGLE Edgar (Confirmed via dmidecode)
CPU: Intel(R) Atom(TM) x5-E8000 CPU @ 1.04GHz (Braswell)
Audio Controller: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller [8086:2284] (rev 35) - Driver snd_hda_intel (Handles HDMI - Card 0)
Audio Codec: Realtek RT5650 (Detected by ALSA as sof-bytcht rt5650 - Card 1, uses rt5645 SOF topology sof-cht-rt5645.tplg)
Software:
Distribution: Linux Mint 22.1 "Xia" (Based on Ubuntu 24.04 "Noble Numbat")
Kernel Versions Tested (All Show Issue):
6.8.0-51-generic
6.8.0-57-generic (Currently Active: Linux mintbook 6.8.0-57-generic #59-Ubuntu SMP PREEMPT_DYNAMIC Sat Mar 15 17:40:59 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux)
6.11.0-21-generic
Audio Server: PipeWire 1.0.5 (with WirePlumber session manager)
Problem Description:
Audio output through the internal speakers/headphone jack works
correctly for a short, variable period after booting (ranging from ~1
minute to ~10 minutes). While playing audio (e.g., YouTube in Firefox,
native games like Chocolate Doom), the sound suddenly cuts out and is
often replaced by a continuous, loud looping beep/tone.
Sometimes, closing the application that was playing audio causes the
looping sound to stop after several seconds, and system audio may
function again temporarily before freezing again shortly after. The
issue occurs reliably across all tested kernels available in the Linux
Mint 22.1 repositories (6.8 series, 6.11 series).
Key Evidence (Kernel Log Errors):
During boot, the kernel logs consistently show errors related to the
Realtek codec detection and, critically, UBSAN (Undefined Behavior
Sanitizer) errors within the ALSA core's DAPM (Dynamic Audio Power
Management) code during the initialization of the SOF sound card.
These errors strongly suggest a kernel bug is the root cause of the
instability.
Key Evidence (Kernel Log Errors):
During boot, the kernel logs consistently show errors related to the
Realtek codec detection and, critically, UBSAN (Undefined Behavior
Sanitizer) errors within the ALSA core's DAPM (Dynamic Audio Power
Management) code during the initialization of the SOF sound card.
These errors strongly suggest a kernel bug is the root cause of the
instability.
Relevant logs from dmesg on kernel 6.8.0-57-generic:
[ 11.222920] rt5640 i2c-10EC5650:00: Device with ID register 0x6419 is not rt5640/39
[ 11.830233] rt5645 i2c-10EC5650:00: Detected Google Chrome platform
[ 12.102210] sof-audio-acpi-intel-byt 808622A8:00: unknown sof_ext_man header type 3 size 0x30
[ 12.735442] UBSAN: shift-out-of-bounds in /build/linux-AUvUe4/linux-6.8.0/sound/soc/soc-dapm.c:814:15
[ 12.735535] snd_soc_dapm_add_path.cold+0x1b/0x5c [snd_soc_core]
[ 12.735615] snd_soc_dapm_add_route+0x313/0x600 [snd_soc_core]
[ 12.735688] snd_soc_dapm_add_routes+0x45/0x80 [snd_soc_core]
[ 12.735753] soc_probe_component+0x265/0x390 [snd_soc_core]
[ 12.735815] snd_soc_bind_card+0x3c1/0x8c0 [snd_soc_core]
[ 12.735876] ? __pfx_devm_card_release+0x10/0x10 [snd_soc_core]
[ 12.735943] snd_soc_register_card+0x145/0x170 [snd_soc_core]
[ 12.736004] devm_snd_soc_register_card+0x48/0xb0 [snd_soc_core]
[ 12.736071] snd_cht_mc_probe+0x49b/0x830 [snd_soc_sst_cht_bsw_rt5645]
[ 12.736173] ? __pfx_snd_cht_mc_driver_init+0x10/0x10 [snd_soc_sst_cht_bsw_rt5645]
[ 12.736189] snd_cht_mc_driver_init+0x1c/0xff0 [snd_soc_sst_cht_bsw_rt5645]
[ 13.022618] UBSAN: shift-out-of-bounds in /build/linux-AUvUe4/linux-6.8.0/sound/soc/soc-dapm.c:3427:13
[ 13.022710] snd_soc_dapm_put_volsw.cold+0x94/0x131 [snd_soc_core]
[ 13.022797] snd_ctl_elem_write+0x109/0x1c0 [snd]
[ 13.022828] snd_ctl_ioctl+0x4a5/0x730 [snd]
[ 13.023098] UBSAN: shift-out-of-bounds in /build/linux-AUvUe4/linux-6.8.0/sound/soc/soc-dapm.c:3428:15
[ 13.023150] snd_soc_dapm_put_volsw.cold+0x127/0x131 [snd_soc_core]
[ 13.023220] snd_ctl_elem_write+0x109/0x1c0 [snd]
[ 13.023248] snd_ctl_ioctl+0x4a5/0x730 [snd]
[ 13.023516] UBSAN: shift-out-of-bounds in /build/linux-AUvUe4/linux-6.8.0/sound/soc/soc-dapm.c:3430:51
[ 13.023571] snd_soc_dapm_put_volsw.cold+0xba/0x131 [snd_soc_core]
[ 13.023643] snd_ctl_elem_write+0x109/0x1c0 [snd]
[ 13.023672] snd_ctl_ioctl+0x4a5/0x730 [snd]
Troubleshooting Steps Attempted:
Tested multiple kernels available via Linux Mint Update Manager (6.8.0-51, 6.8.0-57, 6.11.0-21) - Problem persists on all.
Attempted disabling power saving for snd_hda_intel via modprobe.d - Ineffective (targets wrong driver component). Power save parameter for snd_sof module not found.
Attempted forcing legacy audio driver via kernel parameter snd_intel_dspcfg.dsp_driver=1 - Problem persists.
Checked ALSA / PipeWire / WirePlumber configurations - Appear standard (no custom user configs found).
Problem occurs with different applications (Firefox/YouTube, Chocolate Doom).
Expected Result: Audio playback should be stable without freezes or
looping sounds.
Actual Result: Audio freezes and often loops after short periods of
use, associated with kernel DAPM errors during initialization.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2106352/+subscriptions
Status: Confirmed => Incomplete
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2106352
Title:
Audio freezes/loops (UBSAN DAPM errors) on Acer Chromebook 14 (Edgar)
/ Atom x5-E8000 / RT5650
Status in linux package in Ubuntu:
Incomplete
Bug description:
Audio freezes/loops (UBSAN DAPM errors) on Acer Chromebook 14 (Edgar)
/ Atom x5-E8000 / RT5650 (SOF) with Kernel 6.8 / 6.11
Hardware:
System: Acer Chromebook 14 (CB3-431)
Board Name: GOOGLE Edgar (Confirmed via dmidecode)
CPU: Intel(R) Atom(TM) x5-E8000 CPU @ 1.04GHz (Braswell)
Audio Controller: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller [8086:2284] (rev 35) - Driver snd_hda_intel (Handles HDMI - Card 0)
Audio Codec: Realtek RT5650 (Detected by ALSA as sof-bytcht rt5650 - Card 1, uses rt5645 SOF topology sof-cht-rt5645.tplg)
Software:
Distribution: Linux Mint 22.1 "Xia" (Based on Ubuntu 24.04 "Noble Numbat")
Kernel Versions Tested (All Show Issue):
6.8.0-51-generic
6.8.0-57-generic (Currently Active: Linux mintbook 6.8.0-57-generic #59-Ubuntu SMP PREEMPT_DYNAMIC Sat Mar 15 17:40:59 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux)
6.11.0-21-generic
Audio Server: PipeWire 1.0.5 (with WirePlumber session manager)
Problem Description:
Audio output through the internal speakers/headphone jack works
correctly for a short, variable period after booting (ranging from ~1
minute to ~10 minutes). While playing audio (e.g., YouTube in Firefox,
native games like Chocolate Doom), the sound suddenly cuts out and is
often replaced by a continuous, loud looping beep/tone.
Sometimes, closing the application that was playing audio causes the
looping sound to stop after several seconds, and system audio may
function again temporarily before freezing again shortly after. The
issue occurs reliably across all tested kernels available in the Linux
Mint 22.1 repositories (6.8 series, 6.11 series).
Key Evidence (Kernel Log Errors):
During boot, the kernel logs consistently show errors related to the
Realtek codec detection and, critically, UBSAN (Undefined Behavior
Sanitizer) errors within the ALSA core's DAPM (Dynamic Audio Power
Management) code during the initialization of the SOF sound card.
These errors strongly suggest a kernel bug is the root cause of the
instability.
Key Evidence (Kernel Log Errors):
During boot, the kernel logs consistently show errors related to the
Realtek codec detection and, critically, UBSAN (Undefined Behavior
Sanitizer) errors within the ALSA core's DAPM (Dynamic Audio Power
Management) code during the initialization of the SOF sound card.
These errors strongly suggest a kernel bug is the root cause of the
instability.
Relevant logs from dmesg on kernel 6.8.0-57-generic:
[ 11.222920] rt5640 i2c-10EC5650:00: Device with ID register 0x6419 is not rt5640/39
[ 11.830233] rt5645 i2c-10EC5650:00: Detected Google Chrome platform
[ 12.102210] sof-audio-acpi-intel-byt 808622A8:00: unknown sof_ext_man header type 3 size 0x30
[ 12.735442] UBSAN: shift-out-of-bounds in /build/linux-AUvUe4/linux-6.8.0/sound/soc/soc-dapm.c:814:15
[ 12.735535] snd_soc_dapm_add_path.cold+0x1b/0x5c [snd_soc_core]
[ 12.735615] snd_soc_dapm_add_route+0x313/0x600 [snd_soc_core]
[ 12.735688] snd_soc_dapm_add_routes+0x45/0x80 [snd_soc_core]
[ 12.735753] soc_probe_component+0x265/0x390 [snd_soc_core]
[ 12.735815] snd_soc_bind_card+0x3c1/0x8c0 [snd_soc_core]
[ 12.735876] ? __pfx_devm_card_release+0x10/0x10 [snd_soc_core]
[ 12.735943] snd_soc_register_card+0x145/0x170 [snd_soc_core]
[ 12.736004] devm_snd_soc_register_card+0x48/0xb0 [snd_soc_core]
[ 12.736071] snd_cht_mc_probe+0x49b/0x830 [snd_soc_sst_cht_bsw_rt5645]
[ 12.736173] ? __pfx_snd_cht_mc_driver_init+0x10/0x10 [snd_soc_sst_cht_bsw_rt5645]
[ 12.736189] snd_cht_mc_driver_init+0x1c/0xff0 [snd_soc_sst_cht_bsw_rt5645]
[ 13.022618] UBSAN: shift-out-of-bounds in /build/linux-AUvUe4/linux-6.8.0/sound/soc/soc-dapm.c:3427:13
[ 13.022710] snd_soc_dapm_put_volsw.cold+0x94/0x131 [snd_soc_core]
[ 13.022797] snd_ctl_elem_write+0x109/0x1c0 [snd]
[ 13.022828] snd_ctl_ioctl+0x4a5/0x730 [snd]
[ 13.023098] UBSAN: shift-out-of-bounds in /build/linux-AUvUe4/linux-6.8.0/sound/soc/soc-dapm.c:3428:15
[ 13.023150] snd_soc_dapm_put_volsw.cold+0x127/0x131 [snd_soc_core]
[ 13.023220] snd_ctl_elem_write+0x109/0x1c0 [snd]
[ 13.023248] snd_ctl_ioctl+0x4a5/0x730 [snd]
[ 13.023516] UBSAN: shift-out-of-bounds in /build/linux-AUvUe4/linux-6.8.0/sound/soc/soc-dapm.c:3430:51
[ 13.023571] snd_soc_dapm_put_volsw.cold+0xba/0x131 [snd_soc_core]
[ 13.023643] snd_ctl_elem_write+0x109/0x1c0 [snd]
[ 13.023672] snd_ctl_ioctl+0x4a5/0x730 [snd]
Troubleshooting Steps Attempted:
Tested multiple kernels available via Linux Mint Update Manager (6.8.0-51, 6.8.0-57, 6.11.0-21) - Problem persists on all.
Attempted disabling power saving for snd_hda_intel via modprobe.d - Ineffective (targets wrong driver component). Power save parameter for snd_sof module not found.
Attempted forcing legacy audio driver via kernel parameter snd_intel_dspcfg.dsp_driver=1 - Problem persists.
Checked ALSA / PipeWire / WirePlumber configurations - Appear standard (no custom user configs found).
Problem occurs with different applications (Firefox/YouTube, Chocolate Doom).
Expected Result: Audio playback should be stable without freezes or
looping sounds.
Actual Result: Audio freezes and often loops after short periods of
use, associated with kernel DAPM errors during initialization.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2106352/+subscriptions
[Bug 2106352] Re: Audio freezes/loops (UBSAN DAPM errors) on Acer Chromebook 14 (Edgar) / Atom x5-E8000 / RT5650
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2106352
Title:
Audio freezes/loops (UBSAN DAPM errors) on Acer Chromebook 14 (Edgar)
/ Atom x5-E8000 / RT5650
Status in linux package in Ubuntu:
Incomplete
Bug description:
Audio freezes/loops (UBSAN DAPM errors) on Acer Chromebook 14 (Edgar)
/ Atom x5-E8000 / RT5650 (SOF) with Kernel 6.8 / 6.11
Hardware:
System: Acer Chromebook 14 (CB3-431)
Board Name: GOOGLE Edgar (Confirmed via dmidecode)
CPU: Intel(R) Atom(TM) x5-E8000 CPU @ 1.04GHz (Braswell)
Audio Controller: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller [8086:2284] (rev 35) - Driver snd_hda_intel (Handles HDMI - Card 0)
Audio Codec: Realtek RT5650 (Detected by ALSA as sof-bytcht rt5650 - Card 1, uses rt5645 SOF topology sof-cht-rt5645.tplg)
Software:
Distribution: Linux Mint 22.1 "Xia" (Based on Ubuntu 24.04 "Noble Numbat")
Kernel Versions Tested (All Show Issue):
6.8.0-51-generic
6.8.0-57-generic (Currently Active: Linux mintbook 6.8.0-57-generic #59-Ubuntu SMP PREEMPT_DYNAMIC Sat Mar 15 17:40:59 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux)
6.11.0-21-generic
Audio Server: PipeWire 1.0.5 (with WirePlumber session manager)
Problem Description:
Audio output through the internal speakers/headphone jack works
correctly for a short, variable period after booting (ranging from ~1
minute to ~10 minutes). While playing audio (e.g., YouTube in Firefox,
native games like Chocolate Doom), the sound suddenly cuts out and is
often replaced by a continuous, loud looping beep/tone.
Sometimes, closing the application that was playing audio causes the
looping sound to stop after several seconds, and system audio may
function again temporarily before freezing again shortly after. The
issue occurs reliably across all tested kernels available in the Linux
Mint 22.1 repositories (6.8 series, 6.11 series).
Key Evidence (Kernel Log Errors):
During boot, the kernel logs consistently show errors related to the
Realtek codec detection and, critically, UBSAN (Undefined Behavior
Sanitizer) errors within the ALSA core's DAPM (Dynamic Audio Power
Management) code during the initialization of the SOF sound card.
These errors strongly suggest a kernel bug is the root cause of the
instability.
Key Evidence (Kernel Log Errors):
During boot, the kernel logs consistently show errors related to the
Realtek codec detection and, critically, UBSAN (Undefined Behavior
Sanitizer) errors within the ALSA core's DAPM (Dynamic Audio Power
Management) code during the initialization of the SOF sound card.
These errors strongly suggest a kernel bug is the root cause of the
instability.
Relevant logs from dmesg on kernel 6.8.0-57-generic:
[ 11.222920] rt5640 i2c-10EC5650:00: Device with ID register 0x6419 is not rt5640/39
[ 11.830233] rt5645 i2c-10EC5650:00: Detected Google Chrome platform
[ 12.102210] sof-audio-acpi-intel-byt 808622A8:00: unknown sof_ext_man header type 3 size 0x30
[ 12.735442] UBSAN: shift-out-of-bounds in /build/linux-AUvUe4/linux-6.8.0/sound/soc/soc-dapm.c:814:15
[ 12.735535] snd_soc_dapm_add_path.cold+0x1b/0x5c [snd_soc_core]
[ 12.735615] snd_soc_dapm_add_route+0x313/0x600 [snd_soc_core]
[ 12.735688] snd_soc_dapm_add_routes+0x45/0x80 [snd_soc_core]
[ 12.735753] soc_probe_component+0x265/0x390 [snd_soc_core]
[ 12.735815] snd_soc_bind_card+0x3c1/0x8c0 [snd_soc_core]
[ 12.735876] ? __pfx_devm_card_release+0x10/0x10 [snd_soc_core]
[ 12.735943] snd_soc_register_card+0x145/0x170 [snd_soc_core]
[ 12.736004] devm_snd_soc_register_card+0x48/0xb0 [snd_soc_core]
[ 12.736071] snd_cht_mc_probe+0x49b/0x830 [snd_soc_sst_cht_bsw_rt5645]
[ 12.736173] ? __pfx_snd_cht_mc_driver_init+0x10/0x10 [snd_soc_sst_cht_bsw_rt5645]
[ 12.736189] snd_cht_mc_driver_init+0x1c/0xff0 [snd_soc_sst_cht_bsw_rt5645]
[ 13.022618] UBSAN: shift-out-of-bounds in /build/linux-AUvUe4/linux-6.8.0/sound/soc/soc-dapm.c:3427:13
[ 13.022710] snd_soc_dapm_put_volsw.cold+0x94/0x131 [snd_soc_core]
[ 13.022797] snd_ctl_elem_write+0x109/0x1c0 [snd]
[ 13.022828] snd_ctl_ioctl+0x4a5/0x730 [snd]
[ 13.023098] UBSAN: shift-out-of-bounds in /build/linux-AUvUe4/linux-6.8.0/sound/soc/soc-dapm.c:3428:15
[ 13.023150] snd_soc_dapm_put_volsw.cold+0x127/0x131 [snd_soc_core]
[ 13.023220] snd_ctl_elem_write+0x109/0x1c0 [snd]
[ 13.023248] snd_ctl_ioctl+0x4a5/0x730 [snd]
[ 13.023516] UBSAN: shift-out-of-bounds in /build/linux-AUvUe4/linux-6.8.0/sound/soc/soc-dapm.c:3430:51
[ 13.023571] snd_soc_dapm_put_volsw.cold+0xba/0x131 [snd_soc_core]
[ 13.023643] snd_ctl_elem_write+0x109/0x1c0 [snd]
[ 13.023672] snd_ctl_ioctl+0x4a5/0x730 [snd]
Troubleshooting Steps Attempted:
Tested multiple kernels available via Linux Mint Update Manager (6.8.0-51, 6.8.0-57, 6.11.0-21) - Problem persists on all.
Attempted disabling power saving for snd_hda_intel via modprobe.d - Ineffective (targets wrong driver component). Power save parameter for snd_sof module not found.
Attempted forcing legacy audio driver via kernel parameter snd_intel_dspcfg.dsp_driver=1 - Problem persists.
Checked ALSA / PipeWire / WirePlumber configurations - Appear standard (no custom user configs found).
Problem occurs with different applications (Firefox/YouTube, Chocolate Doom).
Expected Result: Audio playback should be stable without freezes or
looping sounds.
Actual Result: Audio freezes and often loops after short periods of
use, associated with kernel DAPM errors during initialization.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2106352/+subscriptions
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2106352
Title:
Audio freezes/loops (UBSAN DAPM errors) on Acer Chromebook 14 (Edgar)
/ Atom x5-E8000 / RT5650
Status in linux package in Ubuntu:
Incomplete
Bug description:
Audio freezes/loops (UBSAN DAPM errors) on Acer Chromebook 14 (Edgar)
/ Atom x5-E8000 / RT5650 (SOF) with Kernel 6.8 / 6.11
Hardware:
System: Acer Chromebook 14 (CB3-431)
Board Name: GOOGLE Edgar (Confirmed via dmidecode)
CPU: Intel(R) Atom(TM) x5-E8000 CPU @ 1.04GHz (Braswell)
Audio Controller: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller [8086:2284] (rev 35) - Driver snd_hda_intel (Handles HDMI - Card 0)
Audio Codec: Realtek RT5650 (Detected by ALSA as sof-bytcht rt5650 - Card 1, uses rt5645 SOF topology sof-cht-rt5645.tplg)
Software:
Distribution: Linux Mint 22.1 "Xia" (Based on Ubuntu 24.04 "Noble Numbat")
Kernel Versions Tested (All Show Issue):
6.8.0-51-generic
6.8.0-57-generic (Currently Active: Linux mintbook 6.8.0-57-generic #59-Ubuntu SMP PREEMPT_DYNAMIC Sat Mar 15 17:40:59 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux)
6.11.0-21-generic
Audio Server: PipeWire 1.0.5 (with WirePlumber session manager)
Problem Description:
Audio output through the internal speakers/headphone jack works
correctly for a short, variable period after booting (ranging from ~1
minute to ~10 minutes). While playing audio (e.g., YouTube in Firefox,
native games like Chocolate Doom), the sound suddenly cuts out and is
often replaced by a continuous, loud looping beep/tone.
Sometimes, closing the application that was playing audio causes the
looping sound to stop after several seconds, and system audio may
function again temporarily before freezing again shortly after. The
issue occurs reliably across all tested kernels available in the Linux
Mint 22.1 repositories (6.8 series, 6.11 series).
Key Evidence (Kernel Log Errors):
During boot, the kernel logs consistently show errors related to the
Realtek codec detection and, critically, UBSAN (Undefined Behavior
Sanitizer) errors within the ALSA core's DAPM (Dynamic Audio Power
Management) code during the initialization of the SOF sound card.
These errors strongly suggest a kernel bug is the root cause of the
instability.
Key Evidence (Kernel Log Errors):
During boot, the kernel logs consistently show errors related to the
Realtek codec detection and, critically, UBSAN (Undefined Behavior
Sanitizer) errors within the ALSA core's DAPM (Dynamic Audio Power
Management) code during the initialization of the SOF sound card.
These errors strongly suggest a kernel bug is the root cause of the
instability.
Relevant logs from dmesg on kernel 6.8.0-57-generic:
[ 11.222920] rt5640 i2c-10EC5650:00: Device with ID register 0x6419 is not rt5640/39
[ 11.830233] rt5645 i2c-10EC5650:00: Detected Google Chrome platform
[ 12.102210] sof-audio-acpi-intel-byt 808622A8:00: unknown sof_ext_man header type 3 size 0x30
[ 12.735442] UBSAN: shift-out-of-bounds in /build/linux-AUvUe4/linux-6.8.0/sound/soc/soc-dapm.c:814:15
[ 12.735535] snd_soc_dapm_add_path.cold+0x1b/0x5c [snd_soc_core]
[ 12.735615] snd_soc_dapm_add_route+0x313/0x600 [snd_soc_core]
[ 12.735688] snd_soc_dapm_add_routes+0x45/0x80 [snd_soc_core]
[ 12.735753] soc_probe_component+0x265/0x390 [snd_soc_core]
[ 12.735815] snd_soc_bind_card+0x3c1/0x8c0 [snd_soc_core]
[ 12.735876] ? __pfx_devm_card_release+0x10/0x10 [snd_soc_core]
[ 12.735943] snd_soc_register_card+0x145/0x170 [snd_soc_core]
[ 12.736004] devm_snd_soc_register_card+0x48/0xb0 [snd_soc_core]
[ 12.736071] snd_cht_mc_probe+0x49b/0x830 [snd_soc_sst_cht_bsw_rt5645]
[ 12.736173] ? __pfx_snd_cht_mc_driver_init+0x10/0x10 [snd_soc_sst_cht_bsw_rt5645]
[ 12.736189] snd_cht_mc_driver_init+0x1c/0xff0 [snd_soc_sst_cht_bsw_rt5645]
[ 13.022618] UBSAN: shift-out-of-bounds in /build/linux-AUvUe4/linux-6.8.0/sound/soc/soc-dapm.c:3427:13
[ 13.022710] snd_soc_dapm_put_volsw.cold+0x94/0x131 [snd_soc_core]
[ 13.022797] snd_ctl_elem_write+0x109/0x1c0 [snd]
[ 13.022828] snd_ctl_ioctl+0x4a5/0x730 [snd]
[ 13.023098] UBSAN: shift-out-of-bounds in /build/linux-AUvUe4/linux-6.8.0/sound/soc/soc-dapm.c:3428:15
[ 13.023150] snd_soc_dapm_put_volsw.cold+0x127/0x131 [snd_soc_core]
[ 13.023220] snd_ctl_elem_write+0x109/0x1c0 [snd]
[ 13.023248] snd_ctl_ioctl+0x4a5/0x730 [snd]
[ 13.023516] UBSAN: shift-out-of-bounds in /build/linux-AUvUe4/linux-6.8.0/sound/soc/soc-dapm.c:3430:51
[ 13.023571] snd_soc_dapm_put_volsw.cold+0xba/0x131 [snd_soc_core]
[ 13.023643] snd_ctl_elem_write+0x109/0x1c0 [snd]
[ 13.023672] snd_ctl_ioctl+0x4a5/0x730 [snd]
Troubleshooting Steps Attempted:
Tested multiple kernels available via Linux Mint Update Manager (6.8.0-51, 6.8.0-57, 6.11.0-21) - Problem persists on all.
Attempted disabling power saving for snd_hda_intel via modprobe.d - Ineffective (targets wrong driver component). Power save parameter for snd_sof module not found.
Attempted forcing legacy audio driver via kernel parameter snd_intel_dspcfg.dsp_driver=1 - Problem persists.
Checked ALSA / PipeWire / WirePlumber configurations - Appear standard (no custom user configs found).
Problem occurs with different applications (Firefox/YouTube, Chocolate Doom).
Expected Result: Audio playback should be stable without freezes or
looping sounds.
Actual Result: Audio freezes and often loops after short periods of
use, associated with kernel DAPM errors during initialization.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2106352/+subscriptions
[Bug 2104297] Re: not able to install a Power9 bare metal with Ubuntu 25.04 Plucky
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: ubuntu-power-systems
Status: In Progress => Fix Committed
** Also affects: linux (Ubuntu Plucky)
Importance: Critical
Assignee: Massimiliano Pellizzer (mpellizzer)
Status: Fix Committed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2104297
Title:
not able to install a Power9 bare metal with Ubuntu 25.04 Plucky
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Plucky:
Fix Committed
Bug description:
[ Impact ]
In ppc64el kernels, loading modules without any
__patchable_function_entries section would fail due to a
zero size allocation of executable memory for ftrace trampolines.
This causes boot failures when trying to boot the kernel on IBM Power 9
systems. In particular becasue IBM Power 9 tries to load i40e at boot
time, which fails.
The bug was introduced by commit eec37961a56a which landed in v6.13-rc1,
which assumed all modules have traceable functions.
[ Fix ]
Apply the following patch:
- https://lore.kernel.org/all/wlscshbqan2svtqkz5xc6v47tzndfnsvge7h4lbfn67zoplekl@elt2oxwhrp6f/T/
which has not landed in linux-next yet.
[ Test Plan ]
Compile and boot test the kernel on a Power 9 bare metal machine.
[ Where problems could occur ]
The patch simply removes an if branch which handles (incorrectly) errors during
module loading on ppc64 systems. The regression potential therefore is
very low.
-----
Not able to netboot install a Power9 bare metal. It fails because it
is not detecting network, after that the system goes to shell/busybox
```
Begin: Waiting up to 180 secs for any network device to become available ... Failure: Network device did not appear in time
done.
dhcpcd-10.1.0 starting
dev: loaded udev
[ 188.277865] 8021q: 802.1Q VLAN Support v1.8
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
Sleeping 30 seconds before retrying getting a DHCP lease
dhcpcd-10.1.0 starting
dev: loaded udev
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
dhcpcd exited
Sleeping 60 seconds before retrying getting a DHCP lease
dhcpcd-10.1.0 starting
dev: loaded udev
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
dhcpcd exited
Sleeping 90 seconds before retrying getting a DHCP lease
dhcpcd-10.1.0 starting
dev: loaded udev
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
dhcpcd exited
Sleeping 120 seconds before retrying getting a DHCP lease
BusyBox v1.37.0 (Ubuntu 1:1.37.0-4ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2104297/+subscriptions
Status: In Progress => Fix Committed
** Changed in: ubuntu-power-systems
Status: In Progress => Fix Committed
** Also affects: linux (Ubuntu Plucky)
Importance: Critical
Assignee: Massimiliano Pellizzer (mpellizzer)
Status: Fix Committed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2104297
Title:
not able to install a Power9 bare metal with Ubuntu 25.04 Plucky
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Plucky:
Fix Committed
Bug description:
[ Impact ]
In ppc64el kernels, loading modules without any
__patchable_function_entries section would fail due to a
zero size allocation of executable memory for ftrace trampolines.
This causes boot failures when trying to boot the kernel on IBM Power 9
systems. In particular becasue IBM Power 9 tries to load i40e at boot
time, which fails.
The bug was introduced by commit eec37961a56a which landed in v6.13-rc1,
which assumed all modules have traceable functions.
[ Fix ]
Apply the following patch:
- https://lore.kernel.org/all/wlscshbqan2svtqkz5xc6v47tzndfnsvge7h4lbfn67zoplekl@elt2oxwhrp6f/T/
which has not landed in linux-next yet.
[ Test Plan ]
Compile and boot test the kernel on a Power 9 bare metal machine.
[ Where problems could occur ]
The patch simply removes an if branch which handles (incorrectly) errors during
module loading on ppc64 systems. The regression potential therefore is
very low.
-----
Not able to netboot install a Power9 bare metal. It fails because it
is not detecting network, after that the system goes to shell/busybox
```
Begin: Waiting up to 180 secs for any network device to become available ... Failure: Network device did not appear in time
done.
dhcpcd-10.1.0 starting
dev: loaded udev
[ 188.277865] 8021q: 802.1Q VLAN Support v1.8
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
Sleeping 30 seconds before retrying getting a DHCP lease
dhcpcd-10.1.0 starting
dev: loaded udev
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
dhcpcd exited
Sleeping 60 seconds before retrying getting a DHCP lease
dhcpcd-10.1.0 starting
dev: loaded udev
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
dhcpcd exited
Sleeping 90 seconds before retrying getting a DHCP lease
dhcpcd-10.1.0 starting
dev: loaded udev
no valid interfaces found
exiting due to oneshot
aborting as link detection is disabled
dhcpcd exited
Sleeping 120 seconds before retrying getting a DHCP lease
BusyBox v1.37.0 (Ubuntu 1:1.37.0-4ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2104297/+subscriptions
[Bug 2106279] Re: /usr/lib/modules empty after 24.04.2 upgrade
FDE is experimental. You shouldn't use it if this concerns you.
** Package changed: linux (Ubuntu) => canonical-kernel-snaps
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2106279
Title:
/usr/lib/modules empty after 24.04.2 upgrade
Status in canonical-kernel-snaps:
New
Bug description:
See https://discourse.ubuntu.com/t/no-networking-after-some-upgrade-
on-24-04-2-on-a-framework-16-late-2024-setup-with-secure-boot-the-tpm-
for-fde/58387
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-54-generic (not installed)
ProcVersionSignature: Ubuntu 6.8.0-54.56-generic 6.8.12
Uname: Linux 6.8.0-54-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: daisy 3997 F.... pipewire
/dev/snd/controlC0: daisy 4001 F.... wireplumber
/dev/snd/controlC1: daisy 4001 F.... wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 4 20:08:44 2025
MachineType: Framework Laptop 16 (AMD Ryzen 7040 Series)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: snapd_recovery_mode=run console=ttyS0,115200n8 console=tty1 panic=-1 quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.8.0-54-generic N/A
linux-backports-modules-6.8.0-54-generic N/A
linux-firmware N/A
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/27/2024
dmi.bios.release: 3.3
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.03
dmi.board.asset.tag: *
dmi.board.name: FRANMZCP07
dmi.board.vendor: Framework
dmi.board.version: A7
dmi.chassis.asset.tag: FRAGAACPAG4385000D
dmi.chassis.type: 10
dmi.chassis.vendor: Framework
dmi.chassis.version: AG
dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd03/27/2024:br3.3:svnFramework:pnLaptop16(AMDRyzen7040Series):pvrAG:rvnFramework:rnFRANMZCP07:rvrA7:cvnFramework:ct10:cvrAG:skuFRAGAACP0G:
dmi.product.family: 16in Laptop
dmi.product.name: Laptop 16 (AMD Ryzen 7040 Series)
dmi.product.sku: FRAGAACP0G
dmi.product.version: AG
dmi.sys.vendor: Framework
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-kernel-snaps/+bug/2106279/+subscriptions
** Package changed: linux (Ubuntu) => canonical-kernel-snaps
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2106279
Title:
/usr/lib/modules empty after 24.04.2 upgrade
Status in canonical-kernel-snaps:
New
Bug description:
See https://discourse.ubuntu.com/t/no-networking-after-some-upgrade-
on-24-04-2-on-a-framework-16-late-2024-setup-with-secure-boot-the-tpm-
for-fde/58387
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-54-generic (not installed)
ProcVersionSignature: Ubuntu 6.8.0-54.56-generic 6.8.12
Uname: Linux 6.8.0-54-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: daisy 3997 F.... pipewire
/dev/snd/controlC0: daisy 4001 F.... wireplumber
/dev/snd/controlC1: daisy 4001 F.... wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 4 20:08:44 2025
MachineType: Framework Laptop 16 (AMD Ryzen 7040 Series)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: snapd_recovery_mode=run console=ttyS0,115200n8 console=tty1 panic=-1 quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.8.0-54-generic N/A
linux-backports-modules-6.8.0-54-generic N/A
linux-firmware N/A
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/27/2024
dmi.bios.release: 3.3
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.03
dmi.board.asset.tag: *
dmi.board.name: FRANMZCP07
dmi.board.vendor: Framework
dmi.board.version: A7
dmi.chassis.asset.tag: FRAGAACPAG4385000D
dmi.chassis.type: 10
dmi.chassis.vendor: Framework
dmi.chassis.version: AG
dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd03/27/2024:br3.3:svnFramework:pnLaptop16(AMDRyzen7040Series):pvrAG:rvnFramework:rnFRANMZCP07:rvrA7:cvnFramework:ct10:cvrAG:skuFRAGAACP0G:
dmi.product.family: 16in Laptop
dmi.product.name: Laptop 16 (AMD Ryzen 7040 Series)
dmi.product.sku: FRAGAACP0G
dmi.product.version: AG
dmi.sys.vendor: Framework
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-kernel-snaps/+bug/2106279/+subscriptions
воскресенье
[Bug 2103598] Re: NFS, overlay, fstab issue after update to kernel 5.15.0-133-generic and -134
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+
+ After kernel Ubuntu-5.15.0-132, lots of udf patches are introduced but
+ it led to directory corruption when directory's last content has more
+ than one block.
+
+ [Fix]
+
+ Cherry pick commit 1ea1cd11c72d("udf: Fix directory iteration for longer
+ tail extents") from mainline to fix it.
+
+ [Test Case]
+
+ 1. Boot the patched kernel with the CDROM inserted.
+ 2. Check if dmesg shows the error like: udf_fiiter_advance_blk: extent after position 2016 not allocated in directory
+
+
+ [Where problems could occur]
+ The patch simply fix the rounding issue for the directory access on udf filesystem. Should be low risk for regression
+
+
+ ============ original bug report ============
+
Hello,
After updating from 5.15.0-131-generic on ubuntu 22.04 to newer versions, our fstab mountpoints for overlays are failing. we are using them to mount ISO (VM's on vsphere). It happens on all ubuntu vm's.
lsb_release -rd
Description: Ubuntu 22.04.5 LTS
Release: 22.04
apport file in the attachment
fstab entry:
cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=3f1bdecc-af3b-4c65-a8e5-208b58e147b9 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=5cd2a861-4079-4492-bf6b-e60c6d406b4e none swap sw 0 0
#/dev/sda1 /mapsrw ext4 defaults 0 1
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/sr1 /media/cdrom1 udf,iso9660 user,noauto 0 0
-
/dev/sr0 /mapsro udf,iso9660 ro 0 0
overlay /opt/iso overlay
lowerdir=/mapsro,upperdir=/mapsrw,workdir=/mapswork,defaults,_netdev,x-systemd.requires-
mounts-for=/mapsro
-
/dev/sr1 /gcdro udf,iso9660 ro 0 0
overlay /opt/iso/map/gcd overlay lowerdir=/gcdro,upperdir=/gcdrw,workdir=/gcdwork,defaults,_netdev,x-systemd.requires-mounts-for=/gcdro
-
dmesg output after update
[ 2.791617] vmwgfx 0000:00:0f.0: [drm] Screen Target display unit initialized
[ 2.792712] vmwgfx 0000:00:0f.0: [drm] Fifo max 0x00040000 min 0x00001000 cap 0x0000077f
[ 2.793589] vmwgfx 0000:00:0f.0: [drm] Using command buffers with DMA pool.
[ 2.793595] vmwgfx 0000:00:0f.0: [drm] Available shader model: Legacy.
[ 2.795045] fbcon: svgadrmfb (fb0) is primary device
[ 2.795542] Console: switching to colour frame buffer device 100x37
[ 2.799710] [drm] Initialized vmwgfx 2.19.0 20210722 for 0000:00:0f.0 on minor 0
[ 2.800406] systemd[1]: Finished Load Kernel Modules.
[ 2.801077] systemd[1]: Starting Apply Kernel Variables...
[ 2.801185] systemd[1]: Started Journal Service.
[ 2.805436] systemd-journald[434]: Received client request to flush runtime journal.
[ 2.912001] vmw_vmci 0000:00:07.7: Using capabilities 0xc
[ 2.912403] Guest personality initialized and is active
[ 2.916033] VMCI host device registered (name=vmci, major=10, minor=123)
[ 2.916035] Initialized host personality
[ 2.960298] Adding 4317180k swap on /dev/sda5. Priority:-2 extents:1 across:4317180k SSFS
[ 2.975943] RAPL PMU: API unit is 2^-32 Joules, 0 fixed counters, 10737418240 ms ovfl timer
[ 2.979501] cryptd: max_cpu_qlen set to 1000
[ 2.989102] AVX2 version of gcm_enc/dec engaged.
[ 2.989205] AES CTR mode by8 optimization enabled
[ 3.129983] RPC: Registered named UNIX socket transport module.
[ 3.129986] RPC: Registered udp transport module.
[ 3.129986] RPC: Registered tcp transport module.
[ 3.129987] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 3.134884] audit: type=1400 audit(1742377247.423:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=669 comm="apparmor_parser"
[ 3.134888] audit: type=1400 audit(1742377247.423:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=669 comm="apparmor_parser"
[ 3.134905] audit: type=1400 audit(1742377247.423:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=668 comm="apparmor_parser"
[ 3.137445] audit: type=1400 audit(1742377247.427:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=673 comm="apparmor_parser"
[ 3.137447] audit: type=1400 audit(1742377247.427:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=673 comm="apparmor_parser"
[ 3.137450] audit: type=1400 audit(1742377247.427:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=673 comm="apparmor_parser"
[ 3.140695] audit: type=1400 audit(1742377247.431:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="ubuntu_pro_apt_news" pid=671 comm="apparmor_parser"
[ 3.142882] audit: type=1400 audit(1742377247.431:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="tcpdump" pid=674 comm="apparmor_parser"
[ 3.146434] audit: type=1400 audit(1742377247.435:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=670 comm="apparmor_parser"
[ 3.147041] vmxnet3 0000:03:00.0 ens160: intr type 3, mode 0, 9 vectors allocated
[ 3.149459] vmxnet3 0000:03:00.0 ens160: NIC Link is Up 10000 Mbps
[ 3.192250] NET: Registered PF_VSOCK protocol family
[ 16.512894] overlayfs: null uuid detected in lower fs '/', falling back to xino=off,index=off,nfs_export=off.
[ 16.518113] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.518118] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.518145] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.518146] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.518159] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.518160] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.520084] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.520089] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.520125] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.520126] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.522079] FS-Cache: Loaded
[ 16.554821] FS-Cache: Netfs 'nfs' registered for caching
[ 16.684508] NFS: Registering the id_resolver key type
[ 16.684517] Key type id_resolver registered
[ 16.684518] Key type id_legacy registered
[ 20.160812] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.160853] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166339] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166380] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166740] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166773] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166829] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166859] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166912] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166941] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166995] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.167024] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.184362] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.184405] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.198854] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.198895] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.199000] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.199688] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.212325] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.213678] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.219212] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.220536] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.228836] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.230183] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.384191] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.385550] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.386987] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.388239] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.389527] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.390973] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.540547] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.541910] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.587198] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.588558] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.590494] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.591733] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.593009] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.594276] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.595543] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.596853] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.598310] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.599556] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.792315] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.793705] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 29.068728] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 29.070077] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.042175] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.043563] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.271936] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.273292] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.484056] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.485421] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.612029] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.613398] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.787934] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.789298] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
** Description changed:
[SRU Justification]
[Impact]
After kernel Ubuntu-5.15.0-132, lots of udf patches are introduced but
it led to directory corruption when directory's last content has more
than one block.
[Fix]
Cherry pick commit 1ea1cd11c72d("udf: Fix directory iteration for longer
tail extents") from mainline to fix it.
[Test Case]
1. Boot the patched kernel with the CDROM inserted.
2. Check if dmesg shows the error like: udf_fiiter_advance_blk: extent after position 2016 not allocated in directory
-
[Where problems could occur]
- The patch simply fix the rounding issue for the directory access on udf filesystem. Should be low risk for regression
-
+ The patch is already landed after kernel 6.2 and it simply fixes the rounding issue for the directory access on udf filesystem. Should be low risk for regression.
============ original bug report ============
Hello,
After updating from 5.15.0-131-generic on ubuntu 22.04 to newer versions, our fstab mountpoints for overlays are failing. we are using them to mount ISO (VM's on vsphere). It happens on all ubuntu vm's.
lsb_release -rd
Description: Ubuntu 22.04.5 LTS
Release: 22.04
apport file in the attachment
fstab entry:
cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=3f1bdecc-af3b-4c65-a8e5-208b58e147b9 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=5cd2a861-4079-4492-bf6b-e60c6d406b4e none swap sw 0 0
#/dev/sda1 /mapsrw ext4 defaults 0 1
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/sr1 /media/cdrom1 udf,iso9660 user,noauto 0 0
/dev/sr0 /mapsro udf,iso9660 ro 0 0
overlay /opt/iso overlay
lowerdir=/mapsro,upperdir=/mapsrw,workdir=/mapswork,defaults,_netdev,x-systemd.requires-
mounts-for=/mapsro
/dev/sr1 /gcdro udf,iso9660 ro 0 0
overlay /opt/iso/map/gcd overlay lowerdir=/gcdro,upperdir=/gcdrw,workdir=/gcdwork,defaults,_netdev,x-systemd.requires-mounts-for=/gcdro
dmesg output after update
[ 2.791617] vmwgfx 0000:00:0f.0: [drm] Screen Target display unit initialized
[ 2.792712] vmwgfx 0000:00:0f.0: [drm] Fifo max 0x00040000 min 0x00001000 cap 0x0000077f
[ 2.793589] vmwgfx 0000:00:0f.0: [drm] Using command buffers with DMA pool.
[ 2.793595] vmwgfx 0000:00:0f.0: [drm] Available shader model: Legacy.
[ 2.795045] fbcon: svgadrmfb (fb0) is primary device
[ 2.795542] Console: switching to colour frame buffer device 100x37
[ 2.799710] [drm] Initialized vmwgfx 2.19.0 20210722 for 0000:00:0f.0 on minor 0
[ 2.800406] systemd[1]: Finished Load Kernel Modules.
[ 2.801077] systemd[1]: Starting Apply Kernel Variables...
[ 2.801185] systemd[1]: Started Journal Service.
[ 2.805436] systemd-journald[434]: Received client request to flush runtime journal.
[ 2.912001] vmw_vmci 0000:00:07.7: Using capabilities 0xc
[ 2.912403] Guest personality initialized and is active
[ 2.916033] VMCI host device registered (name=vmci, major=10, minor=123)
[ 2.916035] Initialized host personality
[ 2.960298] Adding 4317180k swap on /dev/sda5. Priority:-2 extents:1 across:4317180k SSFS
[ 2.975943] RAPL PMU: API unit is 2^-32 Joules, 0 fixed counters, 10737418240 ms ovfl timer
[ 2.979501] cryptd: max_cpu_qlen set to 1000
[ 2.989102] AVX2 version of gcm_enc/dec engaged.
[ 2.989205] AES CTR mode by8 optimization enabled
[ 3.129983] RPC: Registered named UNIX socket transport module.
[ 3.129986] RPC: Registered udp transport module.
[ 3.129986] RPC: Registered tcp transport module.
[ 3.129987] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 3.134884] audit: type=1400 audit(1742377247.423:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=669 comm="apparmor_parser"
[ 3.134888] audit: type=1400 audit(1742377247.423:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=669 comm="apparmor_parser"
[ 3.134905] audit: type=1400 audit(1742377247.423:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=668 comm="apparmor_parser"
[ 3.137445] audit: type=1400 audit(1742377247.427:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=673 comm="apparmor_parser"
[ 3.137447] audit: type=1400 audit(1742377247.427:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=673 comm="apparmor_parser"
[ 3.137450] audit: type=1400 audit(1742377247.427:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=673 comm="apparmor_parser"
[ 3.140695] audit: type=1400 audit(1742377247.431:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="ubuntu_pro_apt_news" pid=671 comm="apparmor_parser"
[ 3.142882] audit: type=1400 audit(1742377247.431:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="tcpdump" pid=674 comm="apparmor_parser"
[ 3.146434] audit: type=1400 audit(1742377247.435:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=670 comm="apparmor_parser"
[ 3.147041] vmxnet3 0000:03:00.0 ens160: intr type 3, mode 0, 9 vectors allocated
[ 3.149459] vmxnet3 0000:03:00.0 ens160: NIC Link is Up 10000 Mbps
[ 3.192250] NET: Registered PF_VSOCK protocol family
[ 16.512894] overlayfs: null uuid detected in lower fs '/', falling back to xino=off,index=off,nfs_export=off.
[ 16.518113] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.518118] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.518145] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.518146] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.518159] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.518160] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.520084] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.520089] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.520125] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.520126] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.522079] FS-Cache: Loaded
[ 16.554821] FS-Cache: Netfs 'nfs' registered for caching
[ 16.684508] NFS: Registering the id_resolver key type
[ 16.684517] Key type id_resolver registered
[ 16.684518] Key type id_legacy registered
[ 20.160812] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.160853] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166339] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166380] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166740] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166773] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166829] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166859] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166912] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166941] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166995] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.167024] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.184362] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.184405] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.198854] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.198895] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.199000] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.199688] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.212325] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.213678] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.219212] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.220536] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.228836] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.230183] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.384191] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.385550] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.386987] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.388239] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.389527] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.390973] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.540547] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.541910] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.587198] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.588558] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.590494] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.591733] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.593009] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.594276] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.595543] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.596853] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.598310] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.599556] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.792315] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.793705] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 29.068728] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 29.070077] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.042175] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.043563] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.271936] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.273292] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.484056] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.485421] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.612029] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.613398] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.787934] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.789298] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2103598
Title:
NFS, overlay, fstab issue after update to kernel 5.15.0-133-generic
and -134
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Jammy:
New
Bug description:
[SRU Justification]
[Impact]
After kernel Ubuntu-5.15.0-132, lots of udf patches are introduced but
it led to directory corruption when directory's last content has more
than one block.
[Fix]
Cherry pick commit 1ea1cd11c72d("udf: Fix directory iteration for
longer tail extents") from mainline to fix it.
[Test Case]
1. Boot the patched kernel with the CDROM inserted.
2. Check if dmesg shows the error like: udf_fiiter_advance_blk: extent after position 2016 not allocated in directory
[Where problems could occur]
The patch is already landed after kernel 6.2 and it simply fixes the rounding issue for the directory access on udf filesystem. Should be low risk for regression.
============ original bug report ============
Hello,
After updating from 5.15.0-131-generic on ubuntu 22.04 to newer versions, our fstab mountpoints for overlays are failing. we are using them to mount ISO (VM's on vsphere). It happens on all ubuntu vm's.
lsb_release -rd
Description: Ubuntu 22.04.5 LTS
Release: 22.04
apport file in the attachment
fstab entry:
cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=3f1bdecc-af3b-4c65-a8e5-208b58e147b9 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=5cd2a861-4079-4492-bf6b-e60c6d406b4e none swap sw 0 0
#/dev/sda1 /mapsrw ext4 defaults 0 1
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/sr1 /media/cdrom1 udf,iso9660 user,noauto 0 0
/dev/sr0 /mapsro udf,iso9660 ro 0 0
overlay /opt/iso overlay
lowerdir=/mapsro,upperdir=/mapsrw,workdir=/mapswork,defaults,_netdev,x-systemd.requires-
mounts-for=/mapsro
/dev/sr1 /gcdro udf,iso9660 ro 0 0
overlay /opt/iso/map/gcd overlay lowerdir=/gcdro,upperdir=/gcdrw,workdir=/gcdwork,defaults,_netdev,x-systemd.requires-mounts-for=/gcdro
dmesg output after update
[ 2.791617] vmwgfx 0000:00:0f.0: [drm] Screen Target display unit initialized
[ 2.792712] vmwgfx 0000:00:0f.0: [drm] Fifo max 0x00040000 min 0x00001000 cap 0x0000077f
[ 2.793589] vmwgfx 0000:00:0f.0: [drm] Using command buffers with DMA pool.
[ 2.793595] vmwgfx 0000:00:0f.0: [drm] Available shader model: Legacy.
[ 2.795045] fbcon: svgadrmfb (fb0) is primary device
[ 2.795542] Console: switching to colour frame buffer device 100x37
[ 2.799710] [drm] Initialized vmwgfx 2.19.0 20210722 for 0000:00:0f.0 on minor 0
[ 2.800406] systemd[1]: Finished Load Kernel Modules.
[ 2.801077] systemd[1]: Starting Apply Kernel Variables...
[ 2.801185] systemd[1]: Started Journal Service.
[ 2.805436] systemd-journald[434]: Received client request to flush runtime journal.
[ 2.912001] vmw_vmci 0000:00:07.7: Using capabilities 0xc
[ 2.912403] Guest personality initialized and is active
[ 2.916033] VMCI host device registered (name=vmci, major=10, minor=123)
[ 2.916035] Initialized host personality
[ 2.960298] Adding 4317180k swap on /dev/sda5. Priority:-2 extents:1 across:4317180k SSFS
[ 2.975943] RAPL PMU: API unit is 2^-32 Joules, 0 fixed counters, 10737418240 ms ovfl timer
[ 2.979501] cryptd: max_cpu_qlen set to 1000
[ 2.989102] AVX2 version of gcm_enc/dec engaged.
[ 2.989205] AES CTR mode by8 optimization enabled
[ 3.129983] RPC: Registered named UNIX socket transport module.
[ 3.129986] RPC: Registered udp transport module.
[ 3.129986] RPC: Registered tcp transport module.
[ 3.129987] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 3.134884] audit: type=1400 audit(1742377247.423:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=669 comm="apparmor_parser"
[ 3.134888] audit: type=1400 audit(1742377247.423:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=669 comm="apparmor_parser"
[ 3.134905] audit: type=1400 audit(1742377247.423:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=668 comm="apparmor_parser"
[ 3.137445] audit: type=1400 audit(1742377247.427:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=673 comm="apparmor_parser"
[ 3.137447] audit: type=1400 audit(1742377247.427:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=673 comm="apparmor_parser"
[ 3.137450] audit: type=1400 audit(1742377247.427:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=673 comm="apparmor_parser"
[ 3.140695] audit: type=1400 audit(1742377247.431:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="ubuntu_pro_apt_news" pid=671 comm="apparmor_parser"
[ 3.142882] audit: type=1400 audit(1742377247.431:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="tcpdump" pid=674 comm="apparmor_parser"
[ 3.146434] audit: type=1400 audit(1742377247.435:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=670 comm="apparmor_parser"
[ 3.147041] vmxnet3 0000:03:00.0 ens160: intr type 3, mode 0, 9 vectors allocated
[ 3.149459] vmxnet3 0000:03:00.0 ens160: NIC Link is Up 10000 Mbps
[ 3.192250] NET: Registered PF_VSOCK protocol family
[ 16.512894] overlayfs: null uuid detected in lower fs '/', falling back to xino=off,index=off,nfs_export=off.
[ 16.518113] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.518118] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.518145] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.518146] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.518159] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.518160] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.520084] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.520089] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.520125] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.520126] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.522079] FS-Cache: Loaded
[ 16.554821] FS-Cache: Netfs 'nfs' registered for caching
[ 16.684508] NFS: Registering the id_resolver key type
[ 16.684517] Key type id_resolver registered
[ 16.684518] Key type id_legacy registered
[ 20.160812] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.160853] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166339] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166380] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166740] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166773] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166829] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166859] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166912] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166941] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166995] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.167024] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.184362] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.184405] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.198854] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.198895] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.199000] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.199688] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.212325] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.213678] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.219212] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.220536] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.228836] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.230183] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.384191] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.385550] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.386987] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.388239] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.389527] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.390973] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.540547] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.541910] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.587198] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.588558] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.590494] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.591733] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.593009] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.594276] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.595543] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.596853] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.598310] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.599556] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.792315] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.793705] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 29.068728] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 29.070077] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.042175] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.043563] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.271936] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.273292] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.484056] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.485421] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.612029] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.613398] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.787934] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.789298] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2103598/+subscriptions
+ [SRU Justification]
+
+ [Impact]
+
+ After kernel Ubuntu-5.15.0-132, lots of udf patches are introduced but
+ it led to directory corruption when directory's last content has more
+ than one block.
+
+ [Fix]
+
+ Cherry pick commit 1ea1cd11c72d("udf: Fix directory iteration for longer
+ tail extents") from mainline to fix it.
+
+ [Test Case]
+
+ 1. Boot the patched kernel with the CDROM inserted.
+ 2. Check if dmesg shows the error like: udf_fiiter_advance_blk: extent after position 2016 not allocated in directory
+
+
+ [Where problems could occur]
+ The patch simply fix the rounding issue for the directory access on udf filesystem. Should be low risk for regression
+
+
+ ============ original bug report ============
+
Hello,
After updating from 5.15.0-131-generic on ubuntu 22.04 to newer versions, our fstab mountpoints for overlays are failing. we are using them to mount ISO (VM's on vsphere). It happens on all ubuntu vm's.
lsb_release -rd
Description: Ubuntu 22.04.5 LTS
Release: 22.04
apport file in the attachment
fstab entry:
cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=3f1bdecc-af3b-4c65-a8e5-208b58e147b9 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=5cd2a861-4079-4492-bf6b-e60c6d406b4e none swap sw 0 0
#/dev/sda1 /mapsrw ext4 defaults 0 1
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/sr1 /media/cdrom1 udf,iso9660 user,noauto 0 0
-
/dev/sr0 /mapsro udf,iso9660 ro 0 0
overlay /opt/iso overlay
lowerdir=/mapsro,upperdir=/mapsrw,workdir=/mapswork,defaults,_netdev,x-systemd.requires-
mounts-for=/mapsro
-
/dev/sr1 /gcdro udf,iso9660 ro 0 0
overlay /opt/iso/map/gcd overlay lowerdir=/gcdro,upperdir=/gcdrw,workdir=/gcdwork,defaults,_netdev,x-systemd.requires-mounts-for=/gcdro
-
dmesg output after update
[ 2.791617] vmwgfx 0000:00:0f.0: [drm] Screen Target display unit initialized
[ 2.792712] vmwgfx 0000:00:0f.0: [drm] Fifo max 0x00040000 min 0x00001000 cap 0x0000077f
[ 2.793589] vmwgfx 0000:00:0f.0: [drm] Using command buffers with DMA pool.
[ 2.793595] vmwgfx 0000:00:0f.0: [drm] Available shader model: Legacy.
[ 2.795045] fbcon: svgadrmfb (fb0) is primary device
[ 2.795542] Console: switching to colour frame buffer device 100x37
[ 2.799710] [drm] Initialized vmwgfx 2.19.0 20210722 for 0000:00:0f.0 on minor 0
[ 2.800406] systemd[1]: Finished Load Kernel Modules.
[ 2.801077] systemd[1]: Starting Apply Kernel Variables...
[ 2.801185] systemd[1]: Started Journal Service.
[ 2.805436] systemd-journald[434]: Received client request to flush runtime journal.
[ 2.912001] vmw_vmci 0000:00:07.7: Using capabilities 0xc
[ 2.912403] Guest personality initialized and is active
[ 2.916033] VMCI host device registered (name=vmci, major=10, minor=123)
[ 2.916035] Initialized host personality
[ 2.960298] Adding 4317180k swap on /dev/sda5. Priority:-2 extents:1 across:4317180k SSFS
[ 2.975943] RAPL PMU: API unit is 2^-32 Joules, 0 fixed counters, 10737418240 ms ovfl timer
[ 2.979501] cryptd: max_cpu_qlen set to 1000
[ 2.989102] AVX2 version of gcm_enc/dec engaged.
[ 2.989205] AES CTR mode by8 optimization enabled
[ 3.129983] RPC: Registered named UNIX socket transport module.
[ 3.129986] RPC: Registered udp transport module.
[ 3.129986] RPC: Registered tcp transport module.
[ 3.129987] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 3.134884] audit: type=1400 audit(1742377247.423:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=669 comm="apparmor_parser"
[ 3.134888] audit: type=1400 audit(1742377247.423:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=669 comm="apparmor_parser"
[ 3.134905] audit: type=1400 audit(1742377247.423:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=668 comm="apparmor_parser"
[ 3.137445] audit: type=1400 audit(1742377247.427:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=673 comm="apparmor_parser"
[ 3.137447] audit: type=1400 audit(1742377247.427:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=673 comm="apparmor_parser"
[ 3.137450] audit: type=1400 audit(1742377247.427:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=673 comm="apparmor_parser"
[ 3.140695] audit: type=1400 audit(1742377247.431:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="ubuntu_pro_apt_news" pid=671 comm="apparmor_parser"
[ 3.142882] audit: type=1400 audit(1742377247.431:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="tcpdump" pid=674 comm="apparmor_parser"
[ 3.146434] audit: type=1400 audit(1742377247.435:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=670 comm="apparmor_parser"
[ 3.147041] vmxnet3 0000:03:00.0 ens160: intr type 3, mode 0, 9 vectors allocated
[ 3.149459] vmxnet3 0000:03:00.0 ens160: NIC Link is Up 10000 Mbps
[ 3.192250] NET: Registered PF_VSOCK protocol family
[ 16.512894] overlayfs: null uuid detected in lower fs '/', falling back to xino=off,index=off,nfs_export=off.
[ 16.518113] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.518118] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.518145] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.518146] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.518159] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.518160] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.520084] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.520089] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.520125] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.520126] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.522079] FS-Cache: Loaded
[ 16.554821] FS-Cache: Netfs 'nfs' registered for caching
[ 16.684508] NFS: Registering the id_resolver key type
[ 16.684517] Key type id_resolver registered
[ 16.684518] Key type id_legacy registered
[ 20.160812] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.160853] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166339] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166380] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166740] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166773] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166829] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166859] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166912] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166941] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166995] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.167024] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.184362] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.184405] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.198854] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.198895] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.199000] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.199688] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.212325] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.213678] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.219212] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.220536] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.228836] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.230183] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.384191] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.385550] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.386987] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.388239] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.389527] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.390973] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.540547] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.541910] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.587198] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.588558] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.590494] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.591733] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.593009] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.594276] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.595543] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.596853] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.598310] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.599556] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.792315] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.793705] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 29.068728] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 29.070077] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.042175] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.043563] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.271936] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.273292] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.484056] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.485421] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.612029] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.613398] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.787934] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.789298] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
** Description changed:
[SRU Justification]
[Impact]
After kernel Ubuntu-5.15.0-132, lots of udf patches are introduced but
it led to directory corruption when directory's last content has more
than one block.
[Fix]
Cherry pick commit 1ea1cd11c72d("udf: Fix directory iteration for longer
tail extents") from mainline to fix it.
[Test Case]
1. Boot the patched kernel with the CDROM inserted.
2. Check if dmesg shows the error like: udf_fiiter_advance_blk: extent after position 2016 not allocated in directory
-
[Where problems could occur]
- The patch simply fix the rounding issue for the directory access on udf filesystem. Should be low risk for regression
-
+ The patch is already landed after kernel 6.2 and it simply fixes the rounding issue for the directory access on udf filesystem. Should be low risk for regression.
============ original bug report ============
Hello,
After updating from 5.15.0-131-generic on ubuntu 22.04 to newer versions, our fstab mountpoints for overlays are failing. we are using them to mount ISO (VM's on vsphere). It happens on all ubuntu vm's.
lsb_release -rd
Description: Ubuntu 22.04.5 LTS
Release: 22.04
apport file in the attachment
fstab entry:
cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=3f1bdecc-af3b-4c65-a8e5-208b58e147b9 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=5cd2a861-4079-4492-bf6b-e60c6d406b4e none swap sw 0 0
#/dev/sda1 /mapsrw ext4 defaults 0 1
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/sr1 /media/cdrom1 udf,iso9660 user,noauto 0 0
/dev/sr0 /mapsro udf,iso9660 ro 0 0
overlay /opt/iso overlay
lowerdir=/mapsro,upperdir=/mapsrw,workdir=/mapswork,defaults,_netdev,x-systemd.requires-
mounts-for=/mapsro
/dev/sr1 /gcdro udf,iso9660 ro 0 0
overlay /opt/iso/map/gcd overlay lowerdir=/gcdro,upperdir=/gcdrw,workdir=/gcdwork,defaults,_netdev,x-systemd.requires-mounts-for=/gcdro
dmesg output after update
[ 2.791617] vmwgfx 0000:00:0f.0: [drm] Screen Target display unit initialized
[ 2.792712] vmwgfx 0000:00:0f.0: [drm] Fifo max 0x00040000 min 0x00001000 cap 0x0000077f
[ 2.793589] vmwgfx 0000:00:0f.0: [drm] Using command buffers with DMA pool.
[ 2.793595] vmwgfx 0000:00:0f.0: [drm] Available shader model: Legacy.
[ 2.795045] fbcon: svgadrmfb (fb0) is primary device
[ 2.795542] Console: switching to colour frame buffer device 100x37
[ 2.799710] [drm] Initialized vmwgfx 2.19.0 20210722 for 0000:00:0f.0 on minor 0
[ 2.800406] systemd[1]: Finished Load Kernel Modules.
[ 2.801077] systemd[1]: Starting Apply Kernel Variables...
[ 2.801185] systemd[1]: Started Journal Service.
[ 2.805436] systemd-journald[434]: Received client request to flush runtime journal.
[ 2.912001] vmw_vmci 0000:00:07.7: Using capabilities 0xc
[ 2.912403] Guest personality initialized and is active
[ 2.916033] VMCI host device registered (name=vmci, major=10, minor=123)
[ 2.916035] Initialized host personality
[ 2.960298] Adding 4317180k swap on /dev/sda5. Priority:-2 extents:1 across:4317180k SSFS
[ 2.975943] RAPL PMU: API unit is 2^-32 Joules, 0 fixed counters, 10737418240 ms ovfl timer
[ 2.979501] cryptd: max_cpu_qlen set to 1000
[ 2.989102] AVX2 version of gcm_enc/dec engaged.
[ 2.989205] AES CTR mode by8 optimization enabled
[ 3.129983] RPC: Registered named UNIX socket transport module.
[ 3.129986] RPC: Registered udp transport module.
[ 3.129986] RPC: Registered tcp transport module.
[ 3.129987] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 3.134884] audit: type=1400 audit(1742377247.423:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=669 comm="apparmor_parser"
[ 3.134888] audit: type=1400 audit(1742377247.423:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=669 comm="apparmor_parser"
[ 3.134905] audit: type=1400 audit(1742377247.423:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=668 comm="apparmor_parser"
[ 3.137445] audit: type=1400 audit(1742377247.427:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=673 comm="apparmor_parser"
[ 3.137447] audit: type=1400 audit(1742377247.427:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=673 comm="apparmor_parser"
[ 3.137450] audit: type=1400 audit(1742377247.427:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=673 comm="apparmor_parser"
[ 3.140695] audit: type=1400 audit(1742377247.431:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="ubuntu_pro_apt_news" pid=671 comm="apparmor_parser"
[ 3.142882] audit: type=1400 audit(1742377247.431:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="tcpdump" pid=674 comm="apparmor_parser"
[ 3.146434] audit: type=1400 audit(1742377247.435:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=670 comm="apparmor_parser"
[ 3.147041] vmxnet3 0000:03:00.0 ens160: intr type 3, mode 0, 9 vectors allocated
[ 3.149459] vmxnet3 0000:03:00.0 ens160: NIC Link is Up 10000 Mbps
[ 3.192250] NET: Registered PF_VSOCK protocol family
[ 16.512894] overlayfs: null uuid detected in lower fs '/', falling back to xino=off,index=off,nfs_export=off.
[ 16.518113] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.518118] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.518145] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.518146] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.518159] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.518160] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.520084] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.520089] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.520125] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.520126] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.522079] FS-Cache: Loaded
[ 16.554821] FS-Cache: Netfs 'nfs' registered for caching
[ 16.684508] NFS: Registering the id_resolver key type
[ 16.684517] Key type id_resolver registered
[ 16.684518] Key type id_legacy registered
[ 20.160812] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.160853] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166339] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166380] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166740] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166773] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166829] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166859] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166912] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166941] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166995] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.167024] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.184362] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.184405] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.198854] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.198895] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.199000] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.199688] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.212325] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.213678] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.219212] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.220536] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.228836] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.230183] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.384191] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.385550] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.386987] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.388239] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.389527] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.390973] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.540547] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.541910] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.587198] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.588558] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.590494] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.591733] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.593009] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.594276] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.595543] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.596853] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.598310] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.599556] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.792315] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.793705] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 29.068728] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 29.070077] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.042175] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.043563] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.271936] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.273292] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.484056] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.485421] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.612029] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.613398] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.787934] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.789298] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2103598
Title:
NFS, overlay, fstab issue after update to kernel 5.15.0-133-generic
and -134
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Jammy:
New
Bug description:
[SRU Justification]
[Impact]
After kernel Ubuntu-5.15.0-132, lots of udf patches are introduced but
it led to directory corruption when directory's last content has more
than one block.
[Fix]
Cherry pick commit 1ea1cd11c72d("udf: Fix directory iteration for
longer tail extents") from mainline to fix it.
[Test Case]
1. Boot the patched kernel with the CDROM inserted.
2. Check if dmesg shows the error like: udf_fiiter_advance_blk: extent after position 2016 not allocated in directory
[Where problems could occur]
The patch is already landed after kernel 6.2 and it simply fixes the rounding issue for the directory access on udf filesystem. Should be low risk for regression.
============ original bug report ============
Hello,
After updating from 5.15.0-131-generic on ubuntu 22.04 to newer versions, our fstab mountpoints for overlays are failing. we are using them to mount ISO (VM's on vsphere). It happens on all ubuntu vm's.
lsb_release -rd
Description: Ubuntu 22.04.5 LTS
Release: 22.04
apport file in the attachment
fstab entry:
cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=3f1bdecc-af3b-4c65-a8e5-208b58e147b9 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=5cd2a861-4079-4492-bf6b-e60c6d406b4e none swap sw 0 0
#/dev/sda1 /mapsrw ext4 defaults 0 1
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/sr1 /media/cdrom1 udf,iso9660 user,noauto 0 0
/dev/sr0 /mapsro udf,iso9660 ro 0 0
overlay /opt/iso overlay
lowerdir=/mapsro,upperdir=/mapsrw,workdir=/mapswork,defaults,_netdev,x-systemd.requires-
mounts-for=/mapsro
/dev/sr1 /gcdro udf,iso9660 ro 0 0
overlay /opt/iso/map/gcd overlay lowerdir=/gcdro,upperdir=/gcdrw,workdir=/gcdwork,defaults,_netdev,x-systemd.requires-mounts-for=/gcdro
dmesg output after update
[ 2.791617] vmwgfx 0000:00:0f.0: [drm] Screen Target display unit initialized
[ 2.792712] vmwgfx 0000:00:0f.0: [drm] Fifo max 0x00040000 min 0x00001000 cap 0x0000077f
[ 2.793589] vmwgfx 0000:00:0f.0: [drm] Using command buffers with DMA pool.
[ 2.793595] vmwgfx 0000:00:0f.0: [drm] Available shader model: Legacy.
[ 2.795045] fbcon: svgadrmfb (fb0) is primary device
[ 2.795542] Console: switching to colour frame buffer device 100x37
[ 2.799710] [drm] Initialized vmwgfx 2.19.0 20210722 for 0000:00:0f.0 on minor 0
[ 2.800406] systemd[1]: Finished Load Kernel Modules.
[ 2.801077] systemd[1]: Starting Apply Kernel Variables...
[ 2.801185] systemd[1]: Started Journal Service.
[ 2.805436] systemd-journald[434]: Received client request to flush runtime journal.
[ 2.912001] vmw_vmci 0000:00:07.7: Using capabilities 0xc
[ 2.912403] Guest personality initialized and is active
[ 2.916033] VMCI host device registered (name=vmci, major=10, minor=123)
[ 2.916035] Initialized host personality
[ 2.960298] Adding 4317180k swap on /dev/sda5. Priority:-2 extents:1 across:4317180k SSFS
[ 2.975943] RAPL PMU: API unit is 2^-32 Joules, 0 fixed counters, 10737418240 ms ovfl timer
[ 2.979501] cryptd: max_cpu_qlen set to 1000
[ 2.989102] AVX2 version of gcm_enc/dec engaged.
[ 2.989205] AES CTR mode by8 optimization enabled
[ 3.129983] RPC: Registered named UNIX socket transport module.
[ 3.129986] RPC: Registered udp transport module.
[ 3.129986] RPC: Registered tcp transport module.
[ 3.129987] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 3.134884] audit: type=1400 audit(1742377247.423:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=669 comm="apparmor_parser"
[ 3.134888] audit: type=1400 audit(1742377247.423:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=669 comm="apparmor_parser"
[ 3.134905] audit: type=1400 audit(1742377247.423:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=668 comm="apparmor_parser"
[ 3.137445] audit: type=1400 audit(1742377247.427:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=673 comm="apparmor_parser"
[ 3.137447] audit: type=1400 audit(1742377247.427:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=673 comm="apparmor_parser"
[ 3.137450] audit: type=1400 audit(1742377247.427:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=673 comm="apparmor_parser"
[ 3.140695] audit: type=1400 audit(1742377247.431:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="ubuntu_pro_apt_news" pid=671 comm="apparmor_parser"
[ 3.142882] audit: type=1400 audit(1742377247.431:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="tcpdump" pid=674 comm="apparmor_parser"
[ 3.146434] audit: type=1400 audit(1742377247.435:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=670 comm="apparmor_parser"
[ 3.147041] vmxnet3 0000:03:00.0 ens160: intr type 3, mode 0, 9 vectors allocated
[ 3.149459] vmxnet3 0000:03:00.0 ens160: NIC Link is Up 10000 Mbps
[ 3.192250] NET: Registered PF_VSOCK protocol family
[ 16.512894] overlayfs: null uuid detected in lower fs '/', falling back to xino=off,index=off,nfs_export=off.
[ 16.518113] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.518118] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.518145] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.518146] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.518159] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.518160] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.520084] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.520089] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.520125] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.520126] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.522079] FS-Cache: Loaded
[ 16.554821] FS-Cache: Netfs 'nfs' registered for caching
[ 16.684508] NFS: Registering the id_resolver key type
[ 16.684517] Key type id_resolver registered
[ 16.684518] Key type id_legacy registered
[ 20.160812] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.160853] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166339] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166380] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166740] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166773] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166829] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166859] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166912] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166941] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166995] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.167024] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.184362] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.184405] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.198854] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.198895] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.199000] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.199688] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.212325] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.213678] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.219212] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.220536] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.228836] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.230183] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.384191] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.385550] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.386987] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.388239] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.389527] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.390973] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.540547] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.541910] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.587198] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.588558] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.590494] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.591733] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.593009] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.594276] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.595543] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.596853] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.598310] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.599556] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.792315] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.793705] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 29.068728] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 29.070077] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.042175] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.043563] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.271936] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.273292] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.484056] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.485421] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.612029] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.613398] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.787934] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.789298] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2103598/+subscriptions
[Bug 2103598] Re: NFS, overlay, fstab issue after update to kernel 5.15.0-133-generic and -134
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2103598
Title:
NFS, overlay, fstab issue after update to kernel 5.15.0-133-generic
and -134
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Jammy:
New
Bug description:
Hello,
After updating from 5.15.0-131-generic on ubuntu 22.04 to newer versions, our fstab mountpoints for overlays are failing. we are using them to mount ISO (VM's on vsphere). It happens on all ubuntu vm's.
lsb_release -rd
Description: Ubuntu 22.04.5 LTS
Release: 22.04
apport file in the attachment
fstab entry:
cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=3f1bdecc-af3b-4c65-a8e5-208b58e147b9 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=5cd2a861-4079-4492-bf6b-e60c6d406b4e none swap sw 0 0
#/dev/sda1 /mapsrw ext4 defaults 0 1
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/sr1 /media/cdrom1 udf,iso9660 user,noauto 0 0
/dev/sr0 /mapsro udf,iso9660 ro 0 0
overlay /opt/iso overlay
lowerdir=/mapsro,upperdir=/mapsrw,workdir=/mapswork,defaults,_netdev,x-systemd.requires-
mounts-for=/mapsro
/dev/sr1 /gcdro udf,iso9660 ro 0 0
overlay /opt/iso/map/gcd overlay lowerdir=/gcdro,upperdir=/gcdrw,workdir=/gcdwork,defaults,_netdev,x-systemd.requires-mounts-for=/gcdro
dmesg output after update
[ 2.791617] vmwgfx 0000:00:0f.0: [drm] Screen Target display unit initialized
[ 2.792712] vmwgfx 0000:00:0f.0: [drm] Fifo max 0x00040000 min 0x00001000 cap 0x0000077f
[ 2.793589] vmwgfx 0000:00:0f.0: [drm] Using command buffers with DMA pool.
[ 2.793595] vmwgfx 0000:00:0f.0: [drm] Available shader model: Legacy.
[ 2.795045] fbcon: svgadrmfb (fb0) is primary device
[ 2.795542] Console: switching to colour frame buffer device 100x37
[ 2.799710] [drm] Initialized vmwgfx 2.19.0 20210722 for 0000:00:0f.0 on minor 0
[ 2.800406] systemd[1]: Finished Load Kernel Modules.
[ 2.801077] systemd[1]: Starting Apply Kernel Variables...
[ 2.801185] systemd[1]: Started Journal Service.
[ 2.805436] systemd-journald[434]: Received client request to flush runtime journal.
[ 2.912001] vmw_vmci 0000:00:07.7: Using capabilities 0xc
[ 2.912403] Guest personality initialized and is active
[ 2.916033] VMCI host device registered (name=vmci, major=10, minor=123)
[ 2.916035] Initialized host personality
[ 2.960298] Adding 4317180k swap on /dev/sda5. Priority:-2 extents:1 across:4317180k SSFS
[ 2.975943] RAPL PMU: API unit is 2^-32 Joules, 0 fixed counters, 10737418240 ms ovfl timer
[ 2.979501] cryptd: max_cpu_qlen set to 1000
[ 2.989102] AVX2 version of gcm_enc/dec engaged.
[ 2.989205] AES CTR mode by8 optimization enabled
[ 3.129983] RPC: Registered named UNIX socket transport module.
[ 3.129986] RPC: Registered udp transport module.
[ 3.129986] RPC: Registered tcp transport module.
[ 3.129987] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 3.134884] audit: type=1400 audit(1742377247.423:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=669 comm="apparmor_parser"
[ 3.134888] audit: type=1400 audit(1742377247.423:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=669 comm="apparmor_parser"
[ 3.134905] audit: type=1400 audit(1742377247.423:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=668 comm="apparmor_parser"
[ 3.137445] audit: type=1400 audit(1742377247.427:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=673 comm="apparmor_parser"
[ 3.137447] audit: type=1400 audit(1742377247.427:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=673 comm="apparmor_parser"
[ 3.137450] audit: type=1400 audit(1742377247.427:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=673 comm="apparmor_parser"
[ 3.140695] audit: type=1400 audit(1742377247.431:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="ubuntu_pro_apt_news" pid=671 comm="apparmor_parser"
[ 3.142882] audit: type=1400 audit(1742377247.431:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="tcpdump" pid=674 comm="apparmor_parser"
[ 3.146434] audit: type=1400 audit(1742377247.435:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=670 comm="apparmor_parser"
[ 3.147041] vmxnet3 0000:03:00.0 ens160: intr type 3, mode 0, 9 vectors allocated
[ 3.149459] vmxnet3 0000:03:00.0 ens160: NIC Link is Up 10000 Mbps
[ 3.192250] NET: Registered PF_VSOCK protocol family
[ 16.512894] overlayfs: null uuid detected in lower fs '/', falling back to xino=off,index=off,nfs_export=off.
[ 16.518113] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.518118] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.518145] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.518146] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.518159] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.518160] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.520084] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.520089] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.520125] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.520126] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.522079] FS-Cache: Loaded
[ 16.554821] FS-Cache: Netfs 'nfs' registered for caching
[ 16.684508] NFS: Registering the id_resolver key type
[ 16.684517] Key type id_resolver registered
[ 16.684518] Key type id_legacy registered
[ 20.160812] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.160853] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166339] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166380] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166740] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166773] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166829] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166859] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166912] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166941] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166995] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.167024] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.184362] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.184405] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.198854] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.198895] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.199000] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.199688] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.212325] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.213678] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.219212] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.220536] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.228836] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.230183] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.384191] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.385550] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.386987] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.388239] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.389527] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.390973] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.540547] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.541910] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.587198] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.588558] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.590494] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.591733] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.593009] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.594276] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.595543] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.596853] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.598310] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.599556] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.792315] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.793705] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 29.068728] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 29.070077] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.042175] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.043563] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.271936] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.273292] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.484056] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.485421] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.612029] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.613398] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.787934] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.789298] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2103598/+subscriptions
Importance: Undecided
Status: New
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2103598
Title:
NFS, overlay, fstab issue after update to kernel 5.15.0-133-generic
and -134
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Jammy:
New
Bug description:
Hello,
After updating from 5.15.0-131-generic on ubuntu 22.04 to newer versions, our fstab mountpoints for overlays are failing. we are using them to mount ISO (VM's on vsphere). It happens on all ubuntu vm's.
lsb_release -rd
Description: Ubuntu 22.04.5 LTS
Release: 22.04
apport file in the attachment
fstab entry:
cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=3f1bdecc-af3b-4c65-a8e5-208b58e147b9 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=5cd2a861-4079-4492-bf6b-e60c6d406b4e none swap sw 0 0
#/dev/sda1 /mapsrw ext4 defaults 0 1
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/sr1 /media/cdrom1 udf,iso9660 user,noauto 0 0
/dev/sr0 /mapsro udf,iso9660 ro 0 0
overlay /opt/iso overlay
lowerdir=/mapsro,upperdir=/mapsrw,workdir=/mapswork,defaults,_netdev,x-systemd.requires-
mounts-for=/mapsro
/dev/sr1 /gcdro udf,iso9660 ro 0 0
overlay /opt/iso/map/gcd overlay lowerdir=/gcdro,upperdir=/gcdrw,workdir=/gcdwork,defaults,_netdev,x-systemd.requires-mounts-for=/gcdro
dmesg output after update
[ 2.791617] vmwgfx 0000:00:0f.0: [drm] Screen Target display unit initialized
[ 2.792712] vmwgfx 0000:00:0f.0: [drm] Fifo max 0x00040000 min 0x00001000 cap 0x0000077f
[ 2.793589] vmwgfx 0000:00:0f.0: [drm] Using command buffers with DMA pool.
[ 2.793595] vmwgfx 0000:00:0f.0: [drm] Available shader model: Legacy.
[ 2.795045] fbcon: svgadrmfb (fb0) is primary device
[ 2.795542] Console: switching to colour frame buffer device 100x37
[ 2.799710] [drm] Initialized vmwgfx 2.19.0 20210722 for 0000:00:0f.0 on minor 0
[ 2.800406] systemd[1]: Finished Load Kernel Modules.
[ 2.801077] systemd[1]: Starting Apply Kernel Variables...
[ 2.801185] systemd[1]: Started Journal Service.
[ 2.805436] systemd-journald[434]: Received client request to flush runtime journal.
[ 2.912001] vmw_vmci 0000:00:07.7: Using capabilities 0xc
[ 2.912403] Guest personality initialized and is active
[ 2.916033] VMCI host device registered (name=vmci, major=10, minor=123)
[ 2.916035] Initialized host personality
[ 2.960298] Adding 4317180k swap on /dev/sda5. Priority:-2 extents:1 across:4317180k SSFS
[ 2.975943] RAPL PMU: API unit is 2^-32 Joules, 0 fixed counters, 10737418240 ms ovfl timer
[ 2.979501] cryptd: max_cpu_qlen set to 1000
[ 2.989102] AVX2 version of gcm_enc/dec engaged.
[ 2.989205] AES CTR mode by8 optimization enabled
[ 3.129983] RPC: Registered named UNIX socket transport module.
[ 3.129986] RPC: Registered udp transport module.
[ 3.129986] RPC: Registered tcp transport module.
[ 3.129987] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 3.134884] audit: type=1400 audit(1742377247.423:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=669 comm="apparmor_parser"
[ 3.134888] audit: type=1400 audit(1742377247.423:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=669 comm="apparmor_parser"
[ 3.134905] audit: type=1400 audit(1742377247.423:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=668 comm="apparmor_parser"
[ 3.137445] audit: type=1400 audit(1742377247.427:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=673 comm="apparmor_parser"
[ 3.137447] audit: type=1400 audit(1742377247.427:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=673 comm="apparmor_parser"
[ 3.137450] audit: type=1400 audit(1742377247.427:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=673 comm="apparmor_parser"
[ 3.140695] audit: type=1400 audit(1742377247.431:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="ubuntu_pro_apt_news" pid=671 comm="apparmor_parser"
[ 3.142882] audit: type=1400 audit(1742377247.431:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="tcpdump" pid=674 comm="apparmor_parser"
[ 3.146434] audit: type=1400 audit(1742377247.435:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=670 comm="apparmor_parser"
[ 3.147041] vmxnet3 0000:03:00.0 ens160: intr type 3, mode 0, 9 vectors allocated
[ 3.149459] vmxnet3 0000:03:00.0 ens160: NIC Link is Up 10000 Mbps
[ 3.192250] NET: Registered PF_VSOCK protocol family
[ 16.512894] overlayfs: null uuid detected in lower fs '/', falling back to xino=off,index=off,nfs_export=off.
[ 16.518113] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.518118] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.518145] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.518146] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.518159] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.518160] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.520084] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.520089] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.520125] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 16.520126] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 16.522079] FS-Cache: Loaded
[ 16.554821] FS-Cache: Netfs 'nfs' registered for caching
[ 16.684508] NFS: Registering the id_resolver key type
[ 16.684517] Key type id_resolver registered
[ 16.684518] Key type id_legacy registered
[ 20.160812] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.160853] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166339] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166380] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166740] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166773] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166829] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166859] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166912] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.166941] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.166995] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.167024] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.184362] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.184405] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.198854] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.198895] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.199000] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.199688] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.212325] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.213678] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.219212] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.220536] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.228836] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.230183] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.384191] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.385550] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.386987] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.388239] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.389527] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.390973] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.540547] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.541910] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.587198] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.588558] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.590494] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.591733] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.593009] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.594276] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.595543] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.596853] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.598310] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.599556] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 20.792315] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 20.793705] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 29.068728] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 29.070077] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.042175] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.043563] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.271936] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.273292] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.484056] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.485421] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.612029] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.613398] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
[ 2636.787934] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 2016 not allocated in directory (ino 318)
[ 2636.789298] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 318) has entry at pos 2016 with unaligned lenght of impUse field
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2103598/+subscriptions
[Bug 2104936] Re: Freeze (Ubuntu 25.04 loading screen) on the first loading after installation
Three issues there:
1. The i915 kernel driver is crashing(?) on startup (I've seen this in
another bug report too):
i915 0000:00:02.0: [drm] Port B asks to use VBT vswing/preemph tables
2. The Bluetooth kernel driver is taking 20-30 seconds to start up
(download firmware?).
3. Again "nvidia: Spawned process '/sbin/modprobe nvidia-drm' [870] is
taking longer than 59s to complete." but that could just be caused by
#1.
So overall it's probably a kernel bug. Certainly the workaround you
mention in comment #7 just sounds like booting an older kernel version
that's free of the bug(s).
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-570 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2104936
Title:
Freeze (Ubuntu 25.04 loading screen) on the first loading after
installation
Status in linux package in Ubuntu:
New
Status in nvidia-graphics-drivers-570 package in Ubuntu:
New
Bug description:
After having a strange issue on installation (the installer asked me
if I wanted to restart, I clicked yes, it closed, but nothing
happened. I had to shutdown the live OS myself. Maybe I should have do
a 'ubuntu-bug' before rebooting, but by the way I don't know if I had
to choose 'installation' or 'installer').
On the first boot of ubuntu 25.04 beta the loading screen (computer
logo + ubuntu logo) was like freeze. After waiting 1 min then doing
CTRL+ALT+DEL, now the OS does boot fine (tried 3 times).
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 6.14.0-11.11-generic 6.14.0-rc7
Uname: Linux 6.14.0-11-generic x86_64
ApportVersion: 2.32.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 28 15:30:36 2025
InstallCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-11-generic root=UUID=f9796f07-9884-418e-9095-b044d814faaa ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
InstallationDate: Installed on 2025-03-28 (0 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Beta amd64 (20250326.6)
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: ubiquity
Symptom: installer
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2104936/+subscriptions
1. The i915 kernel driver is crashing(?) on startup (I've seen this in
another bug report too):
i915 0000:00:02.0: [drm] Port B asks to use VBT vswing/preemph tables
2. The Bluetooth kernel driver is taking 20-30 seconds to start up
(download firmware?).
3. Again "nvidia: Spawned process '/sbin/modprobe nvidia-drm' [870] is
taking longer than 59s to complete." but that could just be caused by
#1.
So overall it's probably a kernel bug. Certainly the workaround you
mention in comment #7 just sounds like booting an older kernel version
that's free of the bug(s).
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-570 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2104936
Title:
Freeze (Ubuntu 25.04 loading screen) on the first loading after
installation
Status in linux package in Ubuntu:
New
Status in nvidia-graphics-drivers-570 package in Ubuntu:
New
Bug description:
After having a strange issue on installation (the installer asked me
if I wanted to restart, I clicked yes, it closed, but nothing
happened. I had to shutdown the live OS myself. Maybe I should have do
a 'ubuntu-bug' before rebooting, but by the way I don't know if I had
to choose 'installation' or 'installer').
On the first boot of ubuntu 25.04 beta the loading screen (computer
logo + ubuntu logo) was like freeze. After waiting 1 min then doing
CTRL+ALT+DEL, now the OS does boot fine (tried 3 times).
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 6.14.0-11.11-generic 6.14.0-rc7
Uname: Linux 6.14.0-11-generic x86_64
ApportVersion: 2.32.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 28 15:30:36 2025
InstallCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-11-generic root=UUID=f9796f07-9884-418e-9095-b044d814faaa ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
InstallationDate: Installed on 2025-03-28 (0 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Beta amd64 (20250326.6)
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: ubiquity
Symptom: installer
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2104936/+subscriptions
[Bug 2106352] Re: Audio freezes/loops (UBSAN DAPM errors) on Acer Chromebook 14 (Edgar) / Atom x5-E8000 / RT5650
Thank you for reporting this and helping make Ubuntu better. Could you
please boot into a Ubuntu kernel (not third party kernel) and execute
the following command only once, as it will automatically gather
debugging information, in a terminal:
sudo apport-collect 2106352
Does it ever work on older kernels?
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2106352
Title:
Audio freezes/loops (UBSAN DAPM errors) on Acer Chromebook 14 (Edgar)
/ Atom x5-E8000 / RT5650
Status in linux package in Ubuntu:
New
Bug description:
Audio freezes/loops (UBSAN DAPM errors) on Acer Chromebook 14 (Edgar)
/ Atom x5-E8000 / RT5650 (SOF) with Kernel 6.8 / 6.11
Hardware:
System: Acer Chromebook 14 (CB3-431)
Board Name: GOOGLE Edgar (Confirmed via dmidecode)
CPU: Intel(R) Atom(TM) x5-E8000 CPU @ 1.04GHz (Braswell)
Audio Controller: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller [8086:2284] (rev 35) - Driver snd_hda_intel (Handles HDMI - Card 0)
Audio Codec: Realtek RT5650 (Detected by ALSA as sof-bytcht rt5650 - Card 1, uses rt5645 SOF topology sof-cht-rt5645.tplg)
Software:
Distribution: Linux Mint 22.1 "Xia" (Based on Ubuntu 24.04 "Noble Numbat")
Kernel Versions Tested (All Show Issue):
6.8.0-51-generic
6.8.0-57-generic (Currently Active: Linux mintbook 6.8.0-57-generic #59-Ubuntu SMP PREEMPT_DYNAMIC Sat Mar 15 17:40:59 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux)
6.11.0-21-generic
Audio Server: PipeWire 1.0.5 (with WirePlumber session manager)
Problem Description:
Audio output through the internal speakers/headphone jack works
correctly for a short, variable period after booting (ranging from ~1
minute to ~10 minutes). While playing audio (e.g., YouTube in Firefox,
native games like Chocolate Doom), the sound suddenly cuts out and is
often replaced by a continuous, loud looping beep/tone.
Sometimes, closing the application that was playing audio causes the
looping sound to stop after several seconds, and system audio may
function again temporarily before freezing again shortly after. The
issue occurs reliably across all tested kernels available in the Linux
Mint 22.1 repositories (6.8 series, 6.11 series).
Key Evidence (Kernel Log Errors):
During boot, the kernel logs consistently show errors related to the
Realtek codec detection and, critically, UBSAN (Undefined Behavior
Sanitizer) errors within the ALSA core's DAPM (Dynamic Audio Power
Management) code during the initialization of the SOF sound card.
These errors strongly suggest a kernel bug is the root cause of the
instability.
Key Evidence (Kernel Log Errors):
During boot, the kernel logs consistently show errors related to the
Realtek codec detection and, critically, UBSAN (Undefined Behavior
Sanitizer) errors within the ALSA core's DAPM (Dynamic Audio Power
Management) code during the initialization of the SOF sound card.
These errors strongly suggest a kernel bug is the root cause of the
instability.
Relevant logs from dmesg on kernel 6.8.0-57-generic:
[ 11.222920] rt5640 i2c-10EC5650:00: Device with ID register 0x6419 is not rt5640/39
[ 11.830233] rt5645 i2c-10EC5650:00: Detected Google Chrome platform
[ 12.102210] sof-audio-acpi-intel-byt 808622A8:00: unknown sof_ext_man header type 3 size 0x30
[ 12.735442] UBSAN: shift-out-of-bounds in /build/linux-AUvUe4/linux-6.8.0/sound/soc/soc-dapm.c:814:15
[ 12.735535] snd_soc_dapm_add_path.cold+0x1b/0x5c [snd_soc_core]
[ 12.735615] snd_soc_dapm_add_route+0x313/0x600 [snd_soc_core]
[ 12.735688] snd_soc_dapm_add_routes+0x45/0x80 [snd_soc_core]
[ 12.735753] soc_probe_component+0x265/0x390 [snd_soc_core]
[ 12.735815] snd_soc_bind_card+0x3c1/0x8c0 [snd_soc_core]
[ 12.735876] ? __pfx_devm_card_release+0x10/0x10 [snd_soc_core]
[ 12.735943] snd_soc_register_card+0x145/0x170 [snd_soc_core]
[ 12.736004] devm_snd_soc_register_card+0x48/0xb0 [snd_soc_core]
[ 12.736071] snd_cht_mc_probe+0x49b/0x830 [snd_soc_sst_cht_bsw_rt5645]
[ 12.736173] ? __pfx_snd_cht_mc_driver_init+0x10/0x10 [snd_soc_sst_cht_bsw_rt5645]
[ 12.736189] snd_cht_mc_driver_init+0x1c/0xff0 [snd_soc_sst_cht_bsw_rt5645]
[ 13.022618] UBSAN: shift-out-of-bounds in /build/linux-AUvUe4/linux-6.8.0/sound/soc/soc-dapm.c:3427:13
[ 13.022710] snd_soc_dapm_put_volsw.cold+0x94/0x131 [snd_soc_core]
[ 13.022797] snd_ctl_elem_write+0x109/0x1c0 [snd]
[ 13.022828] snd_ctl_ioctl+0x4a5/0x730 [snd]
[ 13.023098] UBSAN: shift-out-of-bounds in /build/linux-AUvUe4/linux-6.8.0/sound/soc/soc-dapm.c:3428:15
[ 13.023150] snd_soc_dapm_put_volsw.cold+0x127/0x131 [snd_soc_core]
[ 13.023220] snd_ctl_elem_write+0x109/0x1c0 [snd]
[ 13.023248] snd_ctl_ioctl+0x4a5/0x730 [snd]
[ 13.023516] UBSAN: shift-out-of-bounds in /build/linux-AUvUe4/linux-6.8.0/sound/soc/soc-dapm.c:3430:51
[ 13.023571] snd_soc_dapm_put_volsw.cold+0xba/0x131 [snd_soc_core]
[ 13.023643] snd_ctl_elem_write+0x109/0x1c0 [snd]
[ 13.023672] snd_ctl_ioctl+0x4a5/0x730 [snd]
Troubleshooting Steps Attempted:
Tested multiple kernels available via Linux Mint Update Manager (6.8.0-51, 6.8.0-57, 6.11.0-21) - Problem persists on all.
Attempted disabling power saving for snd_hda_intel via modprobe.d - Ineffective (targets wrong driver component). Power save parameter for snd_sof module not found.
Attempted forcing legacy audio driver via kernel parameter snd_intel_dspcfg.dsp_driver=1 - Problem persists.
Checked ALSA / PipeWire / WirePlumber configurations - Appear standard (no custom user configs found).
Problem occurs with different applications (Firefox/YouTube, Chocolate Doom).
Expected Result: Audio playback should be stable without freezes or
looping sounds.
Actual Result: Audio freezes and often loops after short periods of
use, associated with kernel DAPM errors during initialization.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2106352/+subscriptions
please boot into a Ubuntu kernel (not third party kernel) and execute
the following command only once, as it will automatically gather
debugging information, in a terminal:
sudo apport-collect 2106352
Does it ever work on older kernels?
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2106352
Title:
Audio freezes/loops (UBSAN DAPM errors) on Acer Chromebook 14 (Edgar)
/ Atom x5-E8000 / RT5650
Status in linux package in Ubuntu:
New
Bug description:
Audio freezes/loops (UBSAN DAPM errors) on Acer Chromebook 14 (Edgar)
/ Atom x5-E8000 / RT5650 (SOF) with Kernel 6.8 / 6.11
Hardware:
System: Acer Chromebook 14 (CB3-431)
Board Name: GOOGLE Edgar (Confirmed via dmidecode)
CPU: Intel(R) Atom(TM) x5-E8000 CPU @ 1.04GHz (Braswell)
Audio Controller: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller [8086:2284] (rev 35) - Driver snd_hda_intel (Handles HDMI - Card 0)
Audio Codec: Realtek RT5650 (Detected by ALSA as sof-bytcht rt5650 - Card 1, uses rt5645 SOF topology sof-cht-rt5645.tplg)
Software:
Distribution: Linux Mint 22.1 "Xia" (Based on Ubuntu 24.04 "Noble Numbat")
Kernel Versions Tested (All Show Issue):
6.8.0-51-generic
6.8.0-57-generic (Currently Active: Linux mintbook 6.8.0-57-generic #59-Ubuntu SMP PREEMPT_DYNAMIC Sat Mar 15 17:40:59 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux)
6.11.0-21-generic
Audio Server: PipeWire 1.0.5 (with WirePlumber session manager)
Problem Description:
Audio output through the internal speakers/headphone jack works
correctly for a short, variable period after booting (ranging from ~1
minute to ~10 minutes). While playing audio (e.g., YouTube in Firefox,
native games like Chocolate Doom), the sound suddenly cuts out and is
often replaced by a continuous, loud looping beep/tone.
Sometimes, closing the application that was playing audio causes the
looping sound to stop after several seconds, and system audio may
function again temporarily before freezing again shortly after. The
issue occurs reliably across all tested kernels available in the Linux
Mint 22.1 repositories (6.8 series, 6.11 series).
Key Evidence (Kernel Log Errors):
During boot, the kernel logs consistently show errors related to the
Realtek codec detection and, critically, UBSAN (Undefined Behavior
Sanitizer) errors within the ALSA core's DAPM (Dynamic Audio Power
Management) code during the initialization of the SOF sound card.
These errors strongly suggest a kernel bug is the root cause of the
instability.
Key Evidence (Kernel Log Errors):
During boot, the kernel logs consistently show errors related to the
Realtek codec detection and, critically, UBSAN (Undefined Behavior
Sanitizer) errors within the ALSA core's DAPM (Dynamic Audio Power
Management) code during the initialization of the SOF sound card.
These errors strongly suggest a kernel bug is the root cause of the
instability.
Relevant logs from dmesg on kernel 6.8.0-57-generic:
[ 11.222920] rt5640 i2c-10EC5650:00: Device with ID register 0x6419 is not rt5640/39
[ 11.830233] rt5645 i2c-10EC5650:00: Detected Google Chrome platform
[ 12.102210] sof-audio-acpi-intel-byt 808622A8:00: unknown sof_ext_man header type 3 size 0x30
[ 12.735442] UBSAN: shift-out-of-bounds in /build/linux-AUvUe4/linux-6.8.0/sound/soc/soc-dapm.c:814:15
[ 12.735535] snd_soc_dapm_add_path.cold+0x1b/0x5c [snd_soc_core]
[ 12.735615] snd_soc_dapm_add_route+0x313/0x600 [snd_soc_core]
[ 12.735688] snd_soc_dapm_add_routes+0x45/0x80 [snd_soc_core]
[ 12.735753] soc_probe_component+0x265/0x390 [snd_soc_core]
[ 12.735815] snd_soc_bind_card+0x3c1/0x8c0 [snd_soc_core]
[ 12.735876] ? __pfx_devm_card_release+0x10/0x10 [snd_soc_core]
[ 12.735943] snd_soc_register_card+0x145/0x170 [snd_soc_core]
[ 12.736004] devm_snd_soc_register_card+0x48/0xb0 [snd_soc_core]
[ 12.736071] snd_cht_mc_probe+0x49b/0x830 [snd_soc_sst_cht_bsw_rt5645]
[ 12.736173] ? __pfx_snd_cht_mc_driver_init+0x10/0x10 [snd_soc_sst_cht_bsw_rt5645]
[ 12.736189] snd_cht_mc_driver_init+0x1c/0xff0 [snd_soc_sst_cht_bsw_rt5645]
[ 13.022618] UBSAN: shift-out-of-bounds in /build/linux-AUvUe4/linux-6.8.0/sound/soc/soc-dapm.c:3427:13
[ 13.022710] snd_soc_dapm_put_volsw.cold+0x94/0x131 [snd_soc_core]
[ 13.022797] snd_ctl_elem_write+0x109/0x1c0 [snd]
[ 13.022828] snd_ctl_ioctl+0x4a5/0x730 [snd]
[ 13.023098] UBSAN: shift-out-of-bounds in /build/linux-AUvUe4/linux-6.8.0/sound/soc/soc-dapm.c:3428:15
[ 13.023150] snd_soc_dapm_put_volsw.cold+0x127/0x131 [snd_soc_core]
[ 13.023220] snd_ctl_elem_write+0x109/0x1c0 [snd]
[ 13.023248] snd_ctl_ioctl+0x4a5/0x730 [snd]
[ 13.023516] UBSAN: shift-out-of-bounds in /build/linux-AUvUe4/linux-6.8.0/sound/soc/soc-dapm.c:3430:51
[ 13.023571] snd_soc_dapm_put_volsw.cold+0xba/0x131 [snd_soc_core]
[ 13.023643] snd_ctl_elem_write+0x109/0x1c0 [snd]
[ 13.023672] snd_ctl_ioctl+0x4a5/0x730 [snd]
Troubleshooting Steps Attempted:
Tested multiple kernels available via Linux Mint Update Manager (6.8.0-51, 6.8.0-57, 6.11.0-21) - Problem persists on all.
Attempted disabling power saving for snd_hda_intel via modprobe.d - Ineffective (targets wrong driver component). Power save parameter for snd_sof module not found.
Attempted forcing legacy audio driver via kernel parameter snd_intel_dspcfg.dsp_driver=1 - Problem persists.
Checked ALSA / PipeWire / WirePlumber configurations - Appear standard (no custom user configs found).
Problem occurs with different applications (Firefox/YouTube, Chocolate Doom).
Expected Result: Audio playback should be stable without freezes or
looping sounds.
Actual Result: Audio freezes and often loops after short periods of
use, associated with kernel DAPM errors during initialization.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2106352/+subscriptions
[Bug 2093871] Re: Introduce and use sendpages_ok() instead of sendpage_ok() in nvme-tcp and drbd
Performing verification for oracular.
Firstly, I started with 6.11.0-21-generic with the following commit
reverted:
commit ab99a87542f194f28e2364a42afbf9fb48b1c724
Author: Ofir Gal <ofir.gal@volumez.com>
Date: Fri Jun 7 10:27:44 2024 +0300
Subject: md/md-bitmap: fix writing non bitmap pages
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ab99a87542f194f28e2364a42afbf9fb48b1c724
This is because the testcases are the same, as the above bug was fixed due to
this bug existing in the first place.
I ran the reproducer:
sudo[1244]: mruffell : TTY=pts/0 ; PWD=/home/mruffell/blktests ; USER=root ; COMMAND=./check md/001
sudo[1244]: pam_unix(sudo:session): session opened for user root(uid=0) by mruffell(uid=1008)
unknown: run blktests md/001 at 2025-04-07 04:17:58
root[1280]: run blktests md/001
brd: module loaded
(udev-worker)[1270]: dm-0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1.
Key type psk registered
nvmet: adding nsid 1 to subsystem blktests-subsystem-1
nvmet_tcp: enabling port 0 (127.0.0.1:4420)
nvmet: creating nvm controller 1 for subsystem blktests-subsystem-1 for NQN nqn.2014-08.org.nvmexpress:uuid:0f01fb42-9f7f-4856-b0b3-51e60b8de349.
nvme nvme1: creating 2 I/O queues.
nvme nvme1: mapped 2/0/0 default/read/poll queues.
nvme nvme1: new ctrl: NQN "blktests-subsystem-1", addr 127.0.0.1:4420, hostnqn: nqn.2014-08.org.nvmexpress:uuid:0f01fb42-9f7f-4856-b0b3-51e60b8de349
(udev-worker)[1270]: nvme1n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme1n1' failed with exit code 1.
(udev-worker)[1270]: md127: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/md127' failed with exit code 1.
md/raid1:md127: active with 1 out of 2 mirrors
------------[ cut here ]------------
WARNING: CPU: 0 PID: 60 at net/core/skbuff.c:7140 skb_splice_from_iter+0x1b5/0x370
Modules linked in: nvme_tcp nvmet_tcp nvmet nvme_keyring brd raid1 tls cfg80211 8021q garp mrp stp llc binfmt_misc nls_iso8859_1 intel_rapl_msr intel_rapl_common intel_uncore_frequency_common skx_edac_common nfit crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic ghash_clmulni_intel sha256_ssse3 sha1_ssse3 aesni_intel crypto_simd cryptd rapl pvpanic_mmio pvpanic psmouse i2c_piix4 i2c_smbus nvme input_leds mac_hid serio_raw sch_fq_codel nvme_fabrics nvme_core nvme_auth efi_pstore dm_multipath nfnetlink vsock_loopback vmw_vsock_virtio_transport_common vmw_vsock_vmci_transport vsock vmw_vmci dmi_sysfs virtio_rng ip_tables x_tables autofs4
CPU: 0 UID: 0 PID: 60 Comm: kworker/0:1H Not tainted 6.11.0-21-generic #20+TEST404844v20250403b1-Ubuntu
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Workqueue: nvme_tcp_wq nvme_tcp_io_work [nvme_tcp]
RIP: 0010:skb_splice_from_iter+0x1b5/0x370
Code: cc 49 89 cd f6 c2 01 0f 85 20 01 00 00 66 90 48 89 da 8b 52 30 81 e2 00 00 00 82 81 fa 00 00 00 80 0f 85 41 ff ff ff 4d 89 fe <0f> 0b 49 c7 c5 fb ff ff ff 48 8b 85 68 ff ff ff 41 01 46 70 41 01
RSP: 0018:ffffac5c0020ba18 EFLAGS: 00010246
RAX: 0000000000000000 RBX: fffff04bc4c1edc0 RCX: 0000000000001000
RDX: 0000000080000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffac5c0020bac0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000004000
R13: 0000000000001000 R14: ffffa094c37d6c00 R15: ffffa094c37d6c00
FS: 0000000000000000(0000) GS:ffffa095f7c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007e272064c6c0 CR3: 0000000104e8c005 CR4: 00000000003706f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
? show_trace_log_lvl+0x1be/0x310
? show_trace_log_lvl+0x1be/0x310
? tcp_sendmsg_locked+0x36e/0xe40
? show_regs.part.0+0x22/0x30
? show_regs.cold+0x8/0x10
? skb_splice_from_iter+0x1b5/0x370
? __warn.cold+0xa7/0x101
? skb_splice_from_iter+0x1b5/0x370
? report_bug+0x114/0x160
? handle_bug+0x51/0xa0
? exc_invalid_op+0x18/0x80
? asm_exc_invalid_op+0x1b/0x20
? skb_splice_from_iter+0x1b5/0x370
? skb_splice_from_iter+0x12a/0x370
tcp_sendmsg_locked+0x36e/0xe40
? tcp_push+0x12d/0x170
? tcp_sendmsg_locked+0xac7/0xe40
? tcp_cleanup_rbuf+0x42/0x90
tcp_sendmsg+0x2c/0x50
inet_sendmsg+0x42/0x80
sock_sendmsg+0x118/0x140
nvme_tcp_try_send_data+0x181/0x4c0 [nvme_tcp]
nvme_tcp_try_send+0x1a6/0x230 [nvme_tcp]
nvme_tcp_io_work+0x6c/0x110 [nvme_tcp]
process_one_work+0x174/0x350
worker_thread+0x32a/0x460
? _raw_spin_unlock_irqrestore+0x11/0x60
? __pfx_worker_thread+0x10/0x10
kthread+0xe1/0x110
? __pfx_kthread+0x10/0x10
ret_from_fork+0x44/0x70
? __pfx_kthread+0x10/0x10
ret_from_fork_asm+0x1a/0x30
</TASK>
---[ end trace 0000000000000000 ]---
Okay, we can reproduce the issue.
I then enabled -proposed, and installed 6.11.0-24-generic, note, which
contains:
commit ab99a87542f194f28e2364a42afbf9fb48b1c724
Author: Ofir Gal <ofir.gal@volumez.com>
Date: Fri Jun 7 10:27:44 2024 +0300
Subject: md/md-bitmap: fix writing non bitmap pages
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ab99a87542f194f28e2364a42afbf9fb48b1c724
AND the three fixed we are testing:
commit 23a55f4492fcf868d068da31a2cd30c15f46207d
Author: Ofir Gal <ofir.gal@volumez.com>
Date: Thu Jul 18 11:45:12 2024 +0300
Subject: net: introduce helper sendpages_ok()
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=23a55f4492fcf868d068da31a2cd30c15f46207d
commit 6af7331a70b4888df43ec1d7e1803ae2c43b6981
Author: Ofir Gal <ofir.gal@volumez.com>
Date: Thu Jul 18 11:45:13 2024 +0300
Subject: nvme-tcp: use sendpages_ok() instead of sendpage_ok()
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6af7331a70b4888df43ec1d7e1803ae2c43b6981
commit 7960af373ade3b39e10106ef415e43a1d2aa48c6
Author: Ofir Gal <ofir.gal@volumez.com>
Date: Thu Jul 18 11:45:14 2024 +0300
Subject: drbd: use sendpages_ok() instead of sendpage_ok()
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7960af373ade3b39e10106ef415e43a1d2aa48c6
I rebooted and ran the reproducer:
$ uname -rv
6.11.0-24-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 14 18:13:56 UTC 2025
$ sudo ./check md/001
md/001 (Raid with bitmap on tcp nvmet with opt-io-size over bitmap size) [passed]
runtime ... 0.451
Just to make sure that the three commits really did fix the issue, I then
built and booted into 6.11.0-24-generic, again with
commit ab99a87542f194f28e2364a42afbf9fb48b1c724
Author: Ofir Gal <ofir.gal@volumez.com>
Date: Fri Jun 7 10:27:44 2024 +0300
Subject: md/md-bitmap: fix writing non bitmap pages
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ab99a87542f194f28e2364a42afbf9fb48b1c724
reverted, so we just test the new fixes only.
$ uname -rv
6.11.0-24-generic #24+TEST404844v20250328b1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 28
$ sudo ./check md/001
md/001 (Raid with bitmap on tcp nvmet with opt-io-size over bitmap size) [passed]
runtime 0.451s ... 0.449s
We continue to pass with the new patches only.
The kernel in -proposed fixes the issue, happy to mark verified for
oracular.
** Tags removed: verification-needed-oracular-linux
** Tags added: verification-done-oracular-linux
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2093871
Title:
Introduce and use sendpages_ok() instead of sendpage_ok() in nvme-tcp
and drbd
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Fix Committed
Status in linux source package in Oracular:
Fix Committed
Bug description:
BugLink: https://bugs.launchpad.net/bugs/2093871
[Impact]
Currently the nvme-tcp and drbd subsystems try to enable the MSG_SPLICE_PAGES
flag on pages to be written, and when MSG_SPLICE_PAGES is set, eventually it
calls skb_splice_from_iter(), which then checks all pages with sendpage_ok()
to see if all the pages are sendable.
At the moment, both subsystems only check the first page in a potentially
contiguous block of pages, if they are sendpage_ok(), and if the first page is,
then it just assumes all the rest are sendpage_ok() too, and sends the I/O off
to eventually be found out by skb_splice_from_iter(). If one or more of the
pages in the contiguous block is not sendpage_ok(), then we get a warn printed,
data transfer is aborted. In the nvme-tcp case, IO then hangs.
This patchset introduces sendpages_ok() which iterates over each page in a
contiguous block, checks if it is sendpage_ok(), and only returns true if all
of them are.
This resolves the whole MSG_SPLICE_PAGES flag situation, since you can now
depend on the result of sendpages_ok(), instead of just assuming everything is
okay.
This issue is what caused bug 2075110 [0] to be discovered in the first place,
since it was responsible for contigious blocks of pages where the first was
sendpage_ok(), but pages further into the block were not.
[0] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2075110
Even with "md/md-bitmap: fix writing non bitmap pages" applied, the issue can
still happen, e.g. with merged IO pages, so this fix is still needed to
eliminate the issue.
[Fix]
The fixes landed in mainline 6.12-rc1:
commit 23a55f4492fcf868d068da31a2cd30c15f46207d
Author: Ofir Gal <ofir.gal@volumez.com>
Date: Thu Jul 18 11:45:12 2024 +0300
Subject: net: introduce helper sendpages_ok()
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=23a55f4492fcf868d068da31a2cd30c15f46207d
commit 6af7331a70b4888df43ec1d7e1803ae2c43b6981
Author: Ofir Gal <ofir.gal@volumez.com>
Date: Thu Jul 18 11:45:13 2024 +0300
Subject: nvme-tcp: use sendpages_ok() instead of sendpage_ok()
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6af7331a70b4888df43ec1d7e1803ae2c43b6981
commit 7960af373ade3b39e10106ef415e43a1d2aa48c6
Author: Ofir Gal <ofir.gal@volumez.com>
Date: Thu Jul 18 11:45:14 2024 +0300
Subject: drbd: use sendpages_ok() instead of sendpage_ok()
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7960af373ade3b39e10106ef415e43a1d2aa48c6
They are needed for noble and oracular.
[Testcase]
This is the same testcase as the original bug 2075110 [0], as the fix is
designed to prevent it or similar other bugs from happening again.
[0] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2075110
Because of this, the fix:
commit ab99a87542f194f28e2364a42afbf9fb48b1c724
Author: Ofir Gal <ofir.gal@volumez.com>
Date: Fri Jun 7 10:27:44 2024 +0300
Subject: md/md-bitmap: fix writing non bitmap pages
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ab99a87542f194f28e2364a42afbf9fb48b1c724
needs to be reverted during your test runs, or you won't see the issue
reproduce.
You can use this ppa for updated kernels with the revert to trigger
the issue:
https://launchpad.net/~mruffell/+archive/ubuntu/sf404844-revert
This can be reproduced by running blktests md/001 [1], which the
author of the fix created to act as a regression test for this issue.
[1]
https://github.com/osandov/blktests/commit/a24a7b462816fbad7dc6c175e53fcc764ad0a822
Deploy a fresh Noble VM, that has a scratch NVME disk.
$ sudo apt install build-essential fio
$ git clone https://github.com/osandov/blktests.git
$ cd blktests
$ make
$ echo "TEST_DEVS=(/dev/nvme0n1)" > config
$ sudo ./check md/001
The md/001 test will hang an affected system, and the above oops
message will be visible in dmesg.
A test kernel is available in the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/sf404844-test
This has both the fixes for this bug, and also bug 2075110. The issue will not
reproduce.
There is also a test kernel available with the fix for this bug present, and the
fix for bug 2075110 reverted, so you can see the impact of these patches only:
https://launchpad.net/~mruffell/+archive/ubuntu/sf404844-repro
This will also not reproduce the issue anymore.
[Where problems could occur]
What we are changing is rather simple. Instead of checking the first page and
assuming all the rest in the contiguous block are sendpage_ok(), we now
check each page in the contiguous block to see if all of them are sendpage_ok().
If any aren't, then we abort the write to the driver, and try again later. This
saves us time.
However, it does take longer to call sendpage_ok() on each of the pages in the
contiguous block, so there will be a minor performance hit.
Small performance hit for correctness should be okay.
Currently we are only applying to nvme-tcp and drbd subsystems. If a regression
were to occur, it would affect users of those subsystems only.
[Other info]
Upstream mailing list:
https://lore.kernel.org/all/20240718084515.3833733-1-ofir.gal@volumez.com/T/#u
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2093871/+subscriptions
Firstly, I started with 6.11.0-21-generic with the following commit
reverted:
commit ab99a87542f194f28e2364a42afbf9fb48b1c724
Author: Ofir Gal <ofir.gal@volumez.com>
Date: Fri Jun 7 10:27:44 2024 +0300
Subject: md/md-bitmap: fix writing non bitmap pages
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ab99a87542f194f28e2364a42afbf9fb48b1c724
This is because the testcases are the same, as the above bug was fixed due to
this bug existing in the first place.
I ran the reproducer:
sudo[1244]: mruffell : TTY=pts/0 ; PWD=/home/mruffell/blktests ; USER=root ; COMMAND=./check md/001
sudo[1244]: pam_unix(sudo:session): session opened for user root(uid=0) by mruffell(uid=1008)
unknown: run blktests md/001 at 2025-04-07 04:17:58
root[1280]: run blktests md/001
brd: module loaded
(udev-worker)[1270]: dm-0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1.
Key type psk registered
nvmet: adding nsid 1 to subsystem blktests-subsystem-1
nvmet_tcp: enabling port 0 (127.0.0.1:4420)
nvmet: creating nvm controller 1 for subsystem blktests-subsystem-1 for NQN nqn.2014-08.org.nvmexpress:uuid:0f01fb42-9f7f-4856-b0b3-51e60b8de349.
nvme nvme1: creating 2 I/O queues.
nvme nvme1: mapped 2/0/0 default/read/poll queues.
nvme nvme1: new ctrl: NQN "blktests-subsystem-1", addr 127.0.0.1:4420, hostnqn: nqn.2014-08.org.nvmexpress:uuid:0f01fb42-9f7f-4856-b0b3-51e60b8de349
(udev-worker)[1270]: nvme1n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme1n1' failed with exit code 1.
(udev-worker)[1270]: md127: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/md127' failed with exit code 1.
md/raid1:md127: active with 1 out of 2 mirrors
------------[ cut here ]------------
WARNING: CPU: 0 PID: 60 at net/core/skbuff.c:7140 skb_splice_from_iter+0x1b5/0x370
Modules linked in: nvme_tcp nvmet_tcp nvmet nvme_keyring brd raid1 tls cfg80211 8021q garp mrp stp llc binfmt_misc nls_iso8859_1 intel_rapl_msr intel_rapl_common intel_uncore_frequency_common skx_edac_common nfit crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic ghash_clmulni_intel sha256_ssse3 sha1_ssse3 aesni_intel crypto_simd cryptd rapl pvpanic_mmio pvpanic psmouse i2c_piix4 i2c_smbus nvme input_leds mac_hid serio_raw sch_fq_codel nvme_fabrics nvme_core nvme_auth efi_pstore dm_multipath nfnetlink vsock_loopback vmw_vsock_virtio_transport_common vmw_vsock_vmci_transport vsock vmw_vmci dmi_sysfs virtio_rng ip_tables x_tables autofs4
CPU: 0 UID: 0 PID: 60 Comm: kworker/0:1H Not tainted 6.11.0-21-generic #20+TEST404844v20250403b1-Ubuntu
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Workqueue: nvme_tcp_wq nvme_tcp_io_work [nvme_tcp]
RIP: 0010:skb_splice_from_iter+0x1b5/0x370
Code: cc 49 89 cd f6 c2 01 0f 85 20 01 00 00 66 90 48 89 da 8b 52 30 81 e2 00 00 00 82 81 fa 00 00 00 80 0f 85 41 ff ff ff 4d 89 fe <0f> 0b 49 c7 c5 fb ff ff ff 48 8b 85 68 ff ff ff 41 01 46 70 41 01
RSP: 0018:ffffac5c0020ba18 EFLAGS: 00010246
RAX: 0000000000000000 RBX: fffff04bc4c1edc0 RCX: 0000000000001000
RDX: 0000000080000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffac5c0020bac0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000004000
R13: 0000000000001000 R14: ffffa094c37d6c00 R15: ffffa094c37d6c00
FS: 0000000000000000(0000) GS:ffffa095f7c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007e272064c6c0 CR3: 0000000104e8c005 CR4: 00000000003706f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
? show_trace_log_lvl+0x1be/0x310
? show_trace_log_lvl+0x1be/0x310
? tcp_sendmsg_locked+0x36e/0xe40
? show_regs.part.0+0x22/0x30
? show_regs.cold+0x8/0x10
? skb_splice_from_iter+0x1b5/0x370
? __warn.cold+0xa7/0x101
? skb_splice_from_iter+0x1b5/0x370
? report_bug+0x114/0x160
? handle_bug+0x51/0xa0
? exc_invalid_op+0x18/0x80
? asm_exc_invalid_op+0x1b/0x20
? skb_splice_from_iter+0x1b5/0x370
? skb_splice_from_iter+0x12a/0x370
tcp_sendmsg_locked+0x36e/0xe40
? tcp_push+0x12d/0x170
? tcp_sendmsg_locked+0xac7/0xe40
? tcp_cleanup_rbuf+0x42/0x90
tcp_sendmsg+0x2c/0x50
inet_sendmsg+0x42/0x80
sock_sendmsg+0x118/0x140
nvme_tcp_try_send_data+0x181/0x4c0 [nvme_tcp]
nvme_tcp_try_send+0x1a6/0x230 [nvme_tcp]
nvme_tcp_io_work+0x6c/0x110 [nvme_tcp]
process_one_work+0x174/0x350
worker_thread+0x32a/0x460
? _raw_spin_unlock_irqrestore+0x11/0x60
? __pfx_worker_thread+0x10/0x10
kthread+0xe1/0x110
? __pfx_kthread+0x10/0x10
ret_from_fork+0x44/0x70
? __pfx_kthread+0x10/0x10
ret_from_fork_asm+0x1a/0x30
</TASK>
---[ end trace 0000000000000000 ]---
Okay, we can reproduce the issue.
I then enabled -proposed, and installed 6.11.0-24-generic, note, which
contains:
commit ab99a87542f194f28e2364a42afbf9fb48b1c724
Author: Ofir Gal <ofir.gal@volumez.com>
Date: Fri Jun 7 10:27:44 2024 +0300
Subject: md/md-bitmap: fix writing non bitmap pages
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ab99a87542f194f28e2364a42afbf9fb48b1c724
AND the three fixed we are testing:
commit 23a55f4492fcf868d068da31a2cd30c15f46207d
Author: Ofir Gal <ofir.gal@volumez.com>
Date: Thu Jul 18 11:45:12 2024 +0300
Subject: net: introduce helper sendpages_ok()
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=23a55f4492fcf868d068da31a2cd30c15f46207d
commit 6af7331a70b4888df43ec1d7e1803ae2c43b6981
Author: Ofir Gal <ofir.gal@volumez.com>
Date: Thu Jul 18 11:45:13 2024 +0300
Subject: nvme-tcp: use sendpages_ok() instead of sendpage_ok()
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6af7331a70b4888df43ec1d7e1803ae2c43b6981
commit 7960af373ade3b39e10106ef415e43a1d2aa48c6
Author: Ofir Gal <ofir.gal@volumez.com>
Date: Thu Jul 18 11:45:14 2024 +0300
Subject: drbd: use sendpages_ok() instead of sendpage_ok()
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7960af373ade3b39e10106ef415e43a1d2aa48c6
I rebooted and ran the reproducer:
$ uname -rv
6.11.0-24-generic #24-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 14 18:13:56 UTC 2025
$ sudo ./check md/001
md/001 (Raid with bitmap on tcp nvmet with opt-io-size over bitmap size) [passed]
runtime ... 0.451
Just to make sure that the three commits really did fix the issue, I then
built and booted into 6.11.0-24-generic, again with
commit ab99a87542f194f28e2364a42afbf9fb48b1c724
Author: Ofir Gal <ofir.gal@volumez.com>
Date: Fri Jun 7 10:27:44 2024 +0300
Subject: md/md-bitmap: fix writing non bitmap pages
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ab99a87542f194f28e2364a42afbf9fb48b1c724
reverted, so we just test the new fixes only.
$ uname -rv
6.11.0-24-generic #24+TEST404844v20250328b1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 28
$ sudo ./check md/001
md/001 (Raid with bitmap on tcp nvmet with opt-io-size over bitmap size) [passed]
runtime 0.451s ... 0.449s
We continue to pass with the new patches only.
The kernel in -proposed fixes the issue, happy to mark verified for
oracular.
** Tags removed: verification-needed-oracular-linux
** Tags added: verification-done-oracular-linux
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2093871
Title:
Introduce and use sendpages_ok() instead of sendpage_ok() in nvme-tcp
and drbd
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Fix Committed
Status in linux source package in Oracular:
Fix Committed
Bug description:
BugLink: https://bugs.launchpad.net/bugs/2093871
[Impact]
Currently the nvme-tcp and drbd subsystems try to enable the MSG_SPLICE_PAGES
flag on pages to be written, and when MSG_SPLICE_PAGES is set, eventually it
calls skb_splice_from_iter(), which then checks all pages with sendpage_ok()
to see if all the pages are sendable.
At the moment, both subsystems only check the first page in a potentially
contiguous block of pages, if they are sendpage_ok(), and if the first page is,
then it just assumes all the rest are sendpage_ok() too, and sends the I/O off
to eventually be found out by skb_splice_from_iter(). If one or more of the
pages in the contiguous block is not sendpage_ok(), then we get a warn printed,
data transfer is aborted. In the nvme-tcp case, IO then hangs.
This patchset introduces sendpages_ok() which iterates over each page in a
contiguous block, checks if it is sendpage_ok(), and only returns true if all
of them are.
This resolves the whole MSG_SPLICE_PAGES flag situation, since you can now
depend on the result of sendpages_ok(), instead of just assuming everything is
okay.
This issue is what caused bug 2075110 [0] to be discovered in the first place,
since it was responsible for contigious blocks of pages where the first was
sendpage_ok(), but pages further into the block were not.
[0] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2075110
Even with "md/md-bitmap: fix writing non bitmap pages" applied, the issue can
still happen, e.g. with merged IO pages, so this fix is still needed to
eliminate the issue.
[Fix]
The fixes landed in mainline 6.12-rc1:
commit 23a55f4492fcf868d068da31a2cd30c15f46207d
Author: Ofir Gal <ofir.gal@volumez.com>
Date: Thu Jul 18 11:45:12 2024 +0300
Subject: net: introduce helper sendpages_ok()
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=23a55f4492fcf868d068da31a2cd30c15f46207d
commit 6af7331a70b4888df43ec1d7e1803ae2c43b6981
Author: Ofir Gal <ofir.gal@volumez.com>
Date: Thu Jul 18 11:45:13 2024 +0300
Subject: nvme-tcp: use sendpages_ok() instead of sendpage_ok()
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6af7331a70b4888df43ec1d7e1803ae2c43b6981
commit 7960af373ade3b39e10106ef415e43a1d2aa48c6
Author: Ofir Gal <ofir.gal@volumez.com>
Date: Thu Jul 18 11:45:14 2024 +0300
Subject: drbd: use sendpages_ok() instead of sendpage_ok()
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7960af373ade3b39e10106ef415e43a1d2aa48c6
They are needed for noble and oracular.
[Testcase]
This is the same testcase as the original bug 2075110 [0], as the fix is
designed to prevent it or similar other bugs from happening again.
[0] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2075110
Because of this, the fix:
commit ab99a87542f194f28e2364a42afbf9fb48b1c724
Author: Ofir Gal <ofir.gal@volumez.com>
Date: Fri Jun 7 10:27:44 2024 +0300
Subject: md/md-bitmap: fix writing non bitmap pages
Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ab99a87542f194f28e2364a42afbf9fb48b1c724
needs to be reverted during your test runs, or you won't see the issue
reproduce.
You can use this ppa for updated kernels with the revert to trigger
the issue:
https://launchpad.net/~mruffell/+archive/ubuntu/sf404844-revert
This can be reproduced by running blktests md/001 [1], which the
author of the fix created to act as a regression test for this issue.
[1]
https://github.com/osandov/blktests/commit/a24a7b462816fbad7dc6c175e53fcc764ad0a822
Deploy a fresh Noble VM, that has a scratch NVME disk.
$ sudo apt install build-essential fio
$ git clone https://github.com/osandov/blktests.git
$ cd blktests
$ make
$ echo "TEST_DEVS=(/dev/nvme0n1)" > config
$ sudo ./check md/001
The md/001 test will hang an affected system, and the above oops
message will be visible in dmesg.
A test kernel is available in the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/sf404844-test
This has both the fixes for this bug, and also bug 2075110. The issue will not
reproduce.
There is also a test kernel available with the fix for this bug present, and the
fix for bug 2075110 reverted, so you can see the impact of these patches only:
https://launchpad.net/~mruffell/+archive/ubuntu/sf404844-repro
This will also not reproduce the issue anymore.
[Where problems could occur]
What we are changing is rather simple. Instead of checking the first page and
assuming all the rest in the contiguous block are sendpage_ok(), we now
check each page in the contiguous block to see if all of them are sendpage_ok().
If any aren't, then we abort the write to the driver, and try again later. This
saves us time.
However, it does take longer to call sendpage_ok() on each of the pages in the
contiguous block, so there will be a minor performance hit.
Small performance hit for correctness should be okay.
Currently we are only applying to nvme-tcp and drbd subsystems. If a regression
were to occur, it would affect users of those subsystems only.
[Other info]
Upstream mailing list:
https://lore.kernel.org/all/20240718084515.3833733-1-ofir.gal@volumez.com/T/#u
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2093871/+subscriptions
Подписаться на:
Сообщения (Atom)