From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 9C326CCD183 for ; Mon, 13 Oct 2025 16:19:03 +0000 (UTC) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1v8LFp-0002di-3t; Mon, 13 Oct 2025 12:18:33 -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 1v8LFh-0002YR-Qe for qemu-devel@nongnu.org; Mon, 13 Oct 2025 12:18:26 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.129.124]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1v8LFb-0003p4-SV for qemu-devel@nongnu.org; Mon, 13 Oct 2025 12:18:25 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1760372297; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=dYiYnki9dQqbBGxnWMlzOcyokr0Awi0RSTzKHaadF3Q=; b=DtfOj6ohRhb6HKGfUpJ062csZ6b221ln0C1nKgOCAeicwJy8G8G/YtOELATFNjwzOT/FDW z2I5D+oKxKYNfhxItQrM5oY55eZ2Dts4yYjnoggpadLR81H4SzOt22yw/a7nSGeau/6ICS 4pXfqR94R3W0heHJDlGdz6T0rvCDheI= Received: from mx-prod-mc-01.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-551-kz3ZvuHPOsuAVLsi4ZnTgA-1; Mon, 13 Oct 2025 12:18:15 -0400 X-MC-Unique: kz3ZvuHPOsuAVLsi4ZnTgA-1 X-Mimecast-MFC-AGG-ID: kz3ZvuHPOsuAVLsi4ZnTgA_1760372294 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-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 688A2195606B; Mon, 13 Oct 2025 16:18:14 +0000 (UTC) Received: from redhat.com (unknown [10.44.32.195]) by mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 261FB19560A2; Mon, 13 Oct 2025 16:18:11 +0000 (UTC) Date: Mon, 13 Oct 2025 18:18:09 +0200 From: Kevin Wolf To: Hanna Czenczek Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org, Stefan Hajnoczi , Markus Armbruster , Brian Song Subject: Re: [PATCH v3 10/21] fuse: Add halted flag Message-ID: References: <20250701114437.207419-1-hreitz@redhat.com> <20250701114437.207419-11-hreitz@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20250701114437.207419-11-hreitz@redhat.com> X-Scanned-By: MIMEDefang 3.0 on 10.30.177.12 Received-SPF: pass client-ip=170.10.129.124; envelope-from=kwolf@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=unavailable autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Am 01.07.2025 um 13:44 hat Hanna Czenczek geschrieben: > This is a flag that we will want when processing FUSE requests > ourselves: When the kernel sends us e.g. a truncated request (i.e. we > receive less data than the request's indicated length), we cannot rely > on subsequent data to be valid. Then, we are going to set this flag, > halting all FUSE request processing. > > We plan to only use this flag in cases that would effectively be kernel > bugs. > > (Right now, the flag is unused because libfuse still does our request > processing.) > > Reviewed-by: Stefan Hajnoczi > Signed-off-by: Hanna Czenczek If we ever extend query-block-exports with export-specific information, exposing this flag would probably be a good idea. And a QMP event might make sense, too. Not a requirement for this series, though. Kevin