From nobody Wed Apr 8 04:25:42 2026 Delivered-To: importer@patchew.org Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=qemu-devel-bounces+importer=patchew.org@nongnu.org; dmarc=pass(p=quarantine dis=none) header.from=redhat.com ARC-Seal: i=1; a=rsa-sha256; t=1773160172; cv=none; d=zohomail.com; s=zohoarc; b=mKD1WBpbdxsrWiv0eF2jRTXbHIDhXmSgTz+5U/LlKuJ5lxG1EBwCgIFZdazMkj5mnBk9ZByWlKxvqHkvIT/9X3EMkpX32tWWSP7HIRZeCdgqwDm0QqQZfpnadTI9h5VvmKsbQSSiMmmz9YA1qzgpmP+bqcVaPXksnKmiUC1E4vs= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1773160172; h=Content-Transfer-Encoding:Cc:Cc:Date:Date:From:From:In-Reply-To:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:References:Sender:Subject:Subject:To:To:Message-Id:Reply-To; bh=M5HmUWnkEJbA+La4dJHbp0RAGgMPp0DV1nggQsvosNE=; b=m+5WokwI+sK2gt6Ub67861pjB8VhFwh4045tKQT5KMGOW7dK2+pmLvci/vqwxY0SLnwWadFXleK/cNKudsUpyKV6O9Ddev1VJR8h9OD9uAcftEvMtrGv7CiAVKx1/ChOihZWLKttAkQkkJSggMW9beQkIQSOBtYyjwiTY3D5jms= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=qemu-devel-bounces+importer=patchew.org@nongnu.org; dmarc=pass header.from= (p=quarantine dis=none) Return-Path: Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) by mx.zohomail.com with SMTPS id 1773160172003553.5225617062418; Tue, 10 Mar 2026 09:29:32 -0700 (PDT) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1vzzvO-0003S7-SO; Tue, 10 Mar 2026 12:27:15 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1vzzv9-0003Le-GG for qemu-devel@nongnu.org; Tue, 10 Mar 2026 12:26:59 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1vzzv7-0000uN-RB for qemu-devel@nongnu.org; Tue, 10 Mar 2026 12:26:59 -0400 Received: from mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-518-uTwkAAJrM8Cwcqq-skD6Vg-1; Tue, 10 Mar 2026 12:26:54 -0400 Received: from mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.12]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 27F701956060; Tue, 10 Mar 2026 16:26:53 +0000 (UTC) Received: from merkur.fritz.box (unknown [10.45.224.112]) by mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 0014819560A6; Tue, 10 Mar 2026 16:26:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1773160017; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=M5HmUWnkEJbA+La4dJHbp0RAGgMPp0DV1nggQsvosNE=; b=ccK1SaMTIavWbPuiAMmQ0LYr8jPMaZKqW4puXS5xi7tmsXn1uV3GM1K+0E71JBG7H3GZ7j o3Zy+cHPihgNz6EcU3mfy3QcbfWwHEnX0IWObltnfKYBc5VnNDFjx/qfkQ0DOAg3KK8Hko FykWoAwVBfFI+R4JuznrzWNZHD7BIAg= X-MC-Unique: uTwkAAJrM8Cwcqq-skD6Vg-1 X-Mimecast-MFC-AGG-ID: uTwkAAJrM8Cwcqq-skD6Vg_1773160013 From: Kevin Wolf To: qemu-block@nongnu.org Cc: kwolf@redhat.com, qemu-devel@nongnu.org Subject: [PULL 14/28] fuse: Explicitly handle non-grow post-EOF accesses Date: Tue, 10 Mar 2026 17:26:08 +0100 Message-ID: <20260310162622.333137-15-kwolf@redhat.com> In-Reply-To: <20260310162622.333137-1-kwolf@redhat.com> References: <20260310162622.333137-1-kwolf@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Scanned-By: MIMEDefang 3.0 on 10.30.177.12 Received-SPF: pass (zohomail.com: domain of gnu.org designates 209.51.188.17 as permitted sender) client-ip=209.51.188.17; envelope-from=qemu-devel-bounces+importer=patchew.org@nongnu.org; helo=lists.gnu.org; Received-SPF: pass client-ip=170.10.133.124; envelope-from=kwolf@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -3 X-Spam_score: -0.4 X-Spam_bar: / X-Spam_report: (-0.4 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.819, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.903, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: qemu development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+importer=patchew.org@nongnu.org Sender: qemu-devel-bounces+importer=patchew.org@nongnu.org X-ZohoMail-DKIM: pass (identity @redhat.com) X-ZM-MESSAGEID: 1773160174389154100 Content-Type: text/plain; charset="utf-8" From: Hanna Czenczek When reading to / writing from non-growable exports, we cap the I/O size by `offset - blk_len`. This will underflow for accesses that are completely past the disk end. Check and handle that case explicitly. This is also enough to ensure that `offset + size` will not overflow; blk_len is int64_t, offset is uint32_t, `offset < blk_len`, so from `INT64_MAX + UINT32_MAX < UINT64_MAX` it follows that `offset + size` cannot overflow. Just one catch: We have to allow write accesses to growable exports past the EOF, so then we cannot rely on `offset < blk_len`, but have to verify explicitly that `offset + size` does not overflow. The negative consequences of not having this commit are luckily limited because blk_pread() and blk_pwrite() will reject post-EOF requests anyway, so a `size` underflow post-EOF will just result in an I/O error. So: - Post-EOF reads will incorrectly result in I/O errors instead of just 0-length reads. We will also attempt to allocate a very large buffer, which is wrong and not good, but not terrible. - Post-EOF writes on non-growable exports will result in I/O errors instead of 0-length writes (which generally indicate ENOSPC). - Post-EOF writes on growable exports can theoretically overflow on EOF and truncate the export down to a much too small size, but in practice, FUSE will never send an offset greater than signed INT_MAX, preventing a uint64_t overflow. (fuse_write_args_fill() in the kernel uses loff_t for the offset, which is signed.) Signed-off-by: Hanna Czenczek Message-ID: <20260309150856.26800-15-hreitz@redhat.com> Reviewed-by: Kevin Wolf Signed-off-by: Kevin Wolf --- block/export/fuse.c | 20 +++++++++++++++++++- tests/qemu-iotests/308 | 35 ++++++++++++++++++++++++++++++----- tests/qemu-iotests/308.out | 10 ++++++++++ 3 files changed, 59 insertions(+), 6 deletions(-) diff --git a/block/export/fuse.c b/block/export/fuse.c index d45c6b814fe..af0a8de17b1 100644 --- a/block/export/fuse.c +++ b/block/export/fuse.c @@ -657,6 +657,16 @@ static void fuse_read(fuse_req_t req, fuse_ino_t inode, return; } =20 + if (offset >=3D blk_len) { + /* + * Technically libfuse does not allow returning a zero error code = for + * read requests, but in practice this is a 0-length read (and a f= uture + * commit will change this code anyway) + */ + fuse_reply_err(req, 0); + return; + } + if (offset + size > blk_len) { size =3D blk_len - offset; } @@ -717,7 +727,15 @@ static void fuse_write(fuse_req_t req, fuse_ino_t inod= e, const char *buf, return; } =20 - if (offset + size > blk_len) { + if (offset >=3D blk_len && !exp->growable) { + fuse_reply_write(req, 0); + return; + } + + if (offset + size < offset) { + fuse_reply_err(req, EINVAL); + return; + } else if (offset + size > blk_len) { if (exp->growable) { ret =3D fuse_do_truncate(exp, offset + size, true, PREALLOC_MO= DE_OFF); if (ret < 0) { diff --git a/tests/qemu-iotests/308 b/tests/qemu-iotests/308 index 6ecb275555a..a83c6fc01fb 100755 --- a/tests/qemu-iotests/308 +++ b/tests/qemu-iotests/308 @@ -300,16 +300,34 @@ dd if=3D/dev/zero of=3D"$EXT_MP" bs=3D1 count=3D64k s= eek=3D$orig_len \ conv=3Dnotrunc 2>&1 \ | _filter_testdir | _filter_imgfmt =20 +# And one really squarely post-EOF write +dd if=3D/dev/zero of=3D"$EXT_MP" bs=3D1 count=3D1 seek=3D$((orig_len + 32 = * 1024)) \ + conv=3Dnotrunc 2>&1 \ + | _filter_testdir | _filter_imgfmt + +# Half-post-EOF reads +dd if=3D"$EXT_MP" of=3D/dev/null bs=3D1 count=3D64k skip=3D$((orig_len - 3= 2 * 1024)) \ + 2>&1 | _filter_testdir | _filter_imgfmt + +# And one really squarely post-EOF read +dd if=3D"$EXT_MP" of=3D/dev/null bs=3D1 count=3D1 skip=3D$((orig_len + 32 = * 1024)) \ + 2>&1 | _filter_testdir | _filter_imgfmt + echo echo '--- Resize export ---' =20 # But we can truncate it explicitly; even with fallocate -fallocate -o "$orig_len" -l 64k "$EXT_MP" +# (Make sure we extend it to a length not divisible by 128k, we need that = below) +bs=3D$((128 * 1024)) +extend_to=3D$(((orig_len + bs - 1) / bs * bs + bs / 2)) +extend_by=3D$((extend_to - orig_len)) + +fallocate -o "$orig_len" -l $extend_by "$EXT_MP" =20 new_len=3D$(get_proto_len "$EXT_MP" "$TEST_IMG") -if [ "$new_len" !=3D "$((orig_len + 65536))" ]; then +if [ "$new_len" !=3D "$extend_to" ]; then echo 'ERROR: Unexpected post-truncate image size:' - echo "$new_len !=3D $((orig_len + 65536))" + echo "$new_len !=3D $extend_to" else echo 'OK: Post-truncate image size is as expected' fi @@ -322,6 +340,13 @@ else echo "$orig_disk_usage =3D> $new_disk_usage" fi =20 +# Use this opportunity to test a read access across the (now no longer so = much +# aligned) EOF. dd can only do requests with a length of its block size, = and +# all of its seek/skip values are in bs units, so it is hard to do a reque= st +# across the EOF if the EOF is at a power of two (64M). +dd if=3D"$EXT_MP" of=3D/dev/null bs=3D$bs count=3D2 skip=3D$((extend_to / = bs)) \ + 2>&1 | _filter_testdir | _filter_imgfmt + echo echo '--- Try growing growable export ---' =20 @@ -338,9 +363,9 @@ dd if=3D/dev/zero of=3D"$EXT_MP" bs=3D1 count=3D64k see= k=3D$new_len conv=3Dnotrunc 2>&1 \ | _filter_testdir | _filter_imgfmt =20 new_len=3D$(get_proto_len "$EXT_MP" "$TEST_IMG") -if [ "$new_len" !=3D "$((orig_len + 131072))" ]; then +if [ "$new_len" !=3D "$((extend_to + 65536))" ]; then echo 'ERROR: Unexpected post-grow image size:' - echo "$new_len !=3D $((orig_len + 131072))" + echo "$new_len !=3D $((extend_to + 65536))" else echo 'OK: Post-grow image size is as expected' fi diff --git a/tests/qemu-iotests/308.out b/tests/qemu-iotests/308.out index 2d7a38d63d2..ebeaf64b486 100644 --- a/tests/qemu-iotests/308.out +++ b/tests/qemu-iotests/308.out @@ -134,11 +134,21 @@ wrote 65536/65536 bytes at offset 1048576 dd: error writing 'TEST_DIR/t.IMGFMT.fuse': No space left on device 1+0 records in 0+0 records out +dd: error writing 'TEST_DIR/t.IMGFMT.fuse': No space left on device +1+0 records in +0+0 records out +32768+0 records in +32768+0 records out +dd: TEST_DIR/t.IMGFMT.fuse: cannot skip to specified offset +0+0 records in +0+0 records out =20 --- Resize export --- (OK: Lengths of export and original are the same) OK: Post-truncate image size is as expected OK: Disk usage grew with fallocate +0+1 records in +0+1 records out =20 --- Try growing growable export --- {'execute': 'block-export-del', --=20 2.53.0