From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-ed1-f45.google.com (mail-ed1-f45.google.com [209.85.208.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9AC271B85F8 for ; Fri, 20 Dec 2024 19:49:59 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.208.45 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1734724201; cv=none; b=Wkpn6RmfJWeXcdS7oyaxnAX2DkGfxy2P0cjMUbjkAflxINb9Cyiyv/wUM1TrvlGRh+FEkzZLulb+IxaP3lD08Eg07tfZFY5T6CySK6JIZpIGzrkDdgNcnsLtpbbKnt5AsU/hn90L1e+25TzYP62lfdk9oAYJBmH+R8JwwhV73ck= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1734724201; c=relaxed/simple; bh=EpsJakmyH9YSpaer6E1J1FTY7JPT3aDCwC4b8DqvOJg=; h=Date:From:To:Cc:Subject:Message-ID:MIME-Version:Content-Type: Content-Disposition; b=Zz+RFTPRMY9UcaImlYd+LU8ZkUHOybO1XQEuIuL70sJzRdlPV3IU6hcS2MymiABFrF9cUp7BRK/1MYbJ4EJtLorlMipmKpdkWvu4Zo9C9K4Ah4qB2Rnh4RjfofMms5miBs1zRet+ECDSbwhnlBRYIstq8e6aF2nvifKbl/aO7zE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=debian.org; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=nMajRwFs; arc=none smtp.client-ip=209.85.208.45 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=debian.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="nMajRwFs" Received: by mail-ed1-f45.google.com with SMTP id 4fb4d7f45d1cf-5d7e3f1fdafso4406266a12.0 for ; Fri, 20 Dec 2024 11:49:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1734724198; x=1735328998; darn=vger.kernel.org; h=content-disposition:mime-version:message-id:subject:cc:to:from:date :sender:from:to:cc:subject:date:message-id:reply-to; bh=CC7HPO/I2vxnnbATSGWhXRaNRcFje7+bdn9wnsTcce4=; b=nMajRwFsPJqCCSvsdYF3HuqvF88wp8ahSbJjbYqFcgDRGL0X7R4ddRecfUGMSdy4gm jTyA8LleqnGwRM6l9aElxDc8fdjocJOGsaLtHnS7SeUsL+IXuiibUqosQRCVm0m5PjdI tgUZAxsLg3U1P+D7SGIfDFNZ5Ushj5LDfr9/OEHB7t9KMsBQss5GP7kJS608FJPi4bY4 7lXFhSqXDgyo35NSt7INXAZxfIE0F0MEpN6Se3YYHXTEfwhOeQRIZzFh1PWhQ1h84+zv LYcmL74xl86+asF9b7V4cTsi+8v/kgPd1e/WNSTVV7XwFe0V3SwGmrSAWGvNgoD4lik5 x9Og== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734724198; x=1735328998; h=content-disposition:mime-version:message-id:subject:cc:to:from:date :sender:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=CC7HPO/I2vxnnbATSGWhXRaNRcFje7+bdn9wnsTcce4=; b=SYxF4MI2h0TkDHXtpp03QBZQwDxcVOHIpLQlcA789pEdpqCHmbXFx1rzEw7i012VR8 H2Tq1nd0+68d8fPHxLLecrSbIotuyssg8dZrCifzhJ8pUJcpqBZ1NWmNETXWJnjjDEMJ ARLDBYL/3T863SzwoT5PzO7/xMGbi+WJVEZ+2nA7kXvX+OT2W4mjChp+r+Ni1Nd2szWc suXhNlLKY43N9ZWYPpLRJFSotflwRRGrSZyeRe1cN48Q97AguB1LgGd3xPVbhWjzXlIB 0WMkXrwRjGzFK4VOnb15uKG5uU4MYrLHSDWaFglX1HgGsuPA8zRxMWAoE9WHimpFh2Jc c97w== X-Forwarded-Encrypted: i=1; AJvYcCXcvnr+nZJ9sYmYtsxljbfLbjU9gJyK85LEtEP2SdGoAdFCWsAW4hDenFjEdAwvJTodOU7xoidOifpBGa4=@vger.kernel.org X-Gm-Message-State: AOJu0Yzw3hq568Ux82VDB4kx+wE1WuKJkmExR/J4jZP1A5D8GMrwF61K KmYG1S5wZDXI+MziNC0gTZ3SRtaz24s/HGqncmxkDhM5fyw77hhZfWkuCqQa X-Gm-Gg: ASbGncvmL207q36MOteUVzkmyWBh/lERPyWCCMokCS6fn6kM5rw/LK+I2xLwXaKigeG TLBDyZuNSrJM86Xtb+1cij+NFzCtetaa2dIjoLeQAI8QlAEPgXW3anmBfVHbC1wd+FInCJOwybY yokszn9RtaF1LMcwXhoN8pDt91bhQyQ+iQDQ/f4+pzQorI2akM/05Y4GGHoluxmTru7f50Fbl5Q ls6qBm9VOt6o7HW9pg/aqf7Poa5nnb9QpMnwUQrJsX3NZZjQS2QPc32FXSKihd5l8JBqrVzZPrw sdAnEzfjt96cELvJ X-Google-Smtp-Source: AGHT+IFdVrNmfcy1kGOF3NSBclOemYsDkCUQHayb8FORkO0KPdukKE0qeYugOEgfwCT7kyptMaY5kw== X-Received: by 2002:a05:6402:1e90:b0:5d3:ff30:b4cc with SMTP id 4fb4d7f45d1cf-5d81de39866mr3841332a12.33.1734724197570; Fri, 20 Dec 2024 11:49:57 -0800 (PST) Received: from eldamar.lan (c-82-192-242-114.customer.ggaweb.ch. [82.192.242.114]) by smtp.gmail.com with ESMTPSA id 4fb4d7f45d1cf-5d80678c5a4sm2008707a12.38.2024.12.20.11.49.56 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 20 Dec 2024 11:49:56 -0800 (PST) Sender: Salvatore Bonaccorso Received: by eldamar.lan (Postfix, from userid 1000) id 8C044BE2EE7; Fri, 20 Dec 2024 20:49:55 +0100 (CET) Date: Fri, 20 Dec 2024 20:49:55 +0100 From: Salvatore Bonaccorso To: regressions@lists.linux.dev, Zhao Mengmeng , Jan Kara Cc: Daniel Reichelt , linux-kernel@vger.kernel.org Subject: [regression] linux: Loop-mounted UDF ISOs no longer readable Message-ID: Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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: > 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? #regzbot introduced: v6.1.112..v6.1.115 #regzbot monitor: https://bugs.debian.org/1089698 Regards, Salvatore