Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #84797 > unrolled thread

Bug#1089698: linux: Loop-mounted UDF ISOs no longer readable

Started byDaniel Reichelt <debian@nachtgeist.net>
First post2024-12-11 15:10 +0100
Last post2024-12-20 21:10 +0100
Articles 9 — 4 participants

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1089698: linux: Loop-mounted UDF ISOs no longer readable Daniel Reichelt <debian@nachtgeist.net> - 2024-12-11 15:10 +0100
    Bug#1089698: linux: Loop-mounted UDF ISOs no longer readable Salvatore Bonaccorso <carnil@debian.org> - 2024-12-15 15:10 +0100
      Bug#1089698: linux: Loop-mounted UDF ISOs no longer readable Daniel Reichelt <debian@nachtgeist.net> - 2024-12-15 16:00 +0100
      Bug#1089698: linux: Loop-mounted UDF ISOs no longer readable Daniel Reichelt <debian@nachtgeist.net> - 2024-12-20 02:00 +0100
        Bug#1089698: linux: Loop-mounted UDF ISOs no longer readable Salvatore Bonaccorso <carnil@debian.org> - 2024-12-20 21:10 +0100
          Bug#1089698: linux: Loop-mounted UDF ISOs no longer readable Daniel Reichelt <debian@nachtgeist.net> - 2024-12-23 04:20 +0100
            Bug#1089698: linux: Loop-mounted UDF ISOs no longer readable Zhao Mengmeng <zhaomengmeng@kylinos.cn> - 2024-12-23 10:10 +0100
    Processed: Re: Bug#1089698: linux: Loop-mounted UDF ISOs no  longer readable "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-12-15 15:10 +0100
    Processed: Re: Bug#1089698: linux: Loop-mounted UDF ISOs no  longer readable "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-12-20 21:10 +0100

#84797 — Bug#1089698: linux: Loop-mounted UDF ISOs no longer readable

FromDaniel Reichelt <debian@nachtgeist.net>
Date2024-12-11 15:10 +0100
SubjectBug#1089698: linux: Loop-mounted UDF ISOs no longer readable
Message-ID<JSvzz-g82W-7@gated-at.bofh.it>
Source: linux
Version: 6.1.115-1
Severity: normal
Tags: upstream

Hi,

in 6.1.112-1 I could loop-mount Windows Setup ISOs (downloaded from M$; hashes
are fine; 10/11, DE/EN don't seem to make any difference) and access their
content perfectly fine, i.e. share the /sources/ sub-directory via samba for
netinstall scenarios.

Starting with 6.1.115-1, the ISOs can be mounted, the root-dir is accessible
and `stat $mntpt/sources` gives output as well. However `ls $mntpt/sources`
hangs and the kernel log is spammed with entries like

---------------8<-------------------------
2024-12-11T14:53:19.616728+01:00 srv kernel: [182394.024828] UDF-fs: error (device loop3): udf_fiiter_advance_blk: extent after position 12272 not allocated in directory (ino 312)
2024-12-11T14:53:19.629970+01:00 srv kernel: [182394.038041] UDF-fs: error (device loop3): udf_verify_fi: directory (ino 312) has too big (2088) entry at pos 12272
2024-12-11T14:53:19.641623+01:00 srv kernel: [182394.049714] UDF-fs: error (device loop3): udf_fiiter_advance_blk: extent after position 12272 not allocated in directory (ino 312)
2024-12-11T14:53:19.654841+01:00 srv kernel: [182394.062928] UDF-fs: error (device loop3): udf_verify_fi: directory (ino 312) has too big (2088) entry at pos 12272
2024-12-11T14:53:19.666495+01:00 srv kernel: [182394.074615] UDF-fs: error (device loop3): udf_fiiter_advance_blk: extent after position 12272 not allocated in directory (ino 312)
2024-12-11T14:53:19.679747+01:00 srv kernel: [182394.087833] UDF-fs: error (device loop3): udf_verify_fi: directory (ino 312) has too big (2088) entry at pos 12272
2024-12-11T14:53:19.691394+01:00 srv kernel: [182394.099510] UDF-fs: error (device loop3): udf_fiiter_advance_blk: extent after position 12272 not allocated in directory (ino 312)
2024-12-11T14:53:19.704646+01:00 srv kernel: [182394.112727] UDF-fs: error (device loop3): udf_verify_fi: directory (ino 312) has too big (2088) entry at pos 12272
2024-12-11T14:53:19.716283+01:00 srv kernel: [182394.124400] UDF-fs: error (device loop3): udf_fiiter_advance_blk: extent after position 12272 not allocated in directory (ino 312)
2024-12-11T14:53:19.729539+01:00 srv kernel: [182394.137618] UDF-fs: error (device loop3): udf_verify_fi: directory (ino 312) has too big (2088) entry at pos 12272
2024-12-11T14:53:19.741185+01:00 srv kernel: [182394.149279] UDF-fs: error (device loop3): udf_fiiter_advance_blk: extent after position 12272 not allocated in directory (ino 312)
2024-12-11T14:53:19.754422+01:00 srv kernel: [182394.162494] UDF-fs: error (device loop3): udf_verify_fi: directory (ino 312) has too big (2088) entry at pos 12272
2024-12-11T14:53:19.766071+01:00 srv kernel: [182394.174159] UDF-fs: error (device loop3): udf_fiiter_advance_blk: extent after position 12272 not allocated in directory (ino 312)
2024-12-11T14:53:19.779289+01:00 srv kernel: [182394.187375] UDF-fs: error (device loop3): udf_verify_fi: directory (ino 312) has too big (2088) entry at pos 12272
---------------8<-------------------------


6.1.119-1 shows the same behaviour.
Let me know if you need additional info.

Thanks!
Daniel


-- System Information:
Debian Release: 12.8
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-28-amd64 (SMP w/16 CPU threads; PREEMPT)

[toc] | [next] | [standalone]

#84826

FromSalvatore Bonaccorso <carnil@debian.org>
Date2024-12-15 15:10 +0100
Message-ID<JTXtL-hdwm-1@gated-at.bofh.it>
In reply to#84797
Control: tags -1 + moreinfo

Hi Daniel,

On Wed, Dec 11, 2024 at 02:58:48PM +0100, Daniel Reichelt wrote:
> Source: linux
> Version: 6.1.115-1
> Severity: normal
> Tags: upstream
> 
> Hi,
> 
> in 6.1.112-1 I could loop-mount Windows Setup ISOs (downloaded from M$; hashes
> are fine; 10/11, DE/EN don't seem to make any difference) and access their
> content perfectly fine, i.e. share the /sources/ sub-directory via samba for
> netinstall scenarios.
> 
> Starting with 6.1.115-1, the ISOs can be mounted, the root-dir is accessible
> and `stat $mntpt/sources` gives output as well. However `ls $mntpt/sources`
> hangs and the kernel log is spammed with entries like
> 
> ---------------8<-------------------------
> 2024-12-11T14:53:19.616728+01:00 srv kernel: [182394.024828] UDF-fs: error (device loop3): udf_fiiter_advance_blk: extent after position 12272 not allocated in directory (ino 312)
> 2024-12-11T14:53:19.629970+01:00 srv kernel: [182394.038041] UDF-fs: error (device loop3): udf_verify_fi: directory (ino 312) has too big (2088) entry at pos 12272
> 2024-12-11T14:53:19.641623+01:00 srv kernel: [182394.049714] UDF-fs: error (device loop3): udf_fiiter_advance_blk: extent after position 12272 not allocated in directory (ino 312)
> 2024-12-11T14:53:19.654841+01:00 srv kernel: [182394.062928] UDF-fs: error (device loop3): udf_verify_fi: directory (ino 312) has too big (2088) entry at pos 12272
> 2024-12-11T14:53:19.666495+01:00 srv kernel: [182394.074615] UDF-fs: error (device loop3): udf_fiiter_advance_blk: extent after position 12272 not allocated in directory (ino 312)
> 2024-12-11T14:53:19.679747+01:00 srv kernel: [182394.087833] UDF-fs: error (device loop3): udf_verify_fi: directory (ino 312) has too big (2088) entry at pos 12272
> 2024-12-11T14:53:19.691394+01:00 srv kernel: [182394.099510] UDF-fs: error (device loop3): udf_fiiter_advance_blk: extent after position 12272 not allocated in directory (ino 312)
> 2024-12-11T14:53:19.704646+01:00 srv kernel: [182394.112727] UDF-fs: error (device loop3): udf_verify_fi: directory (ino 312) has too big (2088) entry at pos 12272
> 2024-12-11T14:53:19.716283+01:00 srv kernel: [182394.124400] UDF-fs: error (device loop3): udf_fiiter_advance_blk: extent after position 12272 not allocated in directory (ino 312)
> 2024-12-11T14:53:19.729539+01:00 srv kernel: [182394.137618] UDF-fs: error (device loop3): udf_verify_fi: directory (ino 312) has too big (2088) entry at pos 12272
> 2024-12-11T14:53:19.741185+01:00 srv kernel: [182394.149279] UDF-fs: error (device loop3): udf_fiiter_advance_blk: extent after position 12272 not allocated in directory (ino 312)
> 2024-12-11T14:53:19.754422+01:00 srv kernel: [182394.162494] UDF-fs: error (device loop3): udf_verify_fi: directory (ino 312) has too big (2088) entry at pos 12272
> 2024-12-11T14:53:19.766071+01:00 srv kernel: [182394.174159] UDF-fs: error (device loop3): udf_fiiter_advance_blk: extent after position 12272 not allocated in directory (ino 312)
> 2024-12-11T14:53:19.779289+01:00 srv kernel: [182394.187375] UDF-fs: error (device loop3): udf_verify_fi: directory (ino 312) has too big (2088) entry at pos 12272
> ---------------8<-------------------------

There were in fact major refactoring of the udf code starting in
6.1.114 upstream.

Two questions:

Can you check with current upstream kernels, ideally 6.13-rc2 or the
versions available in Debian 6.12.5-1 (freshly uploaded, so has to
pass NEW) or 6.12.3-1 to verify the bahaviour is not present there?

If this is the case there might be some requirements in the backports
which got missing.

Samewise, if you have the resources, can you bisect upstream versions
between 6.1.112 and 6.1.115 specifically to identify which commit
causes the regression?

Knowing though if the issue is present as well in mainline or most
recent stable series upstream would be good to get some more
datapoint.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#84831

FromDaniel Reichelt <debian@nachtgeist.net>
Date2024-12-15 16:00 +0100
Message-ID<JTYg9-hdPW-5@gated-at.bofh.it>
In reply to#84826
 > Two questions:
 >
 > Can you check with current upstream kernels, ideally 6.13-rc2 or the
 > versions available in Debian 6.12.5-1 (freshly uploaded, so has to
 > pass NEW) or 6.12.3-1 to verify the bahaviour is not present there?
 >
 > If this is the case there might be some requirements in the backports
 > which got missing.
 >
 > Samewise, if you have the resources, can you bisect upstream versions
 > between 6.1.112 and 6.1.115 specifically to identify which commit
 > causes the regression?
 >
 > Knowing though if the issue is present as well in mainline or most
 > recent stable series upstream would be good to get some more
 > datapoint.


Will do, thanks for the pointers.

[toc] | [prev] | [next] | [standalone]

#84884

FromDaniel Reichelt <debian@nachtgeist.net>
Date2024-12-20 02:00 +0100
Message-ID<JVzwZ-ZAE-1@gated-at.bofh.it>
In reply to#84826
Hi Salvatore,


> Can you check with current upstream kernels[…]

prior to getting into bisecting, I decided to give [1] a shot.
 From testing kernels available there I got this:

OK:
   6.1.112-1
BAD:
   6.1.115-1
   6.1.119-1
OK again:
   6.3.1-1~exp1
   current trixie
   current sid

It may take some time until I get around to bisecting linux.git in the
range 6.1.119..6.3.1 - what with real life and all.


> Samewise, if you have the resources, can you bisect upstream 
> versions between 6.1.112 and 6.1.115 specifically to identify which 
> commit causes the regression?

That one was pretty easy to identify - the one which changes everything 
around in $ksrc/fs/udf (didn't write it up, though). However, I think 
the range I mentioned above is more interesting anyways, in terms of 
getting a viable patch together to fix this in bookworm.

Cheers
Daniel


[1] https://snapshot.debian.org/package/linux/

[toc] | [prev] | [next] | [standalone]

#84887

FromSalvatore Bonaccorso <carnil@debian.org>
Date2024-12-20 21:10 +0100
Message-ID<JVRtT-1aYW-1@gated-at.bofh.it>
In reply to#84884
Control: forwarded -1 https://lore.kernel.org/regressions/Z2XKY0f6on1UbwWb@eldamar.lan/T/#u

Hi Daniel,

On Fri, Dec 20, 2024 at 01:50:49AM +0100, Daniel Reichelt wrote:
> Hi Salvatore,
> 
> 
> > Can you check with current upstream kernels[…]
> 
> prior to getting into bisecting, I decided to give [1] a shot.
> From testing kernels available there I got this:
> 
> OK:
>   6.1.112-1
> BAD:
>   6.1.115-1
>   6.1.119-1
> OK again:
>   6.3.1-1~exp1
>   current trixie
>   current sid
> 
> It may take some time until I get around to bisecting linux.git in the
> range 6.1.119..6.3.1 - what with real life and all.
> 
> 
> > Samewise, if you have the resources, can you bisect upstream versions
> > between 6.1.112 and 6.1.115 specifically to identify which commit causes
> > the regression?
> 
> That one was pretty easy to identify - the one which changes everything
> around in $ksrc/fs/udf (didn't write it up, though). However, I think the
> range I mentioned above is more interesting anyways, in terms of getting a
> viable patch together to fix this in bookworm.

Thanks a lot, please keep us posted with your findings.

Additionally I have now reported the issue on the regressions list as
well:

https://lore.kernel.org/regressions/Z2XKY0f6on1UbwWb@eldamar.lan/T/#u

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#84924

FromDaniel Reichelt <debian@nachtgeist.net>
Date2024-12-23 04:20 +0100
Message-ID<JWH97-1IbB-1@gated-at.bofh.it>
In reply to#84887
On 20.12.24 20:55, Salvatore Bonaccorso wrote:
> Additionally I have now reported the issue on the regressions list as
> well:
> 
> https://lore.kernel.org/regressions/Z2XKY0f6on1UbwWb@eldamar.lan/T/#u

Splendid, thanks!


Quick update: 6.2 is also OK, so we have:

OK still:
   6.1.112-1
UNKNOWN - not in [1], yet to be bisected/compiled
   6.1.113
   6.1.114
BAD:
   6.1.115-1
   6.1.119-1
   6.1.120 not part of [1], but out-of-tree build was bad
OK again:
   6.2 (upstream vanilla)
   6.3.1-1~exp1
   6.11.10 (current Debian testing/Trixie)
   6.12.5  (current Debian unstable/sid)


[1] https://snapshot.debian.org/package/linux/


Thanks to y'all!
Daniel

[toc] | [prev] | [next] | [standalone]

#84925

FromZhao Mengmeng <zhaomengmeng@kylinos.cn>
Date2024-12-23 10:10 +0100
Message-ID<JWMBP-1LBC-5@gated-at.bofh.it>
In reply to#84924
On 2024/12/23 11:10, Daniel Reichelt wrote:
> On 20.12.24 20:55, Salvatore Bonaccorso wrote:
>> Additionally I have now reported the issue on the regressions list as
>> well:
>>
>> https://lore.kernel.org/regressions/Z2XKY0f6on1UbwWb@eldamar.lan/T/#u
> 
> Splendid, thanks!
> 
> 
> Quick update: 6.2 is also OK, so we have:
> 
> OK still:
>   6.1.112-1
> UNKNOWN - not in [1], yet to be bisected/compiled
>   6.1.113
>   6.1.114
> BAD:
>   6.1.115-1
>   6.1.119-1
>   6.1.120 not part of [1], but out-of-tree build was bad
> OK again:
>   6.2 (upstream vanilla)
>   6.3.1-1~exp1
>   6.11.10 (current Debian testing/Trixie)
>   6.12.5  (current Debian unstable/sid)
> 
> 
> [1] https://snapshot.debian.org/package/linux/

Hi Jan, I have tested v6.1 upstream kernel with x86_64_defconfig, it turns out:

v6.1.112 is good as Daniel reported,
v6.1.114 is bad, but the log is little different.
                                              
[   21.307158] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 12280 not allocated in directory (ino 312)                                                           
[   21.307832] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 312) has entry where CRC length (2) does not match entry length (24)                                                 
[   21.308738] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 12280 not allocated in directory (ino 312)                                                           
[   21.309785] UDF-fs: error (device sr0): udf_verify_fi: directory (ino 312) has entry where CRC length (2) does not match entry length (24)                                                 
[   21.310996] UDF-fs: error (device sr0): udf_fiiter_advance_blk: extent after position 12280 not allocated in directory (ino 312)          

I also manually revert my patch "udf: refactor udf_current_aext() to handle error" based on v6.1.115, and
it's still broken, looks like something wrong in v6.1.114. Can you have a look? 

Besides, I noticed that v6.1 LTS backports only 1 of 3 of the refactor patches wich I submitted, that may be a problem.


> 
> Thanks to y'all!
> Daniel

[toc] | [prev] | [next] | [standalone]

#84827 — Processed: Re: Bug#1089698: linux: Loop-mounted UDF ISOs no longer readable

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2024-12-15 15:10 +0100
SubjectProcessed: Re: Bug#1089698: linux: Loop-mounted UDF ISOs no longer readable
Message-ID<JTXtL-hdwm-9@gated-at.bofh.it>
In reply to#84797
Processing control commands:

> tags -1 + moreinfo
Bug #1089698 [src:linux] linux: Loop-mounted UDF ISOs no longer readable
Added tag(s) moreinfo.

-- 
1089698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089698
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#84888 — Processed: Re: Bug#1089698: linux: Loop-mounted UDF ISOs no longer readable

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2024-12-20 21:10 +0100
SubjectProcessed: Re: Bug#1089698: linux: Loop-mounted UDF ISOs no longer readable
Message-ID<JVRtT-1aYW-3@gated-at.bofh.it>
In reply to#84797
Processing control commands:

> forwarded -1 https://lore.kernel.org/regressions/Z2XKY0f6on1UbwWb@eldamar.lan/T/#u
Bug #1089698 [src:linux] linux: Loop-mounted UDF ISOs no longer readable
Set Bug forwarded-to-address to 'https://lore.kernel.org/regressions/Z2XKY0f6on1UbwWb@eldamar.lan/T/#u'.

-- 
1089698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089698
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web