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
