[From nobody Sun Jun 28 15:41:06 2026
Received: (at 1120998-done) by bugs.debian.org; 28 Jun 2026 14:38:42 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-9.0 required=4.0 tests=BAYES_00,DKIM_SIGNED,
 DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FOURLA,HAS_BUG_NUMBER,
 MD5_SHA1_SUM,RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS,VERSION
 autolearn=ham autolearn_force=no
 version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 39; hammy, 102; neutral, 19; spammy,
 1. spammytokens:0.941-+--H*r:bugs.debian.org
 hammytokens:0.000-+--reproducibly, 0.000-+--H*F:U*sebastian,
 0.000-+--H*F:D*breakpoint.cc, 0.000-+--H*RU:sk:chamill,
 0.000-+--H*r:sk:chamill
Return-path: <sebastian@breakpoint.cc>
Received: from chamillionaire.breakpoint.cc ([91.216.245.30]:51444)
 by buxtehude.debian.org with esmtps
 (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from <sebastian@breakpoint.cc>)
 id 1wdqeg-00GKiG-28 for 1120998-done@bugs.debian.org;
 Sun, 28 Jun 2026 14:38:42 +0000
Date: Sun, 28 Jun 2026 16:38:38 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=breakpoint.cc;
 s=2025; t=1782657520;
 h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
 to:to:cc:mime-version:mime-version:content-type:content-type:
 in-reply-to:in-reply-to:references:references;
 bh=rw0bmVMHOC+6OaVG8wYazlkF84tgCXNSshJsh+I9ctk=;
 b=iE6X5GNeLuvVw7bOQ9Xf0Jn+Ljpn9hzDvFNuOIgvgmE4DrCghsmUkb3Cp7XkA7tLOVvOeq
 awGeBt0gxAXrv/o4DEeS+hL0FO36X2LRyaX5sHD1mSTH/KMvy+/RBHFz+Sds9bNSQI5XKg
 eaq/XWregs9Wy6SVBmqcBrsjtfvEbhhf13EE4/EXAO7VjlfucKVdgFhD2MPBzUPve9IIOE
 O+URUkX49oV6IvM1GODVQVDTmeuTYczOh2HtWgPHJebAdHs68gmfI5iX6T96t20HHJ/gY4
 rccUbeW4z83VK8OgPjUfs9/0vU2MFp367cDXa2snXHT2lsAm4k9Fb9sTmV0Z8g==
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=breakpoint.cc;
 s=2025e; t=1782657520;
 h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
 to:to:cc:mime-version:mime-version:content-type:content-type:
 in-reply-to:in-reply-to:references:references;
 bh=rw0bmVMHOC+6OaVG8wYazlkF84tgCXNSshJsh+I9ctk=;
 b=ep1LWmVng1Otjp1HaoDJRHxhvvo28uH97A6EhPCb792U1O08sMAKJ4FIgN9FO98+t9EuoQ
 ZungBJ2hMnLebfDg==
From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
To: Sergio Gelato <sergio.gelato@astro.su.se>, 1120998-done@bugs.debian.org
Subject: Re: [Pkg-clamav-devel] Bug#1120998: clamscan: thread '<unnamed>'
 panicked while scanning a TIFF file
Message-ID: <20260628143838.tq7_7KIn@breakpoint.cc>
References: <44274fbc93294da888cbef12c908f1cd@astro.su.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <44274fbc93294da888cbef12c908f1cd@astro.su.se>

Version: 1.4.4+dfsg-1

On 2025-11-19 11:19:21 [+0000], Sergio Gelato wrote:
> Scanning
> https://github.com/holoviz/datashader/raw/refs/heads/main/datashader/tests/data/world.rgb.tif
> (sha256:
> a89c9376a0023c7b76af4df5000639d0e32d976c4f9d8750b1825ed3fac2eb7b) with
> clamscan reproducibly results in the following warning:
> 
> thread '<unnamed>' panicked at /build/reproducible-path/clamav-1.4.3+dfsg/.cargo/vendor/image/src/codecs/tiff.rs:269:21:
> copy_from_slice: source slice length (131072) does not match destination slice length (393216)
> 
> clamscan then declares the file to be OK and continues normally.

Fixed in 1.4.4.

Sebastian]