From: Zhao Mengmeng <zhaomengmeng@kylinos.cn>
To: Salvatore Bonaccorso <carnil@debian.org>,
regressions@lists.linux.dev, Jan Kara <jack@suse.cz>
Cc: Daniel Reichelt <debian@nachtgeist.net>, linux-kernel@vger.kernel.org
Subject: Re: [regression] linux: Loop-mounted UDF ISOs no longer readable
Date: Mon, 23 Dec 2024 10:48:52 +0800 [thread overview]
Message-ID: <b681e1ea-bb7d-4d8f-b62c-cae1e4116d21@kylinos.cn> (raw)
In-Reply-To: <Z2XKY0f6on1UbwWb@eldamar.lan>
On 2024/12/21 03:49, Salvatore Bonaccorso wrote:
> Hi Jan, hi Zhao,
>
> In Debian we got he following report, full quoted below from Daniel
> Reichelt, dass after updating to 6.1.115 (and later, confirmed up to
> 6.1.119), loop-mounted UDF ISOs are no longer readable:
Sorry to hear that...
>> 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.
>
> We have not a full bisect, but Daniel confirmed already in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089698#22 some
> observations:
>
>> 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
>
> (current trixie is 6.11.10 based kernel, current sid is based on
> 6.12.5 kernel).
>
> Dies this ring some bell to you?
I'll take a look at it. Will post it here if anything new founded.
> #regzbot introduced: v6.1.112..v6.1.115
> #regzbot monitor: https://bugs.debian.org/1089698
>
> Regards,
> Salvatore
next prev parent reply other threads:[~2024-12-23 2:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 19:49 Salvatore Bonaccorso
2024-12-23 2:48 ` Zhao Mengmeng [this message]
2024-12-24 9:46 ` Zhao Mengmeng
2024-12-24 9:59 ` Greg KH
2024-12-25 1:06 ` Zhao Mengmeng
2024-12-24 14:21 ` Daniel Reichelt
2024-12-24 21:21 ` Daniel Reichelt
2024-12-25 1:07 ` Zhao Mengmeng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b681e1ea-bb7d-4d8f-b62c-cae1e4116d21@kylinos.cn \
--to=zhaomengmeng@kylinos.cn \
--cc=carnil@debian.org \
--cc=debian@nachtgeist.net \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®